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 12: SafeMath no longer needed

PreviousGas Saving Technique 11: > 0 is less efficient than != 0 for unsigned integersNextGas Saving Technique 13: variables default to 0

Last updated 1 year ago

Introduction

Efficient gas usage in smart contracts is crucial for the cost-effective operation on the Ethereum network. With the release of Solidity 0.8, some previously essential libraries are no longer needed, creating an opportunity for gas savings. One notable example is the SafeMath library, which was commonly used to prevent integer overflow and underflow. Since Solidity 0.8, these checks are built into the compiler, making SafeMath redundant and removable for gas optimization.

Impact & Details

Understanding Gas Consumption

  • SafeMath Overhead: Previously, the SafeMath library was indispensable for safely conducting arithmetic operations. However, it introduces additional gas costs due to the external library calls and checks it performs.

  • Compiler-Level Checks: Starting with Solidity 0.8, the compiler includes built-in checks for integer overflow and underflow, eliminating the need for SafeMath and thereby saving gas on each transaction that involves arithmetic operations.

How to Remove SafeMath for Gas Savings

Practical Example: Removing SafeMath

Hereโ€™s a contract example before and after the removal of SafeMath:

Before Optimization:

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

import "@openzeppelin/contracts/math/SafeMath.sol";

contract MyContract {
    using SafeMath for uint256;

    function add(uint256 a, uint256 b) public pure returns (uint256) {
        return a.add(b);
    }
}

After Optimization:

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

contract MyContract {
    function add(uint256 a, uint256 b) public pure returns (uint256) {
        return a + b;  // Safe due to built-in overflow checks in Solidity 0.8 and above
    }
}

Recommended Mitigation Steps

  1. Identify SafeMath Usage: Look through your smart contracts to identify where SafeMath is being used.

  2. Remove SafeMath: For contracts using Solidity 0.8 and above, remove SafeMath and refactor arithmetic operations to use standard operators.

  3. Test: After removal, rigorously test the contract to ensure it maintains expected functionality while saving gas on arithmetic operations.

Conclusion

Removing the SafeMath library from smart contracts compiled with Solidity 0.8 and above is a straightforward and effective optimization technique for reducing gas consumption. Though the savings per transaction may seem small, it can amount to a substantial total when considering the volume of transactions processed over time. Ensure to comprehensively test the contract post-optimization to validate its behavior and the gas savings achieved.

๐Ÿ“š
โž—
Book an audit with Zokyo