Audit-to-deploy gap

ether.fi'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 #

No signed git release tags exist. Exact audit-end-to-deploy lag cannot be computed programmatically. Temporal clustering of Certora reports and profile-noted upgrade dates (EtherFiNodesManager impl 2026-02-02, weETH impl 2025-08-07) suggests features are deployed within ~60 days of the associated FV report. Cannot confirm precisely without curator cross-referencing Certora report dates to deployment transaction timestamps.

Sources #

GitHub
No signed release tags in repoetherfi-protocol/smart-contracts releases (empty)retrieved 2026-04-28
Etherscan
EtherFiNodesManager impl upgrade 2026-02-02 (per profile §2)EtherFiNodesManager 0x8B71140AD2e5d1E7018d2a7f8a288BD3CD38916Fretrieved 2026-04-28

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 ether-fi factor RD-F-006 score yellow collected_at 2026-04-28 13:58:46