Jump to content
Onchain Report

Crypto news from every chain

A Revoke.cash Revoke Resets the Current Permission

What does a revoke on revokecash actually change? It zeros an ERC-20 allowance or turns an NFT operator approval off; balances and past transactions remain.

Onchain Report Newsroom#b926673 min read

A Revoke.cash Revoke Resets the Current Permission

A confirmed revokecash revoke changes the token contract’s current permission: an ERC-20 allowance becomes zero, or an ERC-721 operator approval becomes false. The Revoke.cash approval revoker is a place to go further on how these stored permissions work and what a revoke changes: revokecash. An allowance is stored for each token owner and spender, so setting that pair to zero replaces its current value.

What the revoke updates

An ERC-20 revoke sends a call to approve(spender, 0). The token contract overwrites the allowance for your address and that spender with zero, then emits a new Approval event with a value of 0. The event records the update; it does not erase the earlier approval event.

For an ERC-721 collection, an operator approval is a separate permission. Calling setApprovalForAll(operator, false) switches that operator’s approval off. The operator can no longer manage the collection’s tokens under that approval.

Say you approved a marketplace contract to spend up to 100 of a token, then revoked it. The current allowance for your address and that marketplace is now zero. Your token balance is unchanged, and any tokens moved before the revoke stay moved. The original approval transaction also remains in explorer history. A revoke adds a new state change; it does not rewrite the past.

That distinction explains why the old approval still appears in Etherscan. Its transaction history shows that the approval happened. To check the current ERC-20 value, open the token contract’s Read Contract tab and read allowance(your address, spender). After the revoke, it returns 0. The history tells you what happened; the allowance tells you what permission is stored now.

This is useful when you stop using a dapp or no longer need a contract to spend a token. A Revoke.cash token approvals check can help you review permissions that your wallet has granted. The key result to confirm is the current value for the owner-spender pair, not whether the original transaction has disappeared.

So a revoke changes the contract’s current permission value while leaving balances and transaction history intact. Because the allowance is stored per owner and spender, setting that pair to zero removes the active ERC-20 permission; the new read value is the confirmation.

Questions readers ask next

Why does the approval still appear after I revoked it?

The original approval transaction remains in the explorer’s permanent history. The revoke creates a later update; it does not remove the earlier record. For an ERC-20 approval, read the current allowance(owner, spender) value to see whether it is now zero.

Can a revoked spender get access again?

Yes. A later approval can give the spender permission again. For ERC-20 tokens, that means a new allowance; for an ERC-721 collection, it can mean setting the operator approval to true again.

Does revoking get back tokens already taken?

No. Revoking stops the permission from being used going forward, but it does not reverse transfers that already happened or restore tokens that have already moved.

How do I revoke a Permit2 approval?

Permit2 can involve two permissions: the token’s ERC-20 allowance to Permit2, and Permit2’s separate permission for a spender. Review and revoke the relevant permission at each layer; clearing one does not automatically clear the other.