Timelock duration on upgrades

Orca's assessment for RD-F-032 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Squads v4 on-chain time_lock field = 86400 seconds = exactly 24 hours. Per methodology: green >=48h, yellow 24-47h, red <24h. At the yellow/green boundary — 24h is yellow. Timelock is genuine and on-chain verified (not a docs-only claim).

Sources #

Docs
Squads v4 source — vault PDA System Program ownership by designhttps://github.com/Squads-Protocol/v4retrieved 2026-05-16
Internal
Data cache — verified Squads v4 time_lock=86400scache sources.solana_multisigs[0]: verified_time_lock_seconds=86400, retrieved_at=2026-05-16T02:13:34Zretrieved 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 orca factor RD-F-032 score yellow collected_at 2026-05-16 02:39:16