External keeper/relayer not redundant
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-062 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
SushiXSwap cross-chain routing relies on Stargate's executor infrastructure (LayerZero v2 executor network) to relay cross-chain messages. Sushi does not operate its own executor or relayer. If Stargate's executor fails or is paused, cross-chain SushiXSwap transactions may not complete and funds in transit may be temporarily frozen. A second adapter (Squid/Axelar) provides some routing diversity but not at the execution layer level. AMM core has no keeper dependency.
Sources #
- URLL2Beat: Stargate v2 bridgeL2Beat Stargate v2 — permissioned verifiers (Nethermind + LZ Labs); single executor architectureretrieved 2026-05-17
- SushiXSwap v2 GitHubsushiswap/sushixswap-v2 — StargateAdapter confirms Sushi delegates execution to Stargateretrieved 2026-05-17
Methodology #
Determine whether the protocol depends on a single keeper or relayer (Gelato, Chainlink Automation, custom) with no redundancy or failover.
See the full factor methodology and distribution across all protocols →