Timelock duration on upgrades

Axelar Network'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 #

InterchainGovernance minimumTimeLockDelay = 604,800 seconds = 168 hours = 7 days. Verified on-chain from readContract. This is the EVM timelock-equivalent for gateway/governance upgrades. Well above the 48-hour green threshold. CAVEAT: this timelock applies to the gateway upgrade path only. ITS upgrades have NO timelock (direct EOA call — see F027).

Sources #

Docs
EVM Contract Governance — Axelar DocsAxelar EVM governance: InterchainGovernance enforces minimum timelock before proposal executionretrieved 2026-05-17
Etherscan
InterchainGovernance minimumTimeLockDelay — EtherscanInterchainGovernance 0xfDF36A30070ea0241d69052ea85ff44Ad0476a66 readContract: minimumTimeLockDelay()=604800retrieved 2026-05-17

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 axelar factor RD-F-032 score green collected_at 2026-05-16 21:57:49