defirisk.co
rubric v1.7.0

Timelock duration on upgrades

StakeWise v3'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. governance.timelock_address confirmed null in pipeline data cache. No TimelockController between Snapshot vote passage and Safe execution. The 4-of-7 Safe is the only execution gate; wall-clock latency depends on signer availability only, not a protocol-enforced delay. All upgrade/admin actions can execute immediately upon Safe co-signing.

Sources #

  • Governance
    StakeWise DAO Governance Process — forum.stakewise.ioStakeWise DAO Governance Process: SafeSnap encodes passed proposals directly to Safe queue — no delay module mentionedretrieved 2026-05-16
  • Internal
    StakeWise data cache — governance no timelock confirmed00-data-cache.json sources.governance: timelock_address null, timelock_delay_seconds nullretrieved 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 stakewise factor RD-F-032 score red collected_at 2026-05-16 01:03:28