# 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`
- Standard: Uniswap Permit2 contract
- 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/permit2

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

- 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.

## Practice question (fictional)

Fictional Lanternfly Swap asks for a Permit2 signature.

| Field | Value |
| --- | --- |
| 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 |

**Question:** If the router does not submit this signature within 30 minutes, can it still use it next week?

**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 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

- [Permit2 overview](https://developers.uniswap.org/docs/protocols/permit2/overview). Uniswap developer docs. Page as published on the check date. Checked 2026-11-04.
- [Permit2 source: IAllowanceTransfer, ISignatureTransfer, Allowance library](https://github.com/Uniswap/permit2). Uniswap/permit2 on GitHub. main branch on the check date. Checked 2026-11-04.
- [ERC-20: Token Standard](https://ercs.ethereum.org/ERCS/erc-20). Ethereum ERCs. Final; created 2015-11-19. Checked 2026-11-04.
