Storage vs Memory vs Calldata

In Solidity, understanding where data is stored is crucial for both functionality and gas efficiency. Solidity provides three main locations for storing data: storage, memory, and calldata.

1. Storage

• Definition: Storage refers to permanent data stored on the blockchain.
• Scope: State variables are stored in storage.
• Persistence: Changes in storage are permanent and persist across function calls and transactions.
• Gas Cost: Writing to storage is expensive, while reading is cheaper than writing.

Example:

pragma solidity ^0.8.20;

contract StorageExample {
    uint256 public storedData; // Stored permanently on blockchain

    function setStoredData(uint256 _data) public {
        storedData = _data; // Writing to storage costs gas
    }

    function getStoredData() public view returns (uint256) {
        return storedData; // Reading storage is cheaper
    }
}

2. Memory

• Definition: Memory is temporary storage used within function execution.
• Scope: Exists only during a function call.
• Persistence: Data is lost after the function ends.
• Gas Cost: Cheaper than storage for temporary operations.

Example:

pragma solidity ^0.8.20;

contract MemoryExample {
    function doubleValue(uint256 _value) public pure returns (uint256) {
        uint256 temp = _value * 2; // Stored in memory
        return temp;
    }
}

3. Calldata

• Definition: Calldata is read-only data passed to functions, mainly for external function parameters.
• Scope: Exists only during the external function call.
• Persistence: Data cannot be modified.
• Gas Cost: Very cheap because it avoids copying data into memory.

Example:

pragma solidity ^0.8.20;

contract CalldataExample {
    function getFirstElement(uint256[] calldata arr) external pure returns (uint256) {
        return arr[0]; // Read-only access, no gas for copying
    }
}