Timelock duration on upgrades
EigenLayer's assessment for RD-F-032 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Primary timelock MINIMUM_DELAY = 172,800s (48 hours / 2 days) per Etherscan source code read. Foundation docs state 'minimum 10-day delay on safety-critical functions' — major upgrades (ELIP-002 slashing) used 10-day delays in practice. Floor of 2 days (48h) is below the 72h+ threshold expected for a protocol of this TVL; operational standard of 10 days is good. Recorded as ambiguous — curator should confirm which governs.
Sources #
- Etherscanhttps://etherscan.io/address/0xA6Db1A8C5a981d1536266D2a393c5F8dDb210EAFretrieved 2026-04-28
- https://docs.eigenfoundation.org/protocol-governance/technical-architectureretrieved 2026-04-28
Methodology #
Read the timelock delay (in hours) between a queued upgrade proposal and its executable state.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol eigenlayer factor RD-F-032 score yellow collected_at 2026-04-28 13:58:44