Formal verification coverage
StakeWise v3's assessment for RD-F-009 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No formal verification found — no Certora, Halmos, Kani, or equivalent tooling directories exist in the v3-core repository. The repo contains only a slither.config.json for static analysis. Per U8 rule: LST at ~$795M TVL with zero formal verification scores red even with 5+ traditional audits (Rocket Pool precedent). Profile §8 explicitly flagged this gap for code-security-analyst.
Sources #
- InternalStakeWise protocol profile §8 — formal verification gap flagProfile §8 explicitly states: 'No formal verification (Certora, Halmos, Kani, or equivalent) was found as of 2026-05-16. Searched: Certora SecurityReports GitHub, Halmos documentation, StakeWise v3-core GitHub'retrieved 2026-05-16
- StakeWise v3-core GitHub repository rootv3-core repository root — no certora/, halmos/, kani/ or .fv/ directories present; slither.config.json present (static analysis only)retrieved 2026-05-16
Methodology #
Determine the percentage of protocol-declared critical invariants covered by a formal verification proof (Certora Prover, Kani, Halmos, or equivalent).
See the full factor methodology and distribution across all protocols →