Permit2 approvals and signatures
A shared approval contract. You approve the Permit2 contract once per token, then sign messages that give individual spenders an amount and an expiration, or a one-time transfer.
Request: approve(Permit2) then PermitSingle, PermitBatch or PermitTransferFrom signatures
What to read in the prompt
- Step 1 is an ordinary ERC-20
approveto the Permit2 contract. Uniswap’s docs note it is “commonly for the maximumuint256amount”. - Step 2 is a signature. For
PermitSingleorPermitBatch, read each token’samountandexpiration, thespender, andsigDeadline. ForPermitTransferFrom, read the token, the amount anddeadline.
What it lets the other party do
- AllowanceTransfer: Uniswap describes it as “a standing, time-bound allowance inside the Permit2 contract”. The spender can transfer up to
amountuntil “the allowance is exhausted or expires.” - SignatureTransfer: “a single, nonce-scoped transfer through one signature”, which “leaves no standing allowance.”
PermitBatchcovers several tokens in one signature.
What it does not do
- A Permit2 allowance does not outlive its
expiration. - Permit2 can only move tokens you have approved the Permit2 contract for.
How long it lasts
- Three different limits: the ERC-20 approval to Permit2 has no expiry;
sigDeadlinelimits when a signature can be submitted;expirationis when the allowance stops working. - In Permit2’s source, an expiration of 0 means the allowance “only lasts the duration of the block.”
How to undo it
- Permit2’s
approve(token, spender, 0, 0)or itslockdownfunction, which the source describes as “batch revoking approvals”, sets allowances to 0. invalidateNoncescancels unused allowance signatures;invalidateUnorderedNoncesdoes the same for one-time transfer signatures.- Setting the underlying ERC-20 approval to Permit2 to 0 stops all Permit2 spending of that token. Revoke.cash or Etherscan’s token approval checker can show both layers.
A pattern to recognise
- One
PermitBatchsignature can list many tokens. Read every entry, not just the first, and check each expiration.
Practice question
Fictional Lanternfly Swap asks for a Permit2 signature.
- Request type
- Signature: PermitSingle
- Token
- MOSS (fictional)
- Amount
- 500 MOSS
- Expiration
- 30 days from now
- Spender
- Lanternfly Router (fictional contract)
- sigDeadline
- 30 minutes from now
If the router does not submit this signature within 30 minutes, can it still use it next week?
Show the answer
Answer: No. sigDeadline is the last moment the signature can be submitted. The 30-day expiration only matters if the signature was submitted in time.
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:
- Revoke.cash: shows and removes token approvals across many networks
- Etherscan token approval checker: shows and removes token approvals on Ethereum mainnet
Independent tools, not affiliated with this site. Linking is not an endorsement or a safety assessment.
Sources
- Permit2 overview. Uniswap developer docs. Page as published on the check date. Checked 2026-11-04.
- Permit2 source: IAllowanceTransfer, ISignatureTransfer, Allowance library. Uniswap/permit2 on GitHub. main branch on the check date. Checked 2026-11-04.
- 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.