Bridge rate-limiter / chain-pause as positive mitigant
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-185 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Factor measures bridge rate-limiter / chain-pause as positive mitigant. Sushi is not a bridge operator — SushiXSwap routing uses Stargate/LayerZero (third-party). No Sushi-controlled rate-limiter or chain-pause mechanism applies to core DEX AMM. The protocol is a DEX, not a bridge. Factor is not applicable to this protocol type.
Sources #
- Internal00-profile.md §7Profile §7 — 'Sushi does not operate its own canonical bridge; SushiXSwap delegates bridging to Stargate/LayerZero'retrieved 2026-05-17
Methodology #
Determine whether the bridge implements a per-window outflow rate-limiter (and at what cap), and whether the protocol team can trigger a chain-level or validator-set emergency pause.
See the full factor methodology and distribution across all protocols →