How to Revoke Token Approvals: Ethereum, BSC, Polygon, Arbitrum, and More
Learn how to revoke token approvals, check spender permissions, reduce unlimited allowances, and review DeFi wallet risk before signing safely.
Author: Damon Salvatore · Senior Content Marketer Revoking token approvals means removing or reducing a spender's permission to move tokens from your wallet. It is one of the most practical maintenance tasks for DeFi users, especially after swaps, vault deposits, bridges, NFT marketplace activity, or interactions with unfamiliar dApps.
Approvals are easy to forget because they do not always move funds immediately. A token approval can remain after the transaction you wanted is finished. If the spender contract is later abused, upgraded, compromised, or simply no longer needed, an old allowance can become unnecessary risk.
This guide explains how to revoke token approvals, what to check before revoking, how approval checkers work across Ethereum, BSC, Polygon, Arbitrum, and similar EVM networks, and how hardware wallet users should review revoke transactions safely.
Quick Answer: How Do You Revoke Token Approvals?
To revoke a token approval, use a trusted approval checker for the correct network, connect the wallet, review token, spender, and allowance details, then submit a revoke or set-allowance-to-zero transaction. The revoke itself is an on-chain transaction, so it usually requires gas and must be signed by the wallet owner.
The safest flow is to start from an official block explorer or a well-known approval management tool, verify the domain, choose the correct chain, and review each allowance before changing it. Do not connect a wallet to a random site that claims to "clean" approvals.
Revoking does not recover funds that have already moved. It reduces future permission risk.
Key Takeaways
Token revoking is wallet hygiene. It removes permissions that are no longer needed, but it should be done through trusted tools and careful signing. Revoking the wrong approval may break a dApp flow, while ignoring stale unlimited approvals can leave avoidable exposure.
- ERC-20 approvals allow spender addresses to move tokens within an allowance.
- A revoke usually sets the allowance to zero.
- Revoking requires an on-chain transaction and network gas.
- Use the correct chain, such as Ethereum, BSC, Polygon, Arbitrum, Optimism, or Base.
- Check token, spender, amount, and protocol name before signing.
- Unlimited approvals deserve special attention.
- Permit and Permit2 permissions may need different review habits.
- Revoking an approval stops future access, but it cannot reverse transfers that have already happened or recover funds that were already drained.
- A hardware wallet helps protect the signing key, but users still need to approve the correct transaction.
What is a token approval?
A token approval is permission for a spender address to move a token from your wallet up to a set allowance. In ERC-20 token flows, the ERC-20 approve function lets the token owner approve a spender, and the spender can later use transferFrom within that allowance.
This design is common in DeFi. A swap router, lending market, vault, bridge, staking contract, or NFT marketplace may need permission to move tokens during the action the user requests.
The approval itself is not the same as a transfer. It creates or updates permission. That permission may remain after the user closes the site or finishes the original DeFi action.
Why revoke token approvals?
Revoking token approvals reduces stale permission risk. If a spender no longer needs access to a token, removing the allowance limits what that spender can do later.
This matters most for unlimited approvals. Many dApps request very large allowances so users do not need to approve every transaction. That convenience can leave a long-lived permission behind. If the approved spender is unsafe later, the wallet may still have exposure.
Revoking can also help after phishing scares, website impersonation, suspicious signatures, old DeFi experiments, abandoned protocols, and wallets that have interacted with many contracts over time.
What revoking can and cannot do
Revoking can reduce future token movement by a spender. It can remove an allowance, lower an allowance, or force a user to approve again next time.
Revoking cannot undo a completed transfer. If tokens were already moved, setting an allowance to zero does not bring them back. It also cannot protect assets on chains where no approval exists or assets controlled by a separate private key.
Revoking is not a substitute for moving assets if the seed phrase or private key is exposed. If the wallet's recovery secret may be compromised, create a new wallet and move assets after careful verification.
How to check token approvals
Start by choosing the correct network. Approvals are chain-specific. An Ethereum approval checker will not show every BSC, Polygon, Arbitrum, Optimism, Base, or Avalanche approval unless the tool supports those chains and the user switches networks.
Then review each approval:
| Field | What to check |
|---|---|
| Token | Which asset can be moved |
| Spender | Which contract or address has permission |
| Allowance | Exact amount, high amount, or unlimited amount |
| Chain | Ethereum, BSC, Polygon, Arbitrum, Base, or another network |
| Last use | Whether the approval belongs to a dApp you still use |
| Risk signal | Unknown spender, old protocol, unlimited approval, or suspicious site |
Do not rely only on the protocol name shown by a tool. Names can be missing, vague, or misleading. When in doubt, compare the spender address with official protocol documentation or a block explorer.
For Ethereum, start with Etherscan's Token Approval Checker or a well-known multi-chain tool such as Revoke.cash. For other EVM networks, use the matching explorer, such as BscScan, PolygonScan, or Arbiscan, and always confirm that the domain and network are correct before connecting a wallet.
A practical approval check should record the token, spender address, allowance size, chain, and whether the dApp is still in use. Old unlimited approvals are the first items to review because they can stay active until the wallet owner sends a revoke or allowance-reduction transaction.
How to revoke approvals on Ethereum and EVM networks
The steps are similar across Ethereum, BSC, Polygon, Arbitrum, Optimism, Base, and other EVM networks.
- Open a trusted approval checker or the token approval page of the relevant block explorer.
- Select the correct network.
- Connect the wallet you want to review.
- Review token, spender, and allowance.
- Choose revoke or edit allowance.
- Sign the on-chain transaction.
- Wait for confirmation.
- Refresh the checker and confirm the allowance changed.
The revoke transaction usually sets the allowance to zero. Some tools let users reduce the allowance instead of fully revoking it. That may be useful for a dApp you still use, but exact allowances are safer than broad allowances when practical.
Gas cost depends on network congestion and the chain being used, not on whether the old allowance was small or unlimited. After the transaction confirms, refresh the same approval checker and verify that the allowance is 0 or reduced to the exact limit you intended. This final check is the simplest way to confirm the revoke actually took effect.
How to prioritize what to revoke
Most users do not need to revoke every approval every day. Prioritize the highest-risk approvals first.
Start with unlimited approvals to unknown or rarely used spenders. Then check approvals for assets with meaningful value. Next, review old approvals from bridges, NFT marketplaces, yield vaults, and apps you no longer use.
Keep approvals that you understand and still need, but be honest. If you cannot identify the spender, do not remember the dApp, or no longer use the protocol, the approval deserves review.
Permit and Permit2 approvals
Not every permission appears as a traditional ERC-20 approval. Permit-style signatures and Permit2 flows can change how users authorize spending.
Traditional ERC-20 approvals are on-chain allowance transactions. the EIP-2612 permit standard describes how signatures can authorize allowance changes without a separate approve transaction. Uniswap's Permit2 adds a shared approval and signature framework that can handle one-time transfers or allowance-based permissions with spender, amount, and duration details.
The user habit is the same: read the details. Check token, spender, amount, deadline, and the site requesting the signature. A signature can be safer when it is limited and clear, but it can still authorize token movement if the user signs the wrong message.
Hardware wallet users: what to check before signing a revoke
A hardware wallet can help keep the signing key away from the browser device. It does not decide whether the revoke transaction is correct. The user still needs to verify the action.
Before signing a revoke, check:
- The wallet address is the one you intended to review.
- The network is correct.
- The token approval shown in the tool matches the transaction you are signing.
- The transaction is reducing or removing an allowance, not creating a new one.
- The spender address is the one you meant to change.
- The site domain is correct.
If the device shows unclear data, slow down. A revoke should not require entering a seed phrase. A site that asks for a seed phrase to revoke approvals is unsafe.
When using UKey Core 26, treat the device screen as the final review point before confirming a revoke. Check the spender contract, token, network, and whether the allowance is being reduced to zero rather than increased. Browser malware can change what appears on a computer screen, so the safest habit is to compare the approval checker with the on-device details and reject the transaction if they do not match.
How often should you review approvals?
As a practical rule, review your approvals every 1-3 months, and always immediately after you interact with a new or unaudited dApp. Wallets used heavily in DeFi should be checked on the shorter end of that range.
Review approvals immediately after:
- Connecting to an unfamiliar dApp.
- Signing an unlimited approval.
- Using a bridge or new vault.
- Seeing a suspicious token approval prompt.
- Hearing that a protocol or front end was compromised.
- Moving assets from a testing wallet to a storage wallet.
Approval review is easier when wallets are separated by purpose. A small testing wallet can carry more experimental risk. A long-term hardware wallet should have fewer approvals and fewer dApp connections.
What to do if you find a suspicious approval
If you find a suspicious approval, do not panic-click through random tools. Use a trusted approval checker, verify the chain, and revoke the allowance if the wallet still controls the assets. Then check whether any unexpected transfers already happened. You can also compare the spender against known malicious-contract lists, but do not rely on any single list as complete.
If no funds moved, the revoke may be enough to reduce future risk. If funds moved, revoking can still prevent further movement by that spender, but it will not recover assets already transferred.
If the wallet signed multiple suspicious transactions or the recovery phrase may have been exposed, create a new wallet with a new seed phrase. Move remaining assets only after verifying the receiving address on a trusted setup.
Where UKey fits in approval safety
UKey Core 26 fits the signing layer. It can help users keep signing inside dedicated hardware and review prompts on a separate device. That is useful when dealing with approvals, revokes, and DeFi transactions.
UKey Wallet fits the software client layer. It helps users prepare wallet actions and coordinate with UKey hardware. UKey seed backup products fit the recovery layer if a device is lost or damaged.
Approval safety still depends on user review. A hardware wallet can protect the key, but the user must protect the decision.
Related Resources
Continue with these UKey guides to connect token approval hygiene with a broader signing workflow.
- DeFi Token Approval Safety
- Hardware Wallet vs MetaMask
- Why a Hardware Wallet Needs a Screen
- How to Secure Your Crypto Assets
- How UKey Protects Private Keys
- What Is a Cold Wallet?
- Approval Phishing
- Crypto Wallet Drainers
This article is for educational purposes only. It is not financial, legal, tax, or investment advice. Users should verify official domains, chain selection, transaction details, and wallet prompts before signing any approval or revoke transaction.
