Signed/unsigned arithmetic confusion
Yearn Finance's assessment for RD-F-018 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Vyper 0.3.7 (V3) and Vyper 0.2.x/0.3.3 (V2) enforce strict integer types at the language level and do not permit implicit signed/unsigned mixing. Risk is architecturally lower than Solidity by language design. No published audit finding of signed/unsigned confusion in V2 or V3.
Sources #
- URLVyper language — strict integer types, no implicit signed/unsigned conversionVyper language type system documentationretrieved 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 yearn-finance factor RD-F-018 score green collected_at 2026-05-16 08:34:32