Timelock duration on upgrades
Jito'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 #
No standalone on-chain TimelockController identified. SPL Governance has a 2-day delay period post-vote before on-chain execution. Squads V4 has optional timelock feature but Jito's configuration is not confirmed publicly. Emergency Security Council actions explicitly bypass DAO vote procedure. 2-day delay for standard DAO proposals; no delay for emergency paths.
Sources #
- DocsSquads V4 ProtocolSquads V4 timelock feature available but Jito configuration unconfirmedretrieved 2026-04-29
- Jito Foundation Governance ProceduresJito governance procedures: 2-day delay period documented after vote before executionretrieved 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 jito factor RD-F-032 score yellow collected_at 2026-04-29 15:50:23