How to Revoke Token Approvals

Scope: The Cleanup Step, Not the Full Approvals Picture

Swoopr's Token Approvals & Blind Signing hub covers what an approval is, why granting one is unavoidable in DeFi and NFT trading, and how attackers exploit them through phishing and malicious contracts. This page is narrower and entirely practical: it's about the maintenance step most people skip, going back through the approvals you've already granted and turning off the ones you no longer need. If you're still figuring out what an approval actually is or want the unlimited-versus-limited tradeoff explained first, start with the hub and its companion pages, Unlimited vs. Limited Approvals and Token Allowance Checker Tools. This page assumes you already understand the concept and want the process for cleaning up what's already out there.

Key Takeaways

Direct answer: Revoking a token approval means submitting a new on-chain approve transaction that resets the allowance for a specific token-and-spender pair to zero. It costs gas because it's a real transaction, which is why unused approvals pile up for years. The fix is a recurring habit: connect a wallet read-only to an approval-checking tool, review every approval you've ever granted, and revoke the ones tied to protocols you no longer use, don't recognize, or no longer trust, on a cadence of roughly every two to three months rather than as a single one-time cleanup.

• Revoking sets an existing allowance back to zero; it doesn't erase the original approval transaction from the blockchain's history.
• Because revoking is itself an on-chain transaction, it costs gas, which is the practical reason so many approvals never get cleaned up.
• An approval is a standing liability for as long as it exists, regardless of how safely or how long ago you used the protocol it's granted to.
• A protocol exploited years after your last interaction can still drain your wallet through an approval you forgot you left active.
• Batch-revoking tools that support multicall transactions can meaningfully cut the total gas cost of a large cleanup.
• A hardware wallet protects your private key; it does nothing to undo an approval you already signed, deliberately or by mistake.

What "Revoking" Actually Means On-Chain

An approval is a value stored inside a token's smart contract, mapping a token owner's address, a spender's address, and an allowance amount together. When you approve a decentralized exchange, a staking contract, or an NFT marketplace to spend a token on your behalf, you're calling that token contract's approve function and setting a number for exactly that owner-spender pair. The contract remembers this number indefinitely; there's no expiration, no automatic timeout, and no built-in cleanup. It stays exactly as you set it until you call approve again for that same pair with a different number.

Revoking is not a special, separate blockchain operation. It's the same approve function, called again, with the allowance argument set to zero. Once that transaction confirms, the spender contract's stored allowance for your address drops to zero, and any future attempt by that contract to move your tokens using the approval mechanism fails, because there's no longer any allowance left to spend against. Nothing about the original approval transaction is deleted or hidden; it remains permanently visible in the blockchain's transaction history, exactly like every other transaction you've ever sent. What changes is the current state the contract checks before allowing a transfer, not the historical record of what happened.

This distinction matters because it explains the cost. Reading the blockchain's current state, checking what approvals exist and what their values are, is free; it's just a query against public data that any wallet, block explorer, or approval-checking tool can run at no cost to you. Changing that state, which is what revoking does, requires the network to process a new transaction and update the contract's stored data, and that work is exactly what gas fees pay for. There's no way to revoke an approval without paying whatever the network's current gas price is, which on congested networks can run from a couple of dollars to considerably more. This is the unglamorous reason unused approvals accumulate: checking your list costs nothing, but doing anything about what you find costs real money, and that asymmetry is exactly why so few people ever get around to it.

The General Process

Specific approval-checking tools change their interfaces, add features, and occasionally shut down or rebrand, so this walkthrough describes the process at the level that stays true across all of them rather than pointing at one specific product's buttons.

Step one: connect read-only

Reputable approval-checking services let you view your wallet's approval list by entering or connecting your public wallet address, which is read-only and requires no signature, transaction, or permission grant of any kind. You're only looking at public blockchain data; nothing at this stage can move funds or grant a new approval. If a tool asks you to sign anything just to view your list, that's a red flag, and it's worth using a different tool instead.

