★ Post-audit code changes without re-audit
Liquity V1 + V2 (LUSD / BOLD)'s assessment for RD-F-139 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
v2 February 2025 Stability Pool vulnerability triggered complete re-audit before the May 2025 relaunch. Patched code audited by: Dedaub (Nov 2024, cantina-fixes May 2025), ChainSecurity (core through May 2025, governance Jan 2025), Coinspect v2 core (Dec 2024), Coinspect governance (Jan 2025), Certora FV (Dec 2024), Cantina 5-week competition (Mar-Apr 2025 with 800+ researchers). All changes before the May 2025 relaunch are covered by at least one audit. Post-relaunch: immutable contracts; no further changes deployable.
Sources #
- URLAuditing Liquity v2 — Liquity BlogLiquity auditing v2 blog post — comprehensive audit chain for all v2 changes before relaunchretrieved 2026-05-16
- Dedaub Liquity v2 Cantina Fixes ReviewDedaub cantina-fixes review May 13 2025 — covers post-contest remediation deployed at v2 relaunchretrieved 2026-05-16
Methodology #
Count deployed changes to audited bytecode where no subsequent audit or spot-review covers the changed code.
See the full factor methodology and distribution across all protocols →