Bridge validator count (M)
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-148 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Sushi does not operate its own bridge validator set. SushiXSwap delegates to Stargate v2 (LayerZero v2 infrastructure) with 2/2 required DVNs (Nethermind + LayerZero Labs). Sushi has no visibility or control over the validator set. Factor applies to bridge operators; Sushi is a bridge consumer/router.
Sources #
- InternalSushi profile §7 bridge surface scopingrisk-dashboard/.research/protocols/sushi/00-profile.md §7 — is_a_bridge: falseretrieved 2026-05-17
- L2Beat: Stargate v2 bridgeL2Beat Stargate v2 — validator/DVN configuration details; Sushi is a consumer of Stargate, not an operatorretrieved 2026-05-17
Methodology #
Count the number of distinct validators or signers in the bridge's signer set (for non-LZ bridges; use F179 for LayerZero OFT).
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol sushi factor RD-F-148 score not_applicable collected_at 2026-05-16 19:50:37