Step two: review every approval across every token and network

A good checker lists every approval currently associated with your address: spender contract, token, and current allowance amount, often shown as either a specific number or "unlimited." Because approvals are per-network, a wallet active on Ethereum mainnet, a layer 2, and a separate chain like Solana will have entirely separate lists to review; there's no single global view spanning every chain with most tools. Take the time to look at the full list rather than skimming, since the point of this review is catching what's easy to forget.

Step three: identify which approvals to remove

For each entry, ask three questions: do I still actively use this protocol, do I recognize this spender contract at all, and if I do, do I still trust its current security track record. An approval tied to a protocol you use weekly and still trust can reasonably stay. An approval to a spender address you don't recognize, a protocol you tried once years ago and never returned to, or a protocol whose contracts have since had a publicized exploit or been abandoned by its team, is a strong candidate for revocation. When in doubt, most checking tools link out to a block explorer or the protocol's own documentation so you can confirm what the contract actually is before deciding.

Step four: submit the revoke transaction for each one you're removing

Selecting an approval to revoke in most tools prepares a transaction that calls approve with a zero allowance for that specific token-and-spender pair, which you then sign and submit through your connected wallet like any other on-chain transaction. Review what the transaction actually does before signing, confirming it's setting an allowance to zero rather than requesting a new approval. Once it confirms on-chain, that approval is closed; repeat for each one you've decided to remove, using batching where the tool supports it, covered below.

Why This Matters Even for Legitimate Protocols You Trust

The most common reason people skip revoking is a reasonable-sounding one: "I used this protocol, it was fine, nothing bad happened, so there's no problem." That reasoning conflates two different questions. Whether a protocol treated you well in the past is a question about historical outcome. Whether an active approval to that protocol's contract is currently a risk is a question about the contract's ongoing existence, and those two questions have almost nothing to do with each other.

An approval doesn't care about your relationship with a protocol. It's a standing grant of spending rights, sitting in a smart contract's storage, that remains fully functional for as long as it exists, regardless of whether you've opened that protocol's app once since. If the contract holding that approval is ever exploited, through a bug in its code, a compromised admin key, or a malicious upgrade, every wallet with an active, sufficiently large allowance to that contract is exposed to whatever the exploit lets the attacker do, which in the worst documented cases has meant draining approved tokens directly from thousands of wallets with no other interaction with the exploit at all. This has happened to protocols that operated safely for years before the exploit occurred; a long clean track record reduces the odds of a future problem but does not reduce it to zero, and an approval left active has no expiration tied to how much time has passed since your last use.

This is the core argument for treating approval review as ongoing maintenance rather than a reaction to something going wrong. You're not trying to identify protocols that are currently unsafe, which is often impossible to know in advance; you're trying to minimize the number of standing liabilities attached to your wallet at any given time, so the blast radius stays small if any one of them turns out to be a problem. An approval you're not actively using provides zero ongoing benefit while it exists, and it does the same thing whether it's been active for three days or three years: nothing, until the one day it's exploited.

Recommended Cadence

Treating approval cleanup as a single one-time project misses the point, because every new protocol interaction adds another entry to the list the moment it happens. A more durable habit is two overlapping practices working together.

The first is a recurring full review, roughly every two to three months for an active DeFi or NFT user, less often for someone who interacts with new protocols rarely. This doesn't need to be exhaustive every time; the goal is catching approvals that have gone stale since the last pass. A recurring calendar reminder works well here precisely because approval cleanup has no natural trigger of its own; nothing about your wallet visibly changes when an old approval sits there unused, so it's easy to forget without a scheduled prompt.

The second is a spot review immediately after using any new or unfamiliar protocol for the first time, especially one you tried once to claim a single airdrop or mint and don't expect to return to. Rather than letting that one-off approval sit indefinitely, revoking it right after the interaction that needed it closes the window while it's still fresh in mind. It's also the cheapest time to revoke it: you're already paying attention to that protocol, rather than trying to reconstruct months later why an unfamiliar spender address is in your approval list at all.

