Audit-to-deploy gap
Balancer (v2 + v3)'s assessment for RD-F-006 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
v2: OZ audit ended 2021-03-15; deploy 2021-04-20 = ~36 days (within 60d threshold). v3: Core audits (Certora 2024-09, Spearbit 2024-10-04, ToB 2024-10-08) completed before the Dec 11 2024 launch. However Cantina competition audits (2024-12-17 pre-competition and 2024-12-31 post-competition) straddle and post-date the Dec 11 launch — the post-competition Cantina report completed after launch creates a gap where code was live without the full competition audit complete. This is a yellow condition for v3.
Sources #
- URLBalancer v3 launch date Dec 2024 (The Block)https://www.theblock.co/post/330379/balancer-v3-launches-aaveretrieved 2026-05-05
- Balancer v3 audit reports directoryhttps://github.com/balancer/balancer-v3-monorepo/tree/main/auditsretrieved 2026-05-05
Methodology #
Measure the number of days between the audit report sign-off date and the mainnet deploy of the audited bytecode.
See the full factor methodology and distribution across all protocols →