Signed/unsigned arithmetic confusion

Evidence summary #

Solidity 0.6.12 contracts use SafeMath throughout (imported and applied to all arithmetic). SafeMath prevents overflow/underflow but does not prevent all signed/unsigned confusion. However, the contracts use exclusively uint256 for all financial calculations — no signed int conversions found in source inspection of Booster, CvxLockerV2, BaseRewardPool. Low confidence without symbolic execution.

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 →