Timelock duration on upgrades

Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap'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 active on-chain timelock governing any upgrades or sensitive actions. Legacy Timelock (0x9a8541Ddf3a932a9A922B607e9CF7301f1d47bD1) configured with 172,800s (48h) delay but is INACTIVE — last tx 2020-09-27, $0 balance, not wired to current governance. Current governance has zero timelock delay: Snapshot vote → Ops Multisig execution with no on-chain queuing requirement.

Sources #

Internal
00-profile.md §6 Governance TopologyProfile §6: No active on-chain timelock wired to current governance flowretrieved 2026-05-17
Etherscan
Sushi: Timelock — Etherscan (inactive)Legacy Timelock — last tx block 10942452 (2020-09-27), balance $0.03, admin = deployer EOAretrieved 2026-05-17

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 sushi factor RD-F-032 score red collected_at 2026-05-16 19:50:37