What does a token approval allow?
Many applications need two steps. First, your address calls approve(spender, amount) on the token contract. Later, the approved spender can call transferFrom within that allowance.
The spender is an address—often a smart contract—not the friendly name displayed by a website. An approval can remain after you close the page. This is why disconnecting a wallet from an interface does not necessarily revoke token allowances.
A door-pass example
Imagine a pass that opens one storeroom door and allows up to 100 boxes to leave. Signing the pass does not move a box. It authorizes a named holder to move boxes later, within the limit. An unlimited approval is closer to a pass with no useful box limit.
The analogy has a limit: token contracts and application contracts can contain bugs or upgrade controls, and the “door” may be operated by more than one system component.
A safer review routine
- Open the application from a bookmark or independently verified address, not an unexpected message.
- Confirm the network and token contract before reading the friendly token symbol.
- Inspect the spender address, not only the site name, and check that it belongs to the action you intended.
- Compare the requested amount with the amount you actually plan to use. Prefer a bounded allowance when the interface supports it and the extra transaction cost is acceptable.
- Read the wallet’s final confirmation again before signing; reject it if the network, asset, spender, or amount changed.
- After the action, verify the allowance on a trusted block explorer or wallet tool and revoke permissions you no longer need. Revocation is itself an onchain transaction and costs a fee.
Approval safety also depends on signatures. For example, ERC-2612 permits use signed messages to set allowances when submitted onchain. “I see no approvals” is not proof that every permission path is closed. Revocation does not undo a completed transfer or repair an exposed private key.
The distinction between disconnecting an app and revoking an allowance matters: the first changes a connection; the second changes a particular permission. Inspect the resulting onchain state, not just a closed browser tab.
Verify the exact allowance after revocation
The tab is gone. The allowance may not be. Check the token-contract record, not the browser. In the conventional ERC-20 interface, allowance(owner, spender) reports the remaining allowance for that pair on that token contract.
Use a read-only contract view or a documented wallet allowance tool reached through an independently checked route. If an explorer exposes a contract-reading view, check its documentation and the actual contract rather than guessing which buttons are read-only. Ethereum's JSON-RPC documentation distinguishes eth_call from submitting a transaction: the call can read a contract function without creating an onchain transaction. No recovery words or signature are needed for that public lookup.
- Record the network, exact token contract, full owner address and full spender address. A matching symbol or website name is not a matching permission.
- If you already submitted a revocation, inspect that transaction's outcome first. Read its hash and result; a submitted or pending transaction is not proof that state changed.
- Read the token's
allowance(owner, spender)for those exact addresses. Use a block/state observation after the included revocation, not an older cached record. Record the block or observation time where the tool provides it. - Read the result as a permission amount, not your balance. If the call fails, the response is undecodable, or the tool cannot establish the network and contract, the result is unknown, not zero. Do not sign another request to make a read-only result appear.
| Read result | What it tells you | What it does not prove |
|---|---|---|
| Decoded zero | No conventional allowance for that exact pair at the queried state | Every account permission is gone |
| Decoded positive amount | An allowance remains for that pair at the queried state | That it will be used or that the spender is trustworthy |
| Error or unclear result | This check did not establish the allowance | That the allowance is zero |
The ERC-20 interface guide lists allowance and balance as separate methods. Nonzero raw values need the token's unit handling; do not assume every token uses the same decimal count. An old Approval event is a historical record, not a substitute for a current state read.
Zero answers one specific permission question. An unsubmitted permit may be a different future authorization path, and account/session permissions need their own checks. Use the wallet-permission comparison for those scopes. This guide does not test a real wallet, guarantee a revocation tool or ask you to connect an account.
Why can a token approval stay visible after a Permit2 allowance expires?
A token can still report an approval to Permit2 after an app’s own permission inside Permit2 has expired. The token contract stores the first record. Permit2’s AllowanceTransfer module stores the second record for a specific owner, token and spender.
Take one fictional block on a single Ethereum network, timestamped 15 November 2026, 13:00 UTC (1794747600 Unix seconds). Mira is the owner. The demo token contract, the Permit2 contract and the Demo Swap spender contract are three distinct addresses. OWNER, TOKEN, PERMIT2 and APP_SPENDER are placeholders for those four addresses. Both reads use state at the same block. The amounts below are shown in demo tokens after accounting for the token’s decimals.
| Contract read at that block | Value returned | Meaning at 13:00 UTC |
|---|---|---|
On TOKEN: allowance(OWNER, PERMIT2) | 100 demo tokens | The token contract still reports a positive ERC-20 allowance from Mira to the Permit2 contract. |
On PERMIT2: allowance(OWNER, TOKEN, APP_SPENDER) | 40 demo tokens stored. Expiration: 12:00 UTC (1794744000). Nonce: 3. | The Demo Swap spender’s stored amount is still visible. Its allowance expired one hour before this block. |
The ERC-20 specification defines the two-address read. The Permit2 interface returns amount, expiration and nonce for the three-address read. The AllowanceTransfer implementation checks whether the block timestamp is greater than the stored expiration before checking the amount. In this snapshot, the expired record would fail that check even though both stored amounts are positive. The nonce is a separate field.
This pair of reads establishes the state of two records at that block. It leaves other spenders and one-time signature transfers outside the result. For the difference between the stored expiry and a signature deadline, see the wallet permissions guide’s Permit2 comparison.
Update note
11 October 2026: added an exact-pair, read-only allowance verification procedure and zero/positive/unknown interpretation. The original publication date, author and illustration are unchanged.
15 November 2026: added a same-block comparison of an ERC-20 approval to Permit2 and an expired AllowanceTransfer permission for one app.
Sources
- EIP-20: Token Standard — normative interface, accessed 11 October 2026.
- Ethereum.org: ERC-20 token standard — accessed 11 October 2026.
- ERC-2612: Permit Extension — signed-approval mechanism, checked 11 October 2026.
- MetaMask: Revoking token allowances — disconnect/revoke distinction, checked 11 October 2026.
- Ethereum.org: JSON-RPC API — read-only eth_call and queried block/state, checked 11 October 2026.
- Uniswap Developers: Allowance Transfer — checked 15 November 2026.
- Uniswap Permit2: AllowanceTransfer read interface — checked 15 November 2026.
- Uniswap Permit2: transfer-time expiration check — checked 15 November 2026.
See something wrong? Brokzi logs material changes. Prepare a correction note.



