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 40: Removal of Unused Internal Functions for Gas Savings

PreviousGas Saving Technique 39: Avoiding Duplicated Code for Gas SavingsNextGas Saving Tutorial 41: In-lining Single Use Modifiers For Gas Saving

Last updated 1 year ago

Introduction: Internal functions that aren't invoked anywhere within a smart contract are essentially dead code. Not only do they clutter the contract, but they also increase the overall bytecode size, thereby increasing the gas required for contract deployment. This tutorial will guide you on the importance and methods of removing unused internal functions for optimal gas efficiency.

Concept:

  1. Internal Functions: Functions in Solidity that can only be called from the contract they are defined in or from derived contracts.

  2. Deployment Costs: The gas required to deploy a smart contract on the Ethereum network is directly proportional to its bytecode size.

Why Remove Unused Internal Functions?:

  1. Reduced Gas Costs: Eliminating unnecessary code directly reduces the contract's size, leading to cheaper deployment costs.

  2. Improved Readability: Removing unused functions can make the contract easier to read and understand.

  3. Better Maintenance: Fewer lines of code mean fewer potential points of failure or bugs.

Steps to Ensure Efficient Usage:

  1. Regular Audits:

    • Periodically review the contract's functions to identify and remove any that are no longer used.

    • Automated tools and linters can help flag potential unused functions.

  2. Use Interfaces Appropriately:

    • If a contract must have specific functions due to an interface but doesn't use them, ensure the contract inherits from the required interface.

    • Apply the override keyword to functions that are meant to fulfill interface requirements.

  3. Refactoring:

    • As contracts evolve, the necessity for certain functionalities might change. Regularly refactor the codebase to remove redundancies.

Conclusion: Regularly pruning your smart contracts by removing unused internal functions is crucial for ensuring optimal gas efficiency during deployment. It's a best practice that leads to cleaner, more efficient, and easier-to-maintain code.

📚
😄
Book an audit with Zokyo