Should I Revoke Approvals for Tokens I No Longer Hold? The Decision Depends on Reuse
Should you revoke approvals for tokens you no longer hold? Usually yes if you have no planned reuse; weigh spender trust, future access and gas first.
The Tareom Editors5 min read

Usually, you should revoke token approvals you no longer need. An ERC-20 token’s balance and its allowance are separate values, so selling or transferring your tokens leaves the spender’s permission in place. An allowance is the amount a smart contract is authorized to spend from your wallet; it can matter again if tokens later reach that wallet.
The choice is about each unused allowance, not just whether you still own the token. Revoke it to remove future spending access, or retain it if you trust the spender and expect to use it again. If there is no concrete reuse planned, choose revoke.
How to decide whether to revoke an unused allowance
Trust: how comfortable are you with the spender?
Revoking an abandoned permission reduces the access a spender has to your future balance. Retaining it leaves that permission available. Consider who controls the contract and whether you still trust it; an approval can outlast the transaction or service for which you first granted it.
Say you sold the last of a token after using a trading contract. Your current balance may be zero, but the allowance can remain. If that contract later receives permission to spend the token again through the existing allowance, the empty balance today has not removed that access. Revoking clears the allowance; it does not reverse a past transfer or recover tokens already spent.
Reuse: do you have a concrete reason to keep it?
Retaining an allowance can save you from approving the spender again when you return to a service. That convenience is useful when you know you will use the same trusted spender with the same token. Without a real plan to reuse it, the saved step has little value and the permission remains available against future balances.
When reviewing approvals with revokecash, look at the network, spender and remaining allowance, including entries for tokens whose wallet balance is zero. The tool’s allowance review makes it a concrete example of checking what permission is still recorded before deciding whether to clear it. A zero balance and a zero allowance are different states: ERC-20’s balanceOf and allowance functions track them separately.
Imagine your wallet holds none of a token, but the allowance for an old deposit contract is still nonzero. The review shows that the spender and permission remain, even though there is nothing to spend in the wallet right now. If you have no planned deposit, revoking removes the unused permission. If you expect to deposit again and trust the contract, retaining it avoids a future approval step.
Gas: is the saved approval worth the cost?
Revoking requires an onchain transaction, which may involve a network fee. Retaining the allowance avoids paying to clear it now, but you may later pay for a new approval if you return to the service and had revoked the old one. The relevant tradeoff is the cost of clearing today against the value of keeping permission ready and the exposure that comes with it. Fees vary by network and conditions, so consider the cost shown for the transaction you are about to make.
For a standard ERC-20 token, setting approve(spender, 0) clears that spender’s allowance. That action changes the permission. It does not move your tokens or perform another action with the contract. The [revokecash FAQ](https://revoke.cash/learn/faq) covers the practical tradeoffs around approvals and deposited assets.
Who should revoke, and who might retain?
Revoke if you no longer use the spender, cannot identify a concrete reason to keep access, or prefer to remove the permission despite a transaction fee. Retain if the spender is trusted, you expect to use that same token and service again, and avoiding another approval is worth leaving the allowance active.
Use the allowance entry itself to make the decision. Confirm the wallet and network, identify the spender, and check how much permission remains. An old approval for a zero-balance token can still be relevant if that token returns to the wallet; a zero allowance means that spender has no remaining amount under that standard ERC-20 approval.
Related questions
Does revoking approvals unstake tokens?
No. Existing stakes remain deposited because revoking an allowance and unstaking are separate actions. Revocation removes the spender’s permission for future token transfers under that allowance; it does not withdraw assets already deposited. If you later make another deposit, the staking contract may need a new approval to receive the tokens. Check your stake position separately if your goal is to withdraw.
Does disconnecting a wallet remove approvals?
No. Disconnecting a wallet from a site changes the connection, while an ERC-20 allowance remains recorded onchain. A disconnected site or wallet session does not clear the spender’s permission. Review and revoke the allowance separately if you no longer want it active.
For each unused allowance, let trust and concrete reuse justify keeping it; otherwise, revoke it. Selling the token did not clear its allowance, so removing an unneeded permission is the way to end that future access.