Worked Example: The Forgotten Unlimited Approval

Illustrative walkthrough — for education only.

To make the decision process concrete, here's how a realistic approval review typically plays out.

The setup. Two years ago, a trader connected their wallet to a mid-sized yield farming protocol to try a single liquidity pool during a promotional rewards period. Depositing required an approval, and the wallet's default transaction, unmodified before signing, requested unlimited spending rights for the deposited token rather than a limited amount matching the deposit. The trader signed it without adjusting the amount, withdrew from the pool a few weeks later once the promotional rewards ended, and never used the protocol again. The approval itself, however, was never revoked; withdrawing funds from a pool doesn't automatically clear the approval that let you deposit into it in the first place.

The discovery. During a scheduled quarterly review, the trader connects their wallet read-only to an approval checker and finds the entry: an unlimited allowance, granted two years earlier, to a spender contract they don't immediately recognize by address alone. Clicking through to the linked block explorer confirms it's the yield farming protocol's deposit contract, and a quick search shows the protocol is still operating, hasn't had a publicized exploit, but also hasn't seen a security audit update or meaningful development activity in over a year.

The decision process. The trader isn't actively using this protocol and has no plan to return to it. The approval is unlimited, meaning if this specific contract were ever compromised, whatever balance of that token the wallet holds on the day of any future exploit would be exposed, not just a small deposit-sized amount. Weighed against this is a one-time gas cost, in this case a few dollars on the network the protocol runs on, to submit a revoke transaction. The math is straightforward once framed this way: a few dollars paid once, against an unlimited, indefinite exposure to a contract with no ongoing benefit to the trader whatsoever. There's no scenario where leaving the approval active serves any purpose for someone who isn't using the protocol.

The action. The trader selects the entry in the approval checker, confirms the prepared transaction is setting the allowance to zero for that specific token and spender, and signs it. The gas cost is paid once; the exposure closes permanently, unless the trader chooses to approve that same contract again in the future. This is precisely the scenario the recommended cadence exists to catch, an approval that outlived its purpose by roughly two years before anyone looked at it, not because the trader was careless, but because nothing about the wallet's normal use ever surfaced it.

Practical Considerations

Batch revoking

Reviewing and revoking approvals one at a time means paying a full transaction's gas cost for every single revocation, which adds up quickly for a wallet with a dozen or more stale approvals. Several approval-management tools support batching multiple revocations into a single multicall transaction, bundling several approve-to-zero calls into one that pays only one base transaction cost instead of many. Where a tool offers this, selecting several approvals for removal at once and submitting them together is meaningfully cheaper in total gas than repeating the single-revoke process individually. This isn't universal, not every tool or network handles large batched calls the same way, and an extremely large batch can in rare cases approach a block's gas limit, but for a typical cleanup of five to fifteen approvals it's worth checking for a batch option before revoking one by one.

Weighing gas cost against ongoing risk

Every revocation decision is, at bottom, a comparison between a one-time, known cost and an ongoing, unknown risk. The gas cost is concrete: you can see exactly what it will cost before signing. The risk from leaving an approval active is diffuse and impossible to price precisely, since it depends on whether that specific contract is ever exploited, which nobody can predict with certainty. This asymmetry, a certain small cost versus an uncertain but potentially total loss, is why the reasonable default leans toward revoking anything you're not actively using: the downside of revoking something you didn't need to is a few dollars in gas and the minor inconvenience of re-approving later, while the downside of leaving an unnecessary approval active is open-ended for as long as it exists.

Misconceptions Versus Reality

Common Mistakes

• Never checking your approval history at all. Most wallets provide no built-in prompt that approvals exist and accumulate; without deliberately visiting a checking tool, a wallet's full approval list can go unexamined for years, the single biggest reason old approvals are so common.
• Assuming an unused protocol's approval is "probably fine" without actually assessing it. Skipping the real question, whether the spender contract is still maintained, audited, and trusted, in favor of a vague sense that nothing bad has happened yet, treats the absence of a past problem as evidence of future safety, which it isn't.
• Relying only on a wallet's default transaction history. Approvals granted through third-party interfaces or older wallet versions don't always surface clearly there the way a dedicated approval checker's dashboard does; relying on memory misses entries a proper checker would catch.
• Treating a single cleanup as permanently sufficient. Every new protocol interaction adds a fresh entry to the list; a review done once and never repeated drifts back toward the accumulated-risk state that made the first cleanup necessary.
• Skipping the confirmation step before signing a revoke transaction. Briefly confirming the transaction is setting an allowance to zero, rather than requesting a new one, takes seconds and avoids signing something unintended.

Risks, Limitations, and Exceptions

• Gas costs vary significantly by network and congestion; a revocation that costs a few cents on a low-fee layer 2 can cost considerably more on a congested mainnet, which affects how aggressively it's worth cleaning up small approvals.
• Approval-checking tools only see what's visible on the network they're pointed at; a wallet active across several chains needs a separate review on each one.
• Third-party approval-checking and batch-revoke tools are themselves smart contracts or web applications; verify you're using a well-known, established one rather than a search-result link, the same scrutiny you'd apply to any site requesting a wallet connection.
• Revoking an approval you'll need again shortly, for a protocol you use regularly, simply means paying gas again to re-approve later; a minor inconvenience, not a security concern, but worth factoring into which approvals are worth touching during a routine review.
• Some tokens use approval mechanisms that behave slightly differently from the standard model described here; always confirm what a prepared transaction actually does before signing rather than assuming it matches this general description exactly.

Practical Implementation Checklist

1. Connect your wallet address read-only to a reputable approval-checking tool; never sign anything just to view your list.
2. Review the full approval list for each network your wallet is active on, not just the one you check most often.
3. For each approval, confirm whether you still actively use the protocol and whether you still recognize and trust the spender contract.
4. Flag approvals tied to protocols you no longer use, don't recognize, or have lost confidence in for revocation.
5. Use a batch-revoke option where the tool offers one, to reduce total gas cost across multiple revocations.
6. Confirm each prepared transaction is setting the allowance to zero before signing, not requesting a new approval.
7. Set a recurring reminder, roughly every two to three months, for a full review rather than treating this as a one-time task.
8. Do a spot review and revoke immediately after any one-off interaction with a new or unfamiliar protocol.

Sources

• MetaMask Support, "How to view and revoke token approvals," documentation on locating and revoking ERC-20 token spending approvals from a connected wallet. See support.metamask.io.
• Revoke.cash, an open-source token approval management tool for reviewing and revoking ERC-20 and NFT spending approvals across multiple networks. See revoke.cash.
• Ethereum Improvement Proposals, "EIP-20: Token Standard," the technical specification defining the approve and allowance functions that token approvals are built on. See eips.ethereum.org.

Frequently Asked Questions

Conclusion

Revoking a token approval is a straightforward transaction, an approve call with the allowance set to zero, but the gas cost attached to that transaction is exactly why so many wallets are carrying old, forgotten approvals that provide no benefit and no shortage of ongoing risk. The fix isn't a one-time cleanup; it's a recurring habit of connecting read-only to a checking tool, reviewing the full list across every network you use, and weighing a small, known gas cost against an open-ended, unknown risk for anything you're not actively using. Pair this with Unlimited vs. Limited Approvals to understand why the amount you approve in the first place matters just as much as whether you eventually revoke it, and the Approval Best Practices Checklist for the full set of habits beyond just cleanup.

Related Reading

• Token Approvals & Blind Signing — the parent hub covering what approvals are and how blind signing is exploited.
• Token Allowance Checker Tools — a closer look at the category of tool this page's process depends on.
• Unlimited vs. Limited Approvals — why the amount you approve up front changes how much a single exploit can take.
• Approval Best Practices Checklist — the broader set of habits for granting and managing approvals, beyond just revoking them.