Bridge binds message to srcChainId
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-152 — 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 implement cross-chain message validation. srcChainId binding is handled internally by Stargate/LayerZero message protocol. Sushi has no message struct or verifier that could fail to bind srcChainId.
Sources #
- GitHubSushiXSwap v2 GitHubsushiswap/sushixswap-v2 — routing adapter contracts; no message struct with srcChainId authored by Sushiretrieved 2026-05-17
Methodology #
Determine whether the bridge message struct includes `srcChainId` and the verifier enforces per-chain separation.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol sushi factor RD-F-152 score not_applicable collected_at 2026-05-16 19:50:37