Timelock duration on upgrades

Evidence summary #

24-hour timelock declared for program upgrades via Squads V4. This is the minimum review window before an upgrade can execute. 24h is shorter than best-practice recommendation of 48-72h but is meaningful. The timelock is enforced by the Squads protocol's transaction expiration mechanism, not a separate on-chain TimelockController.

Sources #

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 →