Signed/unsigned arithmetic confusion
Jupiter'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 #
Signed/unsigned arithmetic confusion check requires static analysis on source. Rust has stricter type safety than Solidity but the risk still exists. Closed-source binary prevents verification. Gray.
Sources #
- Curator noteprocess-learnings.md §Non-EVM / L1-nativeNon-EVM template: source not available; Rust type safety reduces but does not eliminate riskretrieved 2026-04-29
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 jupiter factor RD-F-018 score gray collected_at 2026-04-29 11:51:25