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 26: Shift Right instead of Dividing by 2

PreviousGas Saving Techniques 25: Redundant Access Control ChecksNextGas Saving Tutorial 27: Efficient Boolean Comparison

Last updated 1 year ago

Introduction: When dealing with smart contracts, every gas unit counts. Optimizing operations, especially arithmetic ones, can lead to significant savings. A common operation seen in contracts is division by 2. While this operation is straightforward, it may not be the most gas-efficient. In this tutorial, we'll explore a more efficient method using the bitwise right shift operation.

Concept: In binary arithmetic, shifting a number one position to the right is equivalent to dividing it by 2. Similarly, shifting left equates to multiplying by 2. Solidity provides the >> operator for the bitwise right shift. When replacing division by 2 with the right shift operation, we achieve two primary advantages:

  1. Gas Efficiency: The EVM's DIV opcode consumes 5 gas. In contrast, the SHR (Shift Right) opcode only requires 3 gas, leading to a 40% reduction in gas for this operation.

  2. Bypass Additional Checks: Solidity's division operation includes a check for division-by-zero. When using bitwise shifting, we bypass this check, thus saving additional gas.

Example:

In the given code snippet:

solidityCopy codeClearingHouse.sol:212: uint toInsurance = liquidationFee / 2;

We can replace the division by 2 with a bitwise right shift for efficiency:

solidityCopy codeClearingHouse.sol:212: uint toInsurance = liquidationFee >> 1;

Recommendation:

  1. Identify areas in your code where division by 2 is used.

  2. Replace the division operation with a bitwise right shift.

  3. Ensure the context and logic still make sense after the change, especially when handling negative values or when precision is paramount.

Conclusion:

Optimizing smart contracts for gas efficiency is crucial, especially when deploying and interacting with them on networks with high gas costs. Replacing divisions by 2 with bitwise right shifts is a simple yet effective way to save on gas. This change doesn't compromise the code's readability, making it a worthwhile optimization to consider in your contracts.

๐Ÿ“š
โžก๏ธ
Book an audit with Zokyo