Timelock on sensitive actions

Euler V2's assessment for RD-F-033 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Upgrades: 4-day timelock (green). Parameter changes: 48h Wildcard timelock (green). Pause/emergency: bypass timelock by design (emergency role). Oracle config: 48h Wildcard timelock (green). EUL mint: ADMIN_ROLE callable without explicit timelock on mint itself (only supply cap protects). 4 of 5 action types timelocked — mint is the gap.

Sources #

Etherscan
EUL Token — mint() callable by ADMIN_ROLE without timelock0xd9fcd98c322942075a5c3860693e9f4f03aae07b#coderetrieved 2026-05-04
Docs
Euler DAO Vaults Governance Documentationdocs.euler.finance/security/dao-vaults-governance/retrieved 2026-05-04

Methodology #

For each sensitive action category (mint / pause / rescue / setOracle / upgrade), determine whether execution requires going through the declared timelock.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol euler-v2 factor RD-F-033 score yellow collected_at 2026-05-04 19:56:06