Signed/unsigned arithmetic confusion
Beefy Finance's assessment for RD-F-018 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Core vault uses uint256 throughout; no signed/unsigned confusion found in source inspection. CLM strategies use int24 ticks (Uniswap v3) requiring careful signed/unsigned handling. Zellic critical finding is adjacent to this. Symbolic analysis not performed. Marked gray pending tool run.
Sources #
- GitHubBeefyVaultV7.solBeefyVaultV7.sol — uint256 throughout vault layer; no signed arithmeticretrieved 2026-05-16
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 →
rubric_version v1.7.0 protocol beefy factor RD-F-018 score gray collected_at 2026-05-16 13:10:30