WORLD CRYPTOCURRENCY GUIDE
Practical analysis

Token approvals: review and revoke spending permissions

Connecting a wallet to a site differs from granting token spending rights. An approval can remain active after disconnecting.

Spending permission closed after a wallet review
Educational illustration: Spending permission closed after a wallet review
Short answer

On each network, inspect approved spenders, token and limit. Revoke permissions you no longer need with a trusted tool, then verify the confirmed transaction. If a recovery phrase is exposed, revocation alone is insufficient.

Identify the approval

Token, spender and limit

Separate workstations in a shared space — AI-generated photograph
Separate the actions

Disconnect versus revoke

Review access

Use a trusted source

01

Identify the approval

An ERC-20 approval lets an address or contract spend a token up to a set limit. Check the network, token contract, spender and allowance; an unlimited amount increases exposure.

02

Separate the actions

Disconnecting a site ends an interface session but generally does not remove an on-chain approval. A message signature or off-chain permission may follow different rules: read every request before signing.

03

Review access

Open the wallet’s own tool or a known block explorer yourself, select the correct network and compare addresses with actual activity. Avoid messages claiming you must urgently follow a revocation link.

04

Revoke carefully

Reduce or cancel an approval you no longer need. Revocation is normally an on-chain transaction and may require the network’s native asset for fees. Read the wallet prompt before signing and wait for confirmation.

05

Verify afterwards

Refresh the approval list after confirmation. Revocation cannot recover assets already moved and cannot secure a compromised key or recovery phrase; that calls for a migration plan from a clean device.

06

Verify a revocation result

Closing a wallet session does not cancel onchain allowances. Revocation is a transaction on the right network, requires fees and must be confirmed before it is effective.

  • Check contract, spender and limit in an explorer.
  • An exposed phrase requires a new key; revocation cannot repair that secret.
07

Practical case: decision and limits

Revoking a spender may leave an earlier offchain signature relevant, depending on type, nonce and expiry. Distinguish recorded allowance, signed permit and NFT operator approval; one list may not cover every mechanism. Confirm revocation on the correct chain and contract. If keys are compromised, reducing allowance does not prevent fresh thief-signed operations.

08

A concrete verification

Read spender and allowance after confirmation: disconnecting a site does not erase on-chain permission.

09

Hypothetical case: revocation checked on the wrong network

A user grants an allowance on network A, then uses network B’s explorer to check revocation. The address may look identical while contract states remain separate. Record network, token contract, owner and spender to locate the relevant permission. Pending revocation is not confirmed revocation; disconnecting the wallet interface from a site does not establish that the allowance disappeared.

  • Check allowance on the correct contract and network after execution.
  • Keep the revocation hash and status; check required fees and native balance.
  • A still-valid off-chain signature may create a later allowance under the contract’s rules; inspect signed requests too.
10

Read an allowance cap in the correct unit

The value returned by allowance uses the token’s integer units. Hypothetical example: a cap of 1000000 with 6 decimals represents 1 token, not a million tokens. A very large integer may correspond to permission displayed as unlimited. Conversion helps read the cap but does not reduce existing permissions.

  • Compare owner, spender, token contract and network before the amount.
  • Use a verified interface to change permission; the converter signs and revokes nothing.
11

Identify both layers of Permit2 authorization

The holder first gives Permit2 an allowance in the ERC-20 token contract. Permit2 can then store a time-limited allowance for an app or use a signature for a single transfer. To check a revocation, record the network, token contract, Permit2 address and final spender. Inspect the ERC-20 allowance to Permit2 and any separate allowance stored by Permit2.

Convert token units without rounding →

Compare

Checks to make

Checks to make
TopicCheck
Identify the approvalToken, spender and limit
Separate the actionsDisconnect versus revoke
Review accessUse a trusted source
Revoke carefullyConfirm the transaction
Verify afterwardsAssess remaining risk

Disconnect, revoke or sign: what changes?

A website connection, a spending permission and a signature are different mechanisms. These examples concern a conventional ERC-20 token; some contracts use different rules.

Diagram: the owner authorizes a spender in the token contract; that contract stores the spending cap and checks transferFrom.
Spending cap ≠ available balance

The owner sets a cap with approve. The spender requests a transfer using transferFrom; the token contract checks its rules and the permission. allowance lets you read the current cap.

Before making a change

  1. Identify the network, token contract, owner and spender. A token symbol is not enough.
  2. Read allowance(owner, spender) on the correct contract. It is a spending cap, not the wallet balance.
  3. After revoking, wait for confirmation and read allowance again. A compromised private key needs a separate response.
ActionActual effectUseful check
Disconnect the websiteEnds the interface connection; a permission already recorded on-chain may remain active.Check the token permissions separately.
Confirm approve(spender, 0)Sets this allowance to zero on the relevant ERC-20 contract, if the transaction succeeds.Check the network, token, spender and new state after confirmation.
Sign an ERC-2612 permitCreates signed permission that another party can submit. The signature alone does not yet change allowance.Inspect spender, value, nonce, deadline and the signing domain.
Wait for the permit deadlinePrevents submission of that permit after its deadline; does not remove an allowance already created.Read allowance again: an expired signature display does not determine its state.
Hide the token in the walletChanges the displayed token list; changes neither the on-chain balance nor permissions.Inspect the contract with an explorer for that network.
Change the wallet passwordProtects local access depending on the software; does not replace the private key or revoke permissions.Distinguish device security, key compromise and contract permissions.

Revoking with approve(spender, 0) does not consume the nonce of an unused ERC-2612 permit. If that signature remains valid, submitting it can restore an allowance. Check previously granted signatures and token-specific invalidation mechanisms; disconnecting does not cancel them.

ERC-20 · ERC-2612 · EIP-712

FAQ

Frequently asked questions

Is disconnecting my wallet enough?

No. An on-chain token approval can remain active after a site is disconnected.

Does revoking close a DeFi position?

Generally the spending permission changes, while an existing position is separate. Check the specific protocol.

Why does revocation cost a fee?

Changing the approval is an on-chain transaction and normally needs the network’s native asset for fees.

Does ERC-20 allowance permit spending native ETH?

It covers the token managed by that contract, not native ETH automatically. Transactions, account delegation or other permissions can have broader effects. Identify the exact request; an allowance list does not summarize every granted power.

Verifiable sources

Independent educational content reviewed against primary documentation. No personalized recommendation or promise of returns. Updated November 15, 2026

Related terms

Approval revocation
On-chain transaction that reduces or cancels a contract’s previously granted right to spend a token.
ERC-20 allowance
A cap stored by a token contract allowing a spender to use tokens for an owner. It is distinct from the balance and specific to the contract and network.
Permit2
Uniswap contract for spending allowances or signed transfers. Check the token allowance to the Permit2 contract and the permission granted to an application separately.
Spender
Address permitted to spend an owner’s tokens under a contract’s rules; check it alongside the relevant network and token.

Prepare and continue reading

Useful background

  • How to choose a crypto wallet

    A crypto wallet manages the keys that authorize operations; it does not physically hold the assets. The right choice depends on use, value at risk and your ability to protect a recovery phrase without sharing it.

  • Message signatures: login, permits and permissions

    No immediate paid transaction does not mean no risk. Inspect request type, domain, network, contract, spender, value and expiry. Reject requests whose scope your wallet cannot explain.

Continue to the next step

  • Recognize and avoid crypto scams

    Crypto scams often combine urgency, impersonation and irreversible payment. Stop the conversation, find the service through an independent official channel, never share a recovery phrase and reject guaranteed-return claims.

  • What to do after a crypto security incident

    Stop signing. Use a trusted device and a new recovery phrase if exposed. A sweeper bot can steal gas top-ups: consult official wallet support before attempting transfers.