EIP-712 domain separator missing chainId

Axelar Network's assessment for RD-F-020 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

AxelarGateway uses a custom non-EIP-712 signing scheme for cross-chain command verification. The gateway message format uses ecrecover on a custom message format where chain binding is enforced at the Axelar consensus layer, not via EIP-712 chainId in a domain separator. No EIP-712 DOMAIN_SEPARATOR pattern found in deployed core contracts. This factor is structurally not applicable to Axelar's custom command-signing architecture.

Sources #

GitHub
AxelarGateway - Non-EIP-712 Signing SchemeAxelarGateway.sol: no EIP-712 domain separator defined; custom ecrecover-based command verificationretrieved 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 axelar factor RD-F-020 score not_applicable collected_at 2026-05-16 21:57:49