Timelock on sensitive actions

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

Evidence summary #

DAO proposals: 2-day delay period after vote before on-chain execution. Program upgrades via Squads: no confirmed timelock beyond multi-party signing requirement. Steward pause: no timelock (immediate). Emergency Security Council actions explicitly bypass DAO procedures. Mixed — standard DAO proposals timelocked (48h), emergency paths not.

Sources #

Governance
Jito Foundation Governance ProceduresGovernance procedures: 2-day delay for DAO proposals; Security Council can bypass for emergenciesretrieved 2026-04-29
GitHub
Jito StakeNet Steward Program GitHubSteward program README: admin can pause state machine immediatelyretrieved 2026-04-29

Methodology #

For each sensitive action category (mint / pause / rescue / setOracle / upgrade), determine whether execution requires going through the declared timelock.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol jito factor RD-F-033 score yellow collected_at 2026-04-29 15:50:23