0Pricing
Web3 & DApp Development Fundamentals · 课时

Gas 优化技术

学习编写高效利用 Gas 的 Solidity 代码，降低交易成本并提升 DApp 在区块链上的性能

Gas 优化技术 是 CoddyKit 上的免费 Web3 & DApp Development Fundamentals 课时。 这是第 3 节课，共 3 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Web3 & DApp Development Fundamentals 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Web3 & DApp Development Fundamentals 课程共包含 3 节课。

本课时的部分内容尚未翻译，以英文显示。

Why Gas Optimization Matters

Welcome to the final lesson in DApp Security & Auditing! Today, we'll master Gas Optimization Techniques.

Gas is the fee paid to execute transactions on the Ethereum network. It's like fuel for your car.

  • Cost Reduction: Lower gas fees mean cheaper transactions for users.
  • Performance: Optimized contracts execute faster.
  • User Experience: Better performance leads to happier users and smoother DApps.

Understanding Gas Costs

Every operation the Ethereum Virtual Machine (EVM) performs costs a certain amount of gas. Complex operations cost more.

When you deploy or interact with a smart contract, you pay gas for:

  • Storing data on the blockchain (most expensive).
  • Performing computations.
  • Sending Ether.

Our goal is to write code that uses fewer of these expensive operations.

Storage vs. Memory vs. Calldata

Understanding where your data lives is key to saving gas. Each location has different costs:

  • Storage: Permanent, on-chain. Most expensive to read/write (SSTORE/SLOAD).
  • Memory: Temporary, exists only during function execution. Cheaper than storage.
  • Calldata: Immutable, read-only, temporary. Used for external function arguments. Cheapest for external inputs.

Prioritize using calldata or memory for variables that don't need to persist on-chain.

Minimize Storage Writes (SSTORE)

Writing to storage (SSTORE) is the single most expensive operation in Solidity. Always ask: does this variable really need to be stored on-chain?

Instead of updating a counter in storage for every iteration, compute it once at the end or use events to log changes.

Consider this simple example:

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

contract StorageCostExample {
    uint256 public counter;

    // High gas cost: writes to storage every call
    function incrementBad() public {
        counter++;
    }

    // Lower gas cost: only reads state
    function getCounter() public view returns (uint256) {
        return counter;
    }
}

Packing Storage Variables

Solidity stores variables in 256-bit (32-byte) 'slots'. If you declare multiple variables that fit within a single slot, they can be 'packed' together, saving gas.

For example, three uint8 variables take up less storage than three uint256 variables if declared consecutively. This saves SSTORE operations.

  • Declare smaller data types (e.g., uint8, bool) when possible.
  • Group variables of similar sizes together.
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;

contract StoragePacking {
    // These will likely pack into one slot
    uint8 public value1;
    bool public isActive;
    uint8 public value2;

    // This will take a separate slot
    address public owner;

    function setValues(uint8 _v1, bool _active, uint8 _v2) public {
        value1 = _v1;
        isActive = _active;
        value2 = _v2;
    }
}

Short-Circuiting Conditionals

When using logical operators like && (AND) or || (OR), Solidity uses 'short-circuiting'. This means it stops evaluating conditions once the result is known.

You can save gas by placing the cheaper, more likely-to-fail, or more likely-to-be-true conditions first.

  • For &&, put the condition most likely to be false first.
  • For ||, put the condition most likely to be true first.
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;

contract ShortCircuitExample {
    uint256 public data = 100;

    function checkCondition(uint256 _input) public view returns (bool) {
        // Cheaper check (input) before more expensive check (storage read)
        return (_input > 0 && data > 50); 
    }
}

Efficient Loops & Iterations

Loops can be gas-expensive, especially if they iterate over large arrays stored in storage. Avoid unbounded loops or loops over dynamic arrays in storage when possible.

  • Process data off-chain if possible.
  • Use fixed-size arrays instead of dynamic ones if the size is known.
  • Refactor logic to avoid loops or reduce iterations.
  • Consider a pull-based system for payouts instead of pushing to many recipients in one transaction.

Using `view` and `pure` Functions

Functions marked as view or pure do not modify the blockchain state. When called externally, they don't cost any gas!

  • view: Reads state variables but doesn't modify them.
  • pure: Neither reads nor modifies state variables.

Internal calls to view/pure functions still consume gas (as part of the larger transaction), but using them correctly for external queries is a huge gas saver for users.

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

contract ViewPureExample {
    uint256 public myNumber = 42;

    // Costs no gas for external calls
    function getNumber() public view returns (uint256) {
        return myNumber;
    }

    // Costs no gas for external calls
    function add(uint256 a, uint256 b) public pure returns (uint256) {
        return a + b;
    }
}

Error Handling Gas Costs

Solidity provides several ways to handle errors: require(), revert(), and assert().

  • require(): Used for validating inputs and conditions. Refunds unused gas when it fails. (Recommended for most checks)
  • revert(): Similar to require, also refunds unused gas.
  • assert(): Used for internal invariants and should *never* fail. Consumes ALL remaining gas when it fails. (Use sparingly for critical internal checks)

Failing an assert is much more expensive than failing a require, so choose your error handling wisely.

Question: Gas Optimization

Consider the following Solidity snippet. Which change would likely lead to the MOST significant gas savings for a user calling updateStatus?

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

contract GasPuzzle {
    uint256 public statusId;
    string public statusName;
    address public owner;

    constructor() {
        owner = msg.sender;
        statusId = 1;
        statusName = "Initial";
    }

    function updateStatus(uint256 _newId, string memory _newName) public {
        require(msg.sender == owner, "Not owner");
        statusId = _newId;
        statusName = _newName;
    }
}

Recap: Gas Optimization Mastery

You've unlocked key strategies for writing gas-efficient Solidity code!

Remember these principles:

  • Minimize Storage Writes: The golden rule.
  • Pack Variables: Group smaller variables to fit slots.
  • Use Efficient Data Locations: Prefer calldata/memory over storage.
  • Optimize Loops: Avoid unbounded or large iterations.
  • Leverage view/pure: For gas-free external reads.
  • Smart Error Handling: Use require/revert, not assert for user input.

Applying these techniques will lead to more affordable, faster, and user-friendly DApps. Keep practicing!

常见问题解答

「Gas 优化技术」课时是免费的吗？

是的 — 「Gas 优化技术」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Web3 & DApp Development Fundamentals 课程的其余内容，请升级到 CoddyKit PRO。 Web3 & DApp Development Fundamentals 课程共包含 3 节课。

「Gas 优化技术」这节课中我会学到什么？

学习编写高效利用 Gas 的 Solidity 代码，降低交易成本并提升 DApp 在区块链上的性能 你通过在浏览器中直接运行的动手代码来练习 Web3 & DApp Development Fundamentals，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Web3 & DApp Development Fundamentals 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Web3 & DApp Development Fundamentals 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 3 节课，共 3 节。

「Gas 优化技术」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Web3 & DApp Development Fundamentals 课中编写并运行代码吗？

能。每节 Web3 & DApp Development Fundamentals 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. 常见智能合约漏洞
  2. 安全工具与审计
  3. Gas 优化技术
← 返回 Web3 & DApp Development Fundamentals