★ Post-audit code changes without re-audit
ether.fi's assessment for RD-F-139 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
EtherFiNodesManager upgraded 2026-02-02 (impl 0x789CbBe0..., tx 0x9eeb5aca...). Most recent Certora audits: 2026-01-29 (Reaudit Core Contracts) — 4 days before the upgrade — and 2026-01-20 (Liquid-Refer/KING/Cross-Pod). No audit explicitly named for the February 2026 implementation found. The temporal gap means the specific deployed bytecode cannot be confirmed as audited. Partially mitigated by continuous Certora engagement (15 reports in 18 months) and fast cycle time.
Sources #
- AuditCertora 2026-01-29: Reaudit Core Contracts — pre-dates Feb 2026 upgrade by 4 daysCertora Reaudit Core Contracts 2026-01-29retrieved 2026-04-28
- EtherFiNodesManager — upgrade date 2026-02-02EtherFiNodesManager proxy — upgraded to 0x789CbBe0 on 2026-02-02, tx 0x9eeb5aca...retrieved 2026-04-28
Methodology #
Count deployed changes to audited bytecode where no subsequent audit or spot-review covers the changed code.
See the full factor methodology and distribution across all protocols →