★ Bridge ecrecover checks result ≠ address(0)
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-151 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
[★ CRITICAL — NOT APPLICABLE] Sushi operates no bridge message verification code. SushiXSwap does not perform ecrecover on cross-chain messages — all signature verification is handled internally by Stargate/LayerZero. No Sushi-authored bridge verifier contract exists. Factor applies to bridge operators who implement their own message verification.
Sources #
- GitHubSushiXSwap v2 GitHub — adapter-only architecturesushiswap/sushixswap-v2 — StargateAdapter and SquidAdapter are routing wrappers; no bridge verifier code authored by Sushiretrieved 2026-05-17
Methodology #
Determine whether the bridge verifier code rejects `ecrecover` returns of `address(0)`.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol sushi factor RD-F-151 score not_applicable collected_at 2026-05-16 19:50:37