Timelock duration on upgrades
Ethena's assessment for RD-F-032 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No on-chain TimelockController deployed. Data cache confirms timelock_address: null. Docs reference '7-day time-lock for core function changes' conceptually but no smart contract implements this. Admin actions execute immediately after 5-of-11 multisig signatures. Effective timelock = 0 hours.
Sources #
- DocsKey Trust Assumptions | Ethenahttps://docs.ethena.fi/solution-design/key-trust-assumptionsretrieved 2026-04-28
- EthenaMinting.sol — 'No timelock mechanism exists in this contract. Role changes and configuration updates execute immediately.'https://github.com/code-423n4/2023-10-ethena/blob/main/contracts/EthenaMinting.solretrieved 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 ethena factor RD-F-032 score red collected_at 2026-04-28 13:58:51