Cally contest - 0xNazgul's results

Use ++index instead of index++ to increment a loop counter

Context: CallyNft.sol#L236-L250

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

Recommendation: Use ++index to increment a loop counter.

Same State Variable Read More Than Once

Context: Cally.sol#L158-L201 (For L168 & L169), Cally.sol#L258-L297 (For L283 & L284)

Description: Functions that read state variables more than once can save gas by casting it to memory

Recommendation: It's best to cast the state variables into memory when read more than once.

Catching The Array Length Prior To Loop

Context: CallyNft.sol#L236-L250

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.

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.