Bridge binds message to srcChainId
Hyperliquid's assessment for RD-F-152 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Domain separator in Signature.sol includes block.chainid: abi.encode(EIP712_DOMAIN_SEPARATOR, keccak256(bytes('Exchange')), keccak256(bytes('1')), block.chainid, VERIFYING_CONTRACT). Messages are EIP-712 typed and chain-bound. Cross-chain replay of Bridge2 messages is not possible.
Sources #
- URLSignature.sol — hyperliquid-dex/contracts (raw GitHub)Signature.sol — makeDomainSeparator with block.chainidretrieved 2026-04-28
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 hyperliquid factor RD-F-152 score green collected_at 2026-04-28 13:58:49