Proposal execution delay < 24h

Evidence summary #

Timelock minimum is 2 days (172,800s) per on-chain read; major upgrades use 10-day delays in practice (ELIP-002 slashing used 10-day timelock confirmed via web search). No proposal-to-execution path under 24 hours exists for upgrades. Pause is instant but pause is not a 'proposal' in the governance sense.

Sources #

Methodology #

Determine whether the time between a governance proposal passing and its executability (including any internal delay) is less than 24 hours.

See the full factor methodology and distribution across all protocols →