Timelock duration on upgrades

Aave v3'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 #

Executor Lvl1: 86,400 seconds (1 day). Executor Lvl2: 604,800 seconds (7 days). Both exceed 24h threshold; Lvl2 far exceeds 48h. Legacy Executor (0x79426A1c) is INACTIVE (IAaveGovernanceV2 interface, 1 tx from 2023); active Lvl2 is 0x17Dd33Ed confirmed by GovernanceV3Ethereum.sol.

Sources #

GitHub
Aave Address Book - GovernanceV3EthereumGovernanceV3Ethereum.solretrieved 2026-04-27
URL
Etherscan - Legacy Aave Executor (GovernanceV2)Legacy Executor V2 source - MINIMUM_DELAY=604800retrieved 2026-04-27

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 aave-v3 factor RD-F-032 score green collected_at 2026-04-27 23:28:46