Wallets & keys · EIP-712 typed data
Sign structured data
Sign a structured request, such as a permit, an order or a vote, the way apps ask wallets to.
Domain, types & value
Three JSON blocks describe exactly what you're signing.
Identifies the app and contract this signature is scoped to.
The shape of the struct being signed.
The actual data, matching the shape above.
Nothing signed yet
Compute a hash, or sign with your wallet, and the result appears here.
About this tool
EIP-712 typed data signing lets an app ask your wallet to sign a structured object instead of a raw string, so the wallet can show readable fields. The signature covers a domain (app name, version, chain ID and verifying contract), the type definitions and the value. Paste all three as JSON, compute the EIP-712 hash, then sign with your wallet through eth_signTypedData_v4 and check the recovered signer.
Common questions
What is an EIP-712 domain separator?
It is the hash of the domain object: the app name, version, chain ID and verifying contract. It is part of every signed digest, so a signature made for one app, contract or chain is rejected by any other.
Is it safe to sign EIP-712 messages?
Only when you trust the app and understand the fields. A Permit or Permit2 signature can let someone move your tokens without another transaction, so read the spender, amount and deadline before you sign. Computing the hash here needs no wallet.
Should EIP712Domain be in the types JSON?
No. Leave it out. ethers.js, which this tool uses, builds the domain type from the domain object you provide and rejects a types object that also defines EIP712Domain.