Skip to content
Home ยป Answers ยป Function Modifiers (view, pure, payable) and Fallback Functions in Solidity

Function Modifiers (view, pure, payable) and Fallback Functions in Solidity

Function Modifiers (view, pure, payable) and Fallback Functions in Solidity

Function modifiers

Function modifiers in Solidity are powerful tools for adding common functionality to multiple functions within a contract. They allow developers to enforce security checks, optimize gas usage, and handle special cases like Ether transactions. Solidity provides three main built-in modifiers: view, pure, and payable.

1. view modifier

The view modifier indicates that the function will not modify the state of the contract. It’s akin to a read-only operation, allowing functions to fetch data from the blockchain without altering any values. By marking a function with view, Solidity ensures that it cannot change any state variables within the contract.

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;

contract MyContract {
    uint256 public myNumber = 10;

    function getNumber() public view returns (uint256) {
        return myNumber;

In this example, the getNumber function is marked with the view modifier because it only reads the value of myNumber without making any modifications to it. This is useful for querying contract states without incurring gas costs.

๐Ÿ”ฅ Check this course out:ย Create Your Own Ethereum Token in Just 30 Mins

2. pure modifier

The pure modifier goes a step further than view by ensuring that the function does not even read the contract’s state. It’s reserved for functions that perform computations and return results solely based on their inputs, without interacting with the blockchain state.

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;

contract MathOperations {
    function square(uint x) public pure returns (uint) {
        return x * x;

In the MathOperations contract, the square function is marked with pure because it only relies on its input x to compute and return the square, without accessing any state variables. This allows for efficient and predictable behavior, particularly in mathematical calculations.

3. payable modifier

The payable modifier is crucial for functions that can receive Ether along with the function call. Without this modifier, a function cannot accept Ether transfers, and sending Ether to such a function would result in an exception. This modifier is essential for implementing financial transactions in Solidity contracts.

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;

contract PayableContract {
    function receivePayment() public payable {
        // Code to handle received Ether

In the PayableContract example, the receivePayment function is marked as payable, allowing it to receive Ether transfers along with the function call. This is commonly used for functions involved in crowdfunding, payments, or token purchases within smart contracts.

๐Ÿ”ฅ Check this course out:ย Build a One Piece Personality dApp With Solidity

Fallback functions

Fallback functions in Solidity are special functions that are executed if a contract is called and no other function matches the given function signature, or if Ether is sent directly to a contract without specifying a function to call. Fallback functions have no name and cannot accept arguments or return values.

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;

contract FallbackExample {
    event Received(address sender, uint amount);

    fallback() external payable {
        emit Received(msg.sender, msg.value);

In this example, the fallback function is triggered when someone sends Ether to the contract without specifying a function to call. It emits an event to log the sender’s address and the amount of Ether sent. Fallback functions are useful for handling unexpected interactions with contracts and managing Ether transfers.

Use Cases and Best Practices

Now that we understand function modifiers and fallback functions, let’s explore some common use cases and best practices for their usage.

1. Security Checks

Modifiers are often used to enforce security checks before executing a function. For example, you might have a modifier to restrict access to certain functions only to the contract owner or authorized users.

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;

contract AccessControl {
    address public owner;

    modifier onlyOwner() {
        require(msg.sender == owner, "Only contract owner can call this function");

    constructor() {
        owner = msg.sender;

    function changeOwner(address newOwner) public onlyOwner {
        owner = newOwner;

In this AccessControl contract, the onlyOwner modifier ensures that only the contract owner can call functions restricted by this modifier. This helps prevent unauthorized access and protects sensitive operations within the contract.

2. Gas optimization

Using view and pure modifiers can help optimize gas costs since they don’t involve state changes. This is especially important when interacting with contracts on the Ethereum blockchain, where gas fees can be significant. By marking functions appropriately, developers can reduce unnecessary gas consumption and make their contracts more efficient.

3. Handling Ether

When dealing with Ether transactions, always use the payable modifier for functions that need to receive Ether. Additionally, make sure to implement a fallback function to handle unexpected Ether transfers. This ensures that contracts can gracefully handle Ether payments and prevent funds from being locked or lost.

๐Ÿ”ฅ Check this course out:ย Build a Semi-Fungible ERC404 Tokens’ Marketplace


In Solidity, function modifiers, and fallback functions are essential tools for defining the behavior and security of smart contracts. Modifiers allow for code reuse and enforce constraints, while fallback functions provide a fallback mechanism for handling unexpected calls and Ether transfers. Understanding and correctly utilizing these features is crucial for writing efficient and secure smart contracts on the Ethereum blockchain. By applying best practices and considering the use cases outlined above, developers can create robust and reliable contracts that meet the needs of their applications.

Try it out, ask us questions, and tell us how it went by tagging Metaschool on Social Media.

Follow us on โ€“

๐Ÿ”ฎTwitter โ€“ย

๐Ÿ”—LinkedIn โ€“ย