Zokyo Gas Savings
  • โ›ฝZokyo Gas Savings
  • ๐Ÿ“šTutorials
    • โœ”๏ธGas Saving Technique 1: Unchecked Arithmetic
    • โ›“๏ธGas Saving Technique 2: Immutable Variable
    • โœจGas Saving Technique 3: Double star ** inefficiency
    • ๐Ÿ’ฐGas Saving Technique 4: Cache Array Length
    • โฌ…๏ธGas Saving Technique 5: ++i costs less gas compared to i++
    • โš–๏ธGas Saving Technique 6: NOT operator ! cheaper than boolean FALSE
    • ๐ŸชกGas Saving Technique 7: Using Short Reason Strings
    • ๐ŸชตGas Saving Technique 8: Use Custom Errors instead of Revert Strings to save Gas
    • โœ’๏ธGas Saving Technique 9: Use Custom Errors instead of Revert Strings to save Gas
    • ๐Ÿ‘พGas Saving Technique 10: Calldata cheaper than memory
    • โ›”Gas Saving Technique 11: > 0 is less efficient than != 0 for unsigned integers
    • โž—Gas Saving Technique 12: SafeMath no longer needed
    • ๐Ÿ˜ฎGas Saving Technique 13: variables default to 0
    • ๐ŸงฑGas Saving Technique 14: struct layout/ variable packing
    • ๐Ÿ“žGas Saving Technique 15: Cache External Call
    • โœ๏ธGas Saving Technique 16: Early Validation before external call
    • ๐Ÿ˜ŽGas Saving Technique 17: Donโ€™t cache value that is used once
    • ๐Ÿ˜งGas Saving Technique 18: Redundant code
    • โœ…Gas Saving Technique 19: Early Validation before external call
    • โ›๏ธGas Saving Technique 20: Storage vs Memory read optimizations
    • โœ’๏ธGas Saving Technique 21: Unneeded If statements
    • ๐ŸŒ—Gas Saving Technique 22: >= is cheaper than >
    • ๐ŸŽ’Gas Saving Technique 23: Public to private constants
    • โน๏ธGas Saving Technique 24: Make unchanged variables constant/immutable
    • โฑ๏ธGas Saving Techniques 25: Redundant Access Control Checks
    • โžก๏ธGas Saving Technique 26: Shift Right instead of Dividing by 2
    • ๐ŸชƒGas Saving Tutorial 27: Efficient Boolean Comparison
    • ๐ŸคGas Saving Technique 28: && operator uses more gas
    • ๐Ÿ‘“Gas Saving Technique 29: x = x + y is cheaper than x += y
    • ๐Ÿ‘‚Gas Saving Technique 30: Using 1 and 2 rather than 0 and 1 saves gas
    • โšฝGas Saving Technique 31: Optimize Storage by Avoiding Booleans
    • ๐Ÿ”™Gas Saving Technique 32: Optimal Use of Named Return Variables in Solidity
    • ๐Ÿ›ข๏ธGas Saving Technique 33: Making Functions Payable for Optimized Gas Costs
    • โœ๏ธGas Saving Technique 34: Optimizing Storage References in Smart Contracts
    • โ›ฐ๏ธGas Saving Technique 35: Usage of uints/ints smaller than 32 bytes (256 bits) incurs overhead
    • ๐ŸŒช๏ธGas Saving Technique 36: Inlining Single Use Internal Functions for Savings
    • โ˜„๏ธGas Saving Technique 37: Switching from Public to External Functions for Savings
    • ๐ŸŽ†Gas Saving Technique 38: Upgrading Solidity Compiler to Improve Gas Efficiency and Security
    • ๐Ÿ•ถ๏ธGas Saving Technique 39: Avoiding Duplicated Code for Gas Savings
    • ๐Ÿ˜„Gas Saving Technique 40: Removal of Unused Internal Functions for Gas Savings
    • ๐Ÿ–‹๏ธGas Saving Tutorial 41: In-lining Single Use Modifiers For Gas Saving
    • โ›๏ธGas Saving Technique 42: `require` vs`assert`
Powered by GitBook
On this page
  1. Tutorials

Gas Saving Technique 19: Early Validation before external call

PreviousGas Saving Technique 18: Redundant codeNextGas Saving Technique 20: Storage vs Memory read optimizations

Last updated 1 year ago

Introduction

Optimizing gas costs is crucial when developing smart contracts. An effective approach is implementing early validation checks before external calls are made. By ensuring the validity of function parameters or states beforehand, you can avoid unnecessary gas expenditure, especially if the function is likely to fail due to invalid inputs or states. This tutorial will elaborate on this gas-saving technique.

Impact & Details

Importance of Early Validation

  • Avoiding Unnecessary Gas Costs: Early validations help prevent executing costly external calls that are destined to fail, saving gas.

  • Enhanced Code Readability and Maintenance: This approach fosters a coding style thatโ€™s not only gas-efficient but also clear and maintainable.

Example: Implementing Early Validation

Below is a structured example to illustrate the importance of early validation:

Before Optimization:

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

contract ExampleContract {
    function withdrawAll() external returns (uint256) {
        ILendingPool lp = getLp();  // External call placed before the validation check
        if (balanceOf() == 0) {
            return 0;  // Function would fail here if balance is zero
        }
        // ... rest of the function ...
    }
}

After Optimization:

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

contract ExampleContract {
    function withdrawAll() external returns (uint256) {
        if (balanceOf() == 0) {
            return 0;  // Early validation prevents the external call if balance is zero, saving gas
        }
        ILendingPool lp = getLp();  // External call is made after validation
        // ... rest of the function ...
    }
}

Recommended Mitigation Steps

  1. Early Validation Implementation: Review the smart contract, identify and implement validation checks before making external calls.

  2. Rearrange Code Sequence: If necessary, rearrange the code to ensure validations are made as early as possible to avoid futile gas consumption in the case of function failure.

  3. Test: After rearranging and implementing early checks, rigorously test the smart contract to ensure its functionality while observing the gas savings.

Conclusion

Implementing early validation checks before external calls is a practical and effective technique to optimize gas usage, especially in scenarios where functions might fail. This practice not only economizes gas but also results in cleaner, more understandable, and maintainable code. Always ensure thorough testing after making these optimizations to confirm improved gas efficiency without compromising the contract's functionality.

๐Ÿ“š
โœ…
Book an audit with Zokyo