# Token approval (ERC-20 approve)

> A transaction that lets another address, the spender, move up to a set amount of one token out of your account, until you change it.

- Request: `approve(spender, amount)`
- Standard: ERC-20
- 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/approve

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 token: each token contract keeps its own allowances.
- The spender: the address that receives the right to move your tokens. It is often a contract, not the app’s name.
- The amount: a number, or the maximum possible value, which wallets and apps often call unlimited.
- The network the request is on.

## What it lets the other party do

- The spender can call `transferFrom` to move your tokens of that token contract. ERC-20 describes `approve` as allowing the spender “to withdraw from your account multiple times, up to the `_value` amount.”
- A new `approve` for the same spender replaces the old amount. ERC-20: “If this function is called again it overwrites the current allowance with `_value`.”

## What it does not do

- It does not move tokens by itself. Moving them is a separate `transferFrom` call made by the spender.
- It does not cover other tokens.
- Disconnecting the app in your wallet does not remove it. ethereum.org: if you disconnect but have granted token allowance permissions, “they can still use those tokens.”

## How long it lasts

- ERC-20 defines no expiry. The allowance stays until it is used up or you replace it. ethereum.org: “There are no expiration dates on contract permissions.” (That sentence is about ERC-20 style approvals; Permit2 and some newer systems do have expirations.)

## How to undo it

- Send a new `approve` for the same spender with an amount of 0. That changes future spending only. It does not return tokens that already moved.
- To see the approvals your real account has, use an established external checker such as Revoke.cash or Etherscan’s token approval checker. This site never looks at your account.

## A pattern to recognise

- A button labelled “verify”, “claim” or “enable” whose wallet prompt is actually an approval for a spender you do not recognise, often for the maximum amount. Read the prompt, not the button.

## Practice question (fictional)

Fictional Lanternfly Swap asks for an approval before your first swap.

| Field | Value |
| --- | --- |
| Request type | Transaction: approve |
| Token | MOSS (fictional) |
| Spender | Lanternfly Router (fictional contract) |
| Amount | 100 MOSS |
| You then swap | 40 MOSS |

**Question:** After the 40-token swap, can the router still move more of your MOSS without a new approval?

**Answer:** Yes. An allowance is a ceiling for repeated `transferFrom` calls, not a single-use pass. If the swap used 40 of it, up to 60 MOSS stays available to the router until you set the allowance to 0.

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

- [ERC-20: Token Standard](https://ercs.ethereum.org/ERCS/erc-20). Ethereum ERCs. Final; created 2015-11-19. Checked 2026-11-04.
- [How to revoke smart contract access to your crypto funds](https://ethereum.org/guides/how-to-revoke-token-access). ethereum.org. Page as published on the check date. Checked 2026-11-04.
- [How to disconnect your wallet from a dapp](https://support.metamask.io/more-web3/dapps/disconnect-wallet-from-a-dapp/). MetaMask Support. Page as published on the check date. Checked 2026-11-04.
