Guardian/pause-keeper distinct from upgrader
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-034 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No formal pause-keeper or guardian role distinct from Ops Multisig identified. Core AMM contracts (V2/V3 factories, routers) are non-pauseable by design. BentoBox has no pause function. No emergency guardian role found with distinct address and distinct authority. The only emergency mechanism is CORE team deciding not to execute a Snapshot vote result.
Sources #
- DocsSushi Governance DocsSushi docs governance — no mention of distinct guardian or pause-keeper roleretrieved 2026-05-17
- 00-profile.md §6Profile §6 — no guardian/pause-keeper role listed in governance topologyretrieved 2026-05-17
Methodology #
Determine whether a pauser/guardian role exists and is held by an address distinct from the upgrader address.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol sushi factor RD-F-034 score red collected_at 2026-05-16 19:50:37