walletpermissions
Request types · ERC-2612 (uses EIP-712)

Permit signature (EIP-2612)

An off-chain signature that sets an ERC-20 allowance once anyone submits it to the token contract. Signing costs no gas, but the result is a normal allowance.

Request: eth_signTypedData_v4 with primaryType "Permit"

Education only: this page does not assess any real request, wallet or app, and is not advice to sign or not sign. Checked against the sources below on November 4, 2026. Drafted with AI assistance and awaiting human review against the cited standards. Markdown version

What to read in the prompt

  • It arrives as a signature request, not a transaction.
  • The primary type Permit and the domain’s verifying contract, which is the token.
  • The fields spender, value and deadline.

What it lets the other party do

  • ERC-2612: a call to permit(...) “will set allowance[owner][spender] to value”. The EIP adds: “The caller of the permit function can be any address.”
  • Once submitted, the spender can use transferFrom like any approval.

What it does not do

  • It cannot be submitted after deadline: the current block time must be “less than or equal to deadline.”
  • Each permit uses your current nonce for that token and increases it by 1, so it cannot be used twice.
  • It only works on tokens that implement EIP-2612.

How long it lasts

  • There are two clocks. The deadline limits when the signature can be submitted. The allowance it creates has no expiry, like any ERC-20 allowance.

How to undo it

  • Before it is submitted: EIP-2612 defines no cancel function. Its security notes say that if the signer submits a permit themselves, that “can render previously signed Permits invalid”, because the nonce moves on.
  • After it is submitted: approve(spender, 0), then check with Revoke.cash or Etherscan’s token approval checker.

A pattern to recognise

  • A no-gas “sign to continue” step can still create an allowance. Look for Permit in the primary type and read the spender and value.
Fictional practice

Practice question

Fictional Orchard asks you to sign a message so you can skip an approval transaction.

Fictional request card
Request type
Signature: eth_signTypedData_v4
Primary type
Permit
Token
LEAF (fictional)
Spender
Orchard Vault (fictional contract)
Value
1,000,000 LEAF
Deadline
30 minutes from now

If Orchard submits this within 30 minutes, does the allowance end when the 30 minutes are up?

Show the answer

Answer: No. The deadline only limits when the signature can be submitted. Once submitted, the 1,000,000 LEAF allowance has no expiry until it is used up or set to 0.

Check your real account elsewhere

This site never connects to a wallet and never asks for an address. To see or remove approvals on a real account, use an established tool:

Independent tools, not affiliated with this site. Linking is not an endorsement or a safety assessment.

Sources

  1. ERC-2612: Permit Extension for EIP-20 Signed Approvals. Ethereum ERCs. Final; created 2020-04-13. Checked 2026-11-04.
  2. EIP-712: Typed structured data hashing and signing. Ethereum EIPs. Final; created 2017-09-12. Checked 2026-11-04.
  3. ERC-20: Token Standard. Ethereum ERCs. Final; created 2015-11-19. Checked 2026-11-04.

Quotes are from these sources. Found an error? Corrections are logged publicly on the changelog.