Gas Optimizations

[code423n4]

[NAZ-G1] Use ++index instead of index++ to increment a loop counter

Context: AxelarGateway.sol#L207, AxelarGasService.sol#L123, AxelarDepositService.sol#L114, AxelarDepositService.sol#L168, AxelarDepositService.sol#L204

Description: Due to reduced stack operations, using ++index saves 5 gas per iteration.

Recommendation: Use ++indexto increment a loop counter.

[NAZ-G2] The Increment In For Loop Post Condition Can Be Made Unchecked

Context: AxelarGateway.sol#L195, AxelarGateway.sol#L207, AxelarGateway.sol#L292, AxelarGasService.sol#L123, AxelarDepositService.sol#L114, AxelarDepositService.sol#L168, AxelarDepositService.sol#L204, AxelarAuthWeighted.sol#L17, AxelarAuthWeighted.sol#L69, AxelarAuthWeighted.sol#L98, AxelarAuthWeighted.sol#L116

Description: (This is only relevant if you are using the default solidity checked arithmetic). i++ involves checked arithmetic, which is not required. This is because the value of i is always strictly less than length <= 2256 - 1. Therefore, the theoretical maximum value of i to enter the for-loop body is `2256 - 2. This means that thei++` in the for loop can never overflow. Regardless, the overflow checks are performed by the compiler.

Unfortunately, the Solidity optimizer is not smart enough to detect this and remove the checks. One can manually do this by:

for (uint i = 0; i < length; i = unchecked_inc(i)) {
    // do something that doesn't change the value of i
}

function unchecked_inc(uint i) returns (uint) {
    unchecked {
        return i + 1;
    }
}

Note that it’s important that the call to unchecked_inc is inlined. This is only possible for solidity versions starting from 0.8.2.

Recommendation: The increment in the for loop post condition can be made unchecked.

[NAZ-G3] Catching The Array Length Prior To Loop

Context: AxelarGateway.sol#L207, AxelarGasService.sol#L123, AxelarDepositService.sol#L114, AxelarDepositService.sol#L168, AxelarDepositService.sol#L204, AxelarAuthWeighted.sol#L17, AxelarAuthWeighted.sol#L98, AxelarAuthWeighted.sol#L116

Description: One can save gas by caching the array length (in stack) and using that set variable in the loop. Replace state variable reads and writes within loops with local variable reads and writes. This is done by assigning state variable values to new local variables, reading and/or writing the local variables in a loop, then after the loop assigning any changed local variables to their equivalent state variables.

Recommendation: Simply do something like so before the for loop: uint length = variable.length. Then add length in place of variable.length in the for loop.

[NAZ-G4] Setting The Constructor To Payable

Context: All Contracts

Description: You can cut out 10 opcodes in the creation-time EVM bytecode if you declare a constructor payable. Making the constructor payable eliminates the need for an initial check of msg.value == 0 and saves 21 gas on deployment with no security risks.

Recommendation: Set the constructor to payable.

[NAZ-G5] Function Ordering via Method ID

Context: All Contracts

Description: Contracts most called functions could simply save gas by function ordering via Method ID. Calling a function at runtime will be cheaper if the function is positioned earlier in the order (has a relatively lower Method ID) because 22 gas are added to the cost of a function for every position that came before it. The caller can save on gas if you prioritize most called functions. One could use This tool to help find alternative function names with lower Method IDs while keeping the original name intact.

Recommendation: Find a lower method ID name for the most called functions for example mostCalled() vs. mostCalled_41q() is cheaper by 44 gas.

[re1ro]

1 - 3

Dup #2

4

Good spot

5

Ack

[GalloDaSballo]

Less than 300 gas saved