Canto Liquidity Mining Protocol - hihen's results

Summary

Total 12 instances over 3 issueswith 382 gas saved:

Gas Optimizations

[G‑01] Use unchecked block for safe subtractions

If it can be confirmed that the subtraction operation will not overflow, using an unchecked block can save gas. For example, require(x <= y); z = y - x; can be optimized to require(x <= y); unchecked { z = y - x; }.

There are 4 instances:

• LiquidityMining.sol ( #L56, #L101, #L213, #L243 ):

/// @audit checked on line 50
56:                         : block.timestamp - time

/// @audit checked on line 94
101:                             : block.timestamp - time

/// @audit checked on line 207
213:                         : block.timestamp - time

/// @audit checked on line 237
243:                         : block.timestamp - time

[G‑02] Do not cache state variables that are used only once

It's cheaper to access the state variable directly if it is accessed only once. This can save the 3 gas cost of the extra stack allocation.

There are 2 instances:

• LiquidityMining.sol ( #L169, #L261 ):

169:         CurveMath.CurveState memory curve = curves_[poolIdx];

261:         CurveMath.CurveState memory curve = curves_[poolIdx];

[G‑03] Using assembly to check for zero can save gas

Using assembly to check for zero can save gas by allowing more direct access to the evm and reducing some of the overhead associated with high-level operations in solidity.

There are 6 instances:

• LiquidityMining.sol ( #L47, #L86, #L114, #L142, #L204, #L233 ):

47:         if (lastAccrued != 0) {

86:         if (lastAccrued != 0) {

114:                         if (tickTracking.exitTimestamp == 0) {

142:                     if (tickTracking_[poolIdx][i][numTickTracking - 1].exitTimestamp == 0) {

204:         if (lastAccrued != 0) {

233:         if (lastAccrued != 0) {