Timelock duration on upgrades

OpenEden'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 timelock identified on any chain. Data cache timelock_address: null. The 2025-08-14 vault V5 upgrade was executed directly by the Safe (execTransaction) without routing through any TimelockController. All prior upgrades (2024-12-20, 2024-12-23, 2024-02-15) also show no timelock intermediate. Red: no timelock on upgrades.

Sources #

Etherscan
Vault upgrade tx — no timelockUpgrade tx 0xf162138b — ExecutionSuccess event from Safe directly, no timelock CallExecuted eventretrieved 2026-05-16
Internal
Data cache — timelock_address nullData cache 00-data-cache.json: governance.timelock_address = nullretrieved 2026-05-16

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 openeden factor RD-F-032 score red collected_at 2026-05-16 10:11:45