Signed/unsigned arithmetic confusion

Evidence summary #

Solidity 0.8.x built-in overflow checks mitigate most signed/unsigned confusion at compile time. Protocol uses uint256 throughout for amounts and indices. Certora FV and Prototech invariant tests cover arithmetic correctness. No evidence of signed/unsigned casting issues.

Sources #

Methodology #

Determine whether signed-integer conversions or comparisons where unsigned was intended exist in the deployed bytecode/source.

See the full factor methodology and distribution across all protocols →