EIP-712 Typed Data Hash

Paste typed data JSON with types, primaryType, domain and message. The tool computes the domain separator, the struct hash and the final digest that is signed.

Use the tool

Why this tool exists

Typed data signatures show readable fields in a wallet prompt instead of an opaque hash, and they are used for permits, order books, gasless transactions and DAO votes. On the contract side, the digest must be rebuilt exactly, and a small difference in a type string, field order or an address casing yields a different hash and a signature that fails to verify. This tool takes the same JSON a dapp sends to eth_signTypedData_v4 and shows the encoded type, the type hash, the domain separator, the hash of the message struct and the final signing digest. It handles nested structs, arrays, fixed-size bytes and integers with range checks. It runs in your browser, produces no signature and never needs a private key.

How to use it

  1. Paste the typed data JSON, or use the Mail example already loaded.
  2. Run the tool.
  3. Compare the domain separator, struct hash and digest with your contract or library.

Frequently asked questions

What goes into the final digest?

keccak256 of 0x1901, followed by the 32-byte domain separator and the 32-byte hash of the message struct. This is the value the wallet signs.

What if my JSON has no EIP712Domain type?

The tool builds it from the domain fields present, in the standard order: name, version, chainId, verifyingContract and salt. Supply the type yourself for a non-standard domain.

Which types are supported?

Structs, arrays (fixed or dynamic), string, bytes, bytesN, address, bool and intN/uintN with range checks. Values outside a type's range or the wrong byte length raise an error.

Does it sign or verify a signature?

No. It only computes hashes. Never paste private keys into a web page; to check a signature, use a verifier with the digest it gives you.