Deployed bytecode matches signed release tag
Liquity V1 + V2 (LUSD / BOLD)'s assessment for RD-F-136 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
v2 launched 2025-05-19 from audited codebase. Dedaub cantina-fixes review (May 13 2025) covered post-contest remediation; launch followed within 6 days. v2 addresses/1.json provides ground-truth deployment addresses matching GitHub main branch. Immutable post-deploy — no bytecode divergence possible.
Sources #
- GitHubLiquity v2 Mainnet Addressesbold/contracts/addresses/1.json — canonical addresses matching audited codebaseretrieved 2026-05-16
- Dedaub Liquity v2 Cantina Fixes ReviewDedaub Liquity v2 Cantina Fixes Review — May 13 2025; covers post-contest remediation before May 19 relaunchretrieved 2026-05-16
Methodology #
Determine whether the deployed runtime bytecode corresponds to a signed git tag in the protocol's repository.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol liquity factor RD-F-136 score green collected_at 2026-05-16 10:35:50