# Typed-data signature (eth_signTypedData_v4)

> A request to sign structured data. What the signature authorizes depends on the contract or service that will check it.

- Request: `eth_signTypedData_v4`
- Standard: EIP-712
- Track: Request types
- Checked against sources: 2026-11-04
- Review status: drafted with AI assistance, awaiting human review
- Canonical page: https://walletpermissions.com/learn/requests/sign-typed-data

Education only. This does not assess any real request, wallet or app, and is not advice to sign or not sign. Every app, token and address in the practice card is fictional.

## What to read in the prompt

- The domain: `name`, `chainId` and especially `verifyingContract`. EIP-712: “the address of the contract that will verify the signature.”
- The primary type, such as `Permit` or an order, and every amount, recipient, deadline and nonce in the message.
- MetaMask’s docs say “the top-level struct type’s name and the `domain.name` are presented to the user prominently in the confirmation.” Both are chosen by whoever built the request.

## What it lets the other party do

- It produces a signature that a contract or server can verify. Depending on the primary type it can be a token permit, a marketplace order, a vote or a login.
- Whoever holds the signature can try to use it. EIP-712 warns that an attacker can intercept a signature “and submits it to the contract before the original intended use takes place.”

## What it does not do

- Signing is not itself an on-chain transaction and costs no gas.
- EIP-712 does not prevent replays on its own: “It does not include replay protection.” That is left to each application.

## How long it lasts

- There is no general rule. Look for deadline, expiry and nonce fields in the message. If there are none, ask how the receiving contract limits it.

## How to undo it

- There is no universal cancel. Some protocols provide a cancel or nonce function. If the signature has already created an allowance, remove it like any allowance and check with Revoke.cash or Etherscan’s token approval checker.

## A pattern to recognise

- A familiar name in the domain with an unfamiliar verifying contract. The name is free text; the verifying contract is what checks the signature.

## Practice question (fictional)

Fictional Kiteframe Market asks you to sign a listing.

| Field | Value |
| --- | --- |
| Request type | Signature: eth_signTypedData_v4 |
| Domain name | Kiteframe Market |
| Primary type | Order |
| You offer | 1 Paper Heron (fictional NFT) |
| You receive | 0.0001 fictional ETH |

**Question:** Because signing costs no gas, is it impossible for this signature to move your heron?

**Answer:** No. A signed order is meant to be submitted to a marketplace contract, which can then transfer the heron on the stated terms. No gas at signing time says nothing about what happens when someone submits it.

## Check your real account elsewhere

This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements):

- [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks
- [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet

## Sources

- [EIP-712: Typed structured data hashing and signing](https://eips.ethereum.org/EIPS/eip-712). Ethereum EIPs. Final; created 2017-09-12. Checked 2026-11-04.
- [Sign data (eth_signTypedData_v4 and personal_sign)](https://docs.metamask.io/metamask-connect/evm/guides/sign-data/). MetaMask developer docs. Page as published on the check date. Checked 2026-11-04.
- [ERC-191: Signed Data Standard](https://ercs.ethereum.org/ERCS/erc-191). Ethereum ERCs. Final; created 2016-01-20. Checked 2026-11-04.
