2026-11-17 11:49 UTC65390c
How do you use Revoke.cash to revoke on Base?
How to use revokecash on Base: match the token and spender, sign a revocation with the owning wallet, then confirm the permission is inactive on-chain.
Crypto Record Editorial3 min read

After spotting an unwanted Base permission, revokecash lets you select Base, identify the approval, and sign its revocation with the wallet that granted it; confirmation updates the permission stored on Base. For this task, use revokecash to inspect the wallet’s Base approvals and choose the permission you want to remove. You will need the owning wallet and ETH on Base to pay for the transaction.
Approval details identify the permission to remove
The Revoke.cash approval checker shows the token, spender and approved amount, which lets you match the entry to the permission you intend to change. The token identifies what was approved; the spender is the contract allowed to act on that token; the amount shows the ERC-20 allowance.
Open the official Revoke.cash site, enter the wallet address, and select Base. Match both the token contract and spender before proceeding. A familiar token name alone may not identify the exact approval: compare the contract and the spender with the permission you want removed.
ERC-20 allowances and ERC-721 operator approvals grant different permissions. An allowance sets how many fungible tokens a spender may move. An NFT operator approval lets an operator manage NFTs for the wallet. The approval entry tells you which kind you are reviewing, so select the specific permission you no longer want active.
Think of an approval as a standing key given to a contract. Revoking the selected permission changes that key’s authority on Base. It does not undo a transfer that already happened, and the transaction only addresses the permission you select; other approvals remain separate.
A confirmed Base transaction changes the selected permission
Once you have identified the approval, connect the account that granted it, choose Revoke for that entry, and review the Base transaction before signing. The address used to inspect the approval can be any address, but only the owning account can authorize a change to its permission.
Base uses ETH for gas. ETH held on Ethereum cannot pay for a revocation on Base, because the transaction is submitted on Base and its gas must be paid there. Before signing, make sure the owning account has ETH on Base; having ETH in the same wallet on another network does not cover this transaction.
After signing, wait for the transaction to confirm on Base, then refresh the approval view. Look again at the selected entry. For an ERC-20 approval, verify that its allowance is zero. For an ERC-721 approval, verify that the operator permission is disabled. Those are the results that show the selected permission is inactive.
If the entry still shows an active allowance or operator permission, the task is not complete. Confirm you refreshed the Base view and matched the same token and spender or operator. A confirmed revocation changes the permission stored on Base; the refreshed approval status is how you check that the intended change took effect.
- Inspect the approval on Base and match its token and spender.
- Connect the owning wallet and sign the revocation, with ETH on Base for gas.
- Wait for confirmation, refresh, and verify zero allowance or a disabled NFT operator.