Timelock duration on upgrades

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

Evidence summary #

No EVM-style TimelockController documented. Realms DAO (when active) had no confirmed on-chain time-delay between proposal passing and execution beyond the voting period itself. During governance pause, no formal on-chain timelock on team decisions. Program upgrades go through Squads multisig signature threshold only — no time delay. Profile explicitly records has_timelock: false.

Sources #

Docs
Jupiter DAO voting portalProfile §6 notes no timelock documented; governance pause confirms team controlretrieved 2026-04-29
URL
Solana exchange Jupiter pauses DAO voting | DL NewsDL News governance pause — no timelock on team decisionsretrieved 2026-04-29

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 jupiter factor RD-F-032 score red collected_at 2026-04-29 11:51:25