Timelock duration on upgrades
Euler V2's assessment for RD-F-032 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Admin Timelock (0xBfeE): 172,800s (48h). eVault Factory Timelock (0xfb034): 345,600s (4 days). EUL DAO Timelock (0xd4Ee): 172,800s (48h). Wildcard Timelock (0x1b8C): ~172,800s (48h per docs). All >=48h green threshold.
Sources #
- EtherscanEUL DAO Timelock — minDelay 172800s (48h)0xd4Ee8939a537D943a4E46E7Ae04069C9451d724F constructor minDelay=172800retrieved 2026-05-04
- Euler DAO Vaults Governance Documentationdocs.euler.finance/security/dao-vaults-governance/retrieved 2026-05-04
- Euler Admin Timelock — minDelay 172800s (48h)0xBfeE2D937FB9223FFD65b7cDF607bd1DA9B97E59 constructor minDelay=172800retrieved 2026-05-04
- eVault Factory Timelock — minDelay 345600s (4 days)0xfb034c1C6c7F42171b2d1Cb8486E0f43ED07A968 constructor minDelay=345600retrieved 2026-05-04
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 euler-v2 factor RD-F-032 score green collected_at 2026-05-04 19:56:06