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 39: Avoiding Duplicated Code for Gas Savings

PreviousGas Saving Technique 38: Upgrading Solidity Compiler to Improve Gas Efficiency and SecurityNextGas Saving Technique 40: Removal of Unused Internal Functions for Gas Savings

Last updated 1 year ago

Introduction: Duplicated code, also known as code redundancy, not only affects the readability and maintainability of smart contracts but also has a direct impact on deployment and execution costs. Each repeated line of code contributes to the overall size of a contract, leading to increased gas costs. This tutorial highlights the importance of avoiding duplicated code for gas efficiency.


Concept:

  1. Duplicated Code: Refers to identical or very similar blocks of code that appear in multiple locations in a contract.

  2. Gas Efficiency: The measure of how effectively a contract utilizes the gas required for deployment and transaction execution. Duplicated code negatively impacts gas efficiency by increasing the overall bytecode size.


Reasons to Avoid Duplicated Code:

  1. Increased Deployment Costs: The larger the contract's bytecode, the more gas required to deploy it on the Ethereum network.

  2. Higher Transaction Costs: Repeated operations can lead to higher execution costs for transactions.

  3. Maintenance Challenges: Duplicated code can introduce bugs and make it harder to update or modify the contract in the future.

  4. Readability: Redundant code makes it harder for developers to understand the contract's logic, potentially leading to errors or overlooked vulnerabilities.


Techniques to Reduce Duplicated Code:

  1. Modularization:

    • Break your contract into smaller, reusable components or functions.

    • For example, if multiple functions use the same logic for checking user permissions, move that logic into a separate internal function.

  2. Use Libraries:

    • Externalize common logic into libraries. This allows you to reuse code across different contracts.

    • Example: SafeMath library in Solidity for arithmetic operations.

  3. Inheritance and Interfaces:

    • Use inheritance to create base contracts with shared logic that can be inherited by other contracts.

    • Define interfaces for contracts that can implement common functionality.

  4. State Variable Initialization:

    • If multiple functions initialize the same state variables with default values, consider setting these defaults during contract deployment to avoid redundancy.

Conclusion: Avoiding duplicated code is essential for writing gas-efficient, readable, and maintainable smart contracts. Regularly reviewing and refactoring contracts to minimize redundancy can save developers both gas and potential headaches in the long run.

๐Ÿ“š
๐Ÿ•ถ๏ธ
Book an audit with Zokyo