Timelock duration on upgrades

Spiko'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 timelock on any chain. Data cache confirms governance.timelock_address: null. Tech blog and Arbitrum STEP-2 application both describe direct multisig control with no delay. Upgrades executable immediately on 2-of-5 signatures.

Sources #

Governance
Spiko USTBL Arbitrum STEP-2 applicationArbitrum STEP-2 application: no timelock mechanism mentionedretrieved 2026-05-16
Docs
Spiko smart contracts architecture blogtech.spiko.io: no timelock described; super-admin multisig has full access to upgrade contracts directlyretrieved 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 spiko factor RD-F-032 score red collected_at 2026-05-15 22:52:13