Audit-to-deploy gap
mETH Protocol's assessment for RD-F-006 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
v3 LiquidityBuffer: audits Oct 20-22 2025 (Exvul/Blocksec/Hexens), deployed Oct 24 2025 (block 23645928) — gap of 2-4 days. v2 cmETH: Hexens Aug 31, Secure3 Sept 11 2024, with L1cmETHAdapter deployed Aug 2 2024 (pre-audit for some v2 audits, post-audit for others). v1 core: Hexens Aug 25 2023, MixBytes Oct-Nov 2023, Staking proxy live Nov 2023. No systematic >180-day audit-to-deploy gap.
Sources #
- EtherscanmETH LiquidityBuffer Proxy — Etherscan deployment dateLiquidityBuffer proxy deployed block 23645928, Oct 24 2025retrieved 2026-05-16
- mETH Protocol Security Audits — audit datesExvul Oct 20, Blocksec Oct 21, Hexens Oct 22, MixBytes Nov 13 2025 — all within 2-4 days of LiquidityBuffer deploymentretrieved 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 →
rubric_version v1.7.0 protocol meth-protocol factor RD-F-006 score green collected_at 2026-05-16 02:17:50