Payload to scan. For a transaction, the serialized value from a build endpoint, unchanged. EVM: 0x-prefixed RLP hex; the chain comes from its chain ID. SVM: base58 Solana wire transaction, scanned as mainnet. For EIP-712 typed data, the eth_signTypedData_v4 JSON document as a string, with exactly the top-level keys types, primaryType, domain and message. domain.chainId selects the chain. If EIP712Domain declares no chainId, a bytes32 salt holding a Polygon PoS chain ID is accepted instead, as Polygon meta-transactions use; any other salt returns 400. The document is parsed strictly, and these return 400: duplicate or case-variant keys at any depth; non-integer numbers; struct, field or type names outside [A-Za-z_][A-Za-z0-9_]*; a declared struct other than EIP712Domain that primaryType does not reach; an EIP712Domain that is not an ordered subset of string name, string version, uint256 chainId, address verifyingContract and bytes32 salt; and domain keys that differ from the declared EIP712Domain fields. A document too expensive to hash also returns 400: a struct name, field name or field type over 128 characters, a field type with over 24 array dimensions, over 64 struct types, over 64 fields in a struct, over 1,024 struct values, over 1,048,576 characters of combined encodeType text, or over 8,192 values. Values count struct fields, array elements across every dimension, and every dropped message key with its contents. Message keys a struct does not declare are dropped and not hashed, but they still follow the parsing rules; when any are dropped, the last entry in reasons says how many. The scan runs on a canonical re-serialisation of the document.