Code complexity vs audit coverage
Rocket Pool's assessment for RD-F-024 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Large codebase (20+ contracts, 48.7% Solidity per GitHub statistics). Houston Consensys Diligence engagement was explicitly time-boxed at 2x10 person-days with recommended follow-up — indicating audit scope was narrow relative to codebase size. Saturn One complexity (megapools, 4 ETH bonding, express/standard queues, RPL fee switch) is high; three firms engaged. No LOC/nSLOC count publicly available to compute exact ratio.
Sources #
- GitHub
- Rocket Pool Houston | Consensys DiligenceConsensys Diligence Houston audit — 2x10 person-days, time-boxed, recommended follow-upretrieved 2026-05-04
Methodology #
Determine whether the cyclomatic complexity or LOC-per-audit-day ratio exceeds the curator-declared credibility threshold for the audit to be meaningful.
See the full factor methodology and distribution across all protocols →