EIP-712 domain separator missing chainId
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-020 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Core AMM contracts (v2/v3 factory, SushiXSwap v2) don't appear to use EIP-712 domain separators in reviewed source. If EIP-712 is used in peripheral contracts (MasterChef staking, xSUSHI, SUSHI token permit), chainId inclusion cannot be verified without a complete tool run on all peripheral contracts. Peripheral contracts not reviewed in this pass.
Sources #
- GitHubSushiXSwapV2.sol raw sourceSushiXSwapV2.sol — no EIP-712 domain separator visible in constructor or contract bodyretrieved 2026-05-17
Methodology #
Determine whether the EIP-712 domain separator struct omits the `chainId` field, allowing cross-chain replay.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol sushi factor RD-F-020 score gray collected_at 2026-05-16 19:50:37