walletpermissions
Request types · Uniswap Permit2 contract

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

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

  • Step 1 is an ordinary ERC-20 approve to the Permit2 contract. Uniswap’s docs note it is “commonly for the maximum uint256 amount”.
  • Step 2 is a signature. For PermitSingle or PermitBatch, read each token’s amount and expiration, the spender, and sigDeadline. For PermitTransferFrom, read the token, the amount and deadline.

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 amount until “the allowance is exhausted or expires.”
  • SignatureTransfer: “a single, nonce-scoped transfer through one signature”, which “leaves no standing allowance.”
  • PermitBatch covers 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; sigDeadline limits when a signature can be submitted; expiration is 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 its lockdown function, which the source describes as “batch revoking approvals”, sets allowances to 0.
  • invalidateNonces cancels unused allowance signatures; invalidateUnorderedNonces does 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 PermitBatch signature can list many tokens. Read every entry, not just the first, and check each expiration.
Fictional practice

Practice question

Fictional Lanternfly Swap asks for a Permit2 signature.

Fictional request card
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:

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

Sources

  1. Permit2 overview. Uniswap developer docs. Page as published on the check date. Checked 2026-11-04.
  2. Permit2 source: IAllowanceTransfer, ISignatureTransfer, Allowance library. Uniswap/permit2 on GitHub. main branch on the check date. 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.