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 7: Using Short Reason Strings

PreviousGas Saving Technique 6: NOT operator ! cheaper than boolean FALSENextGas Saving Technique 8: Use Custom Errors instead of Revert Strings to save Gas

Last updated 1 year ago

Introduction

Developing cost-efficient smart contracts on the Ethereum blockchain requires a keen eye for detail, where even seemingly minor optimizations can lead to reduced gas consumption. One such optimization technique involves minimizing the length of reason strings used in require statements or error messages. Keeping reason strings short and concise not only aids in readability but also helps save gas, making transactions more cost-effective.

Impact & Details

Understanding Gas Consumption

  • Size Matters: In Ethereum, the deployment and execution cost of smart contracts is influenced by their size. Since strings consume storage, longer reason strings naturally lead to higher gas costs. Every string used occupies at least 32 bytes.

  • Cost Efficiency with Short Strings: By keeping reason strings within 32 bytes, you can avoid unnecessary gas expenses. Short, clear, and meaningful strings are the key to efficient gas usage and effective communication with contract users.

How to Implement Short Reason Strings for Gas Savings

Practical Example: Efficient Reason Strings Usage

Below are examples illustrating the optimization:

Before Optimization:

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

contract ReasonStringsOptimizer {
    function doSomething(uint value) public pure {
        require(value > 10, "The provided value must be greater than 10");
    }
}

After Optimization:

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

contract ReasonStringsOptimizer {
    function doSomething(uint value) public pure {
        require(value > 10, "Value must be > 10");
    }
}

In the optimized version, the reason string is shortened while still conveying the necessary information, thereby saving gas.

Recommended Mitigation Steps

  1. Identify Long Reason Strings: Go through your smart contracts and identify reason strings that exceed 32 bytes.

  2. Shorten Reason Strings: Redraft and shorten the identified strings, ensuring they remain within 32 bytes while still conveying the intended message clearly.

  3. Test: Conduct testing to ensure the smart contract functions as expected with the revised reason strings, while also saving gas.

Conclusion

Employing short reason strings is a straightforward yet effective technique to save gas in smart contract development. While the gas savings for individual transactions might be small, the cumulative effect over numerous transactions can be substantial. Additionally, concise messages contribute to better readability and understanding of the contractโ€™s functions and requirements. After implementing these changes, thorough testing is crucial to confirm that the contract continues to operate as intended while utilizing less gas.

๐Ÿ“š
๐Ÿชก
Book an audit with Zokyo