EIP-712 domain separator missing chainId

Evidence summary #

The Feb 2026 Deposit Flow audit identified an EIP-712 replay vulnerability in CounterfactualDepositSpokePool where the signed struct (`EXECUTE_DEPOSIT_TYPEHASH`) excludes route-specific fields but the domain separator is not the issue — the issue is in the struct payload binding, not the domain separator itself. The domain separator in standard OZ EIP-712 does include chainId. The unresolved medium is about struct-level replay (same signature reusable across routes), not missing chainId in do...

Sources #

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 →