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 21: Unneeded If statements

PreviousGas Saving Technique 20: Storage vs Memory read optimizationsNextGas Saving Technique 22: >= is cheaper than >

Last updated 1 year ago

Introduction

Every operation in a smart contract costs gas. To optimize for lower gas consumption, it is crucial to remove code that doesn't contribute to the contractโ€™s functionality. One common area of improvement is the removal of unnecessary if statements that check conditions already verified elsewhere or conditions that can never be true. This tutorial will guide you through identifying and removing such redundant if statements.

Impact & Details

Understanding the Impact:

  • Gas Savings: Unnecessary if statements waste gas each time the contract is called, and removing them can lead to gas savings over the lifetime of the contract.

  • Code Simplification: Redundant checks complicate the codebase. Removing them simplifies the code, making it easier to read and maintain.

Example: Removing Unneeded 'If' Statements

Before Optimization:

solidityCopy codepragma solidity ^0.8.0;

contract ExampleContract {
    function cleanUp(bytes32 claimIdentifier) external {
        if (_setState(claimIdentifier, State.NonExistent) != State.Cleaned) {
            revert InvalidState();  // This check might be unnecessary
        }
        // ... rest of the function ...
    }
}

After Optimization:

Analyzing the _setState function and understanding the various states a claimIdentifier can be in will often reveal that some checks are unnecessary. If you find that _setState(claimIdentifier, State.NonExistent) can only result in State.Cleaned or revert beforehand, you can safely remove the if statement.

solidityCopy codepragma solidity ^0.8.0;

contract ExampleContract {
    function cleanUp(bytes32 claimIdentifier) external {
        _setState(claimIdentifier, State.NonExistent);
        // The unnecessary 'if' statement has been removed
        // ... rest of the function ...
    }
}

Recommended Mitigation Steps

  1. Review and Analyze: Review the code thoroughly to identify if statements that check for conditions already verified elsewhere or that will never be true.

  2. Remove Redundant Checks: After identification, safely remove these unnecessary if statements from the code.

  3. Test: Always test the contract after making changes to ensure that it still behaves as expected.

Conclusion

Removing unneeded if statements is a simple yet effective optimization that can lead to gas savings and a cleaner, more manageable codebase. Always be sure to understand the logic and states of your contract thoroughly to safely remove these checks without introducing new risks, and test your contract extensively to ensure it behaves as expected after the changes.

๐Ÿ“š
โœ’๏ธ
Book an audit with Zokyo