Security-Council threshold reduction (RT)
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-182 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
T-09 phase-2 signal (v1.1 candidate from batch-24). Signal: bridge/protocol Security Council multisig executes threshold reduction, timelock removal, or new-signer addition within ≤14 days of any of the above. Sushi does not have a formal Security Council in the Drift Protocol sense. Nearest equivalents: Ops Multisig (3-of-5, threshold=3, owner_count=5 per data-cache) and Treasury Multisig (4-of-6, threshold=4, owner_count=6 per data-cache). Neither multisig has had a threshold reduction event. The June 2024 Sushi Labs restructuring transferred treasury control to Sushi Labs but maintained the same threshold configurations. No Security Council threshold change event detected.
Sources #
- InternalSushi data cache — safe_multisigs configuration (2026-05-16)00-data-cache.json safe_multisigs — Ops: threshold=3, owner_count=5; Treasury: threshold=4, owner_count=6retrieved 2026-05-16
- SushiSwap evolves into Sushi Labs — CryptoBriefingSushi Labs DAO overhaul — governance restructure June 2024; multisig threshold configurations unchangedretrieved 2026-05-17
Methodology #
Detect in real-time whether the bridge/protocol Security Council multisig executes a threshold reduction (e.g. 3/5 → 2/5), timelock removal, or new-signer addition within ≤14 days of either of those events.
See the full factor methodology and distribution across all protocols →