Audit-to-deploy gap
QuickSwap'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 #
V3 Algebra core: C4 contest ended Oct 1, 2022; QuickSwap V3 launched Oct 7, 2022 — gap of ~6 days (green). ABDK+Hexens pre-launch audits: blog published Aug 16, 2022, V3 launched Oct 7, 2022 — gap ~51 days (green). V2 core: ABDK FV completed Apr 2020; V2 Factory deployed Oct 2020 — gap ~6 months (>60d, red threshold). Mixed picture: V3 gap is clean, V2 gap exceeds threshold. Scored yellow overall as V2's gap is historical and the code is now immutable.
Sources #
- EtherscanQuickSwap V2 Factory PolygonscanV2 Factory deploy Oct 2020 (6 months after ABDK Apr 2020)retrieved 2026-05-16
- Code4rena 2022-09 QuickSwap ReportC4 contest Sep 26 - Oct 1, 2022 (6 days before V3 launch)retrieved 2026-05-16
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 →