Proposal execution delay < 24h
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-038 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No mandatory on-chain delay between a successful Snapshot vote and execution by the Ops Multisig. Snapshot has a voting period of several days, but after vote closes, Ops Multisig can execute immediately with zero queuing delay. No TimelockController in the execution path. Execution delay post-vote = 0 hours.
Sources #
- DocsSushi Governance DocsSushi governance docs — Snapshot → Ops Multisig execution path described; no timelock queuing step mentionedretrieved 2026-05-17
- 00-profile.md §6Profile §6 — 'No active on-chain timelock is wired to the current governance flow'retrieved 2026-05-17
Methodology #
Determine whether the time between a governance proposal passing and its executability (including any internal delay) is less than 24 hours.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol sushi factor RD-F-038 score red collected_at 2026-05-16 19:50:37