How to Use revokecash: Remove and Verify Wallet Permissions
revokecash helps you inspect wallet approvals, revoke unwanted permissions, and verify the on-chain result. Start with your wallet address and the network where you granted an approval. Match the token and spender, connect the wallet that owns the permission, and sign the revocation. Once the transaction confirms, refresh the permission: an ERC-20 allowance of zero or an ERC-721 operator approval of false means the selected permission has been removed.
What should you prepare before revoking?
Before revoking, identify the owner account, network, token, and spender involved. An ERC-20 approval gives a spender permission to withdraw tokens from an owner’s account up to the remaining allowance. An ERC-721 operator approval lets an operator manage the owner’s NFTs in a collection. A separate ERC-721 approval can cover just one NFT.
These permissions persist on-chain until they are changed. Disconnecting your wallet from a website ends that website session; it does not change an ERC-20 allowance or an NFT operator approval. You need a revocation transaction to remove a permission you no longer want.
Have your wallet address ready for public inspection. To submit a revocation, you also need signing access to the owner wallet and enough of the network’s native token to pay gas. The required gas payment changes with network conditions and the transaction. Keep your recovery words private: inspecting an address and signing a transaction never require you to share them.
Open the official domain by entering it yourself in your browser. You can inspect a public address first, then connect the owner wallet when you are ready to sign. revokecash.io is an option for reviewing permissions your wallet has granted and revoking approvals you no longer need.
How do you use revokecash to remove a permission?
To remove a permission with revokecash, inspect the right account and network, identify the approval, select revoke, and review the transaction before signing. Ethereum, Base, and BNB Chain have separate on-chain permission states. Start with the chain on which you granted the approval, even when the same wallet address appears on another chain.
- Confirm that the displayed owner address matches the wallet you control. If you use several accounts, compare the full address rather than its shortened label.
- Find the token and the spender or NFT operator you intend to remove. Use filters and approval history to narrow the search, especially when you remember roughly which interaction created the permission. Compare contract addresses; a token symbol or familiar name alone is an uncertain match.
- Select the unwanted permission for revocation. Say you approved a DeFi contract to spend an ERC-20 token for a trade you have finished. That approval may still carry a remaining allowance. Revoking it sets that spender’s allowance for the token to zero.
- Read the wallet prompt before signing. Confirm the owner account, network, destination contract, function arguments, and gas quote. Sign only when they describe the permission you chose.
The destination and arguments deserve a careful look. For a direct ERC-20 revocation, the transaction targets the token contract and calls its approval function with the spender address and an amount of zero. The spender appears in the function arguments; it is not the transaction destination. Verify both addresses against the permission you identified. A correct token contract paired with the wrong spender leaves the unwanted allowance in place.
For a direct ERC-721 operator revocation, the destination is the NFT contract. Its arguments identify the operator and set approval to false. Verify that collection contract and operator address separately. If the wallet presents undecoded transaction data, use a trusted way to decode it before signing rather than guessing from the destination alone.
How do you confirm the result and solve common problems?
A revocation is complete when the transaction succeeds on-chain and the current permission shows the intended value. Wait for confirmation, inspect the transaction receipt for success, and refresh the approval view. For ERC-20, the token’s allowance for your owner address and that spender should be zero. For an ERC-721 operator, the contract’s operator approval for your address should be false. A submitted transaction or closed wallet prompt is only an intermediate step.
If the wallet reports insufficient gas, fund that account with the native gas token on the same network and try again. If you reject the wallet prompt, no revocation is submitted; return to the permission and review a new prompt. If a transaction stays pending, follow its transaction hash and wait for its final status before sending another revocation. If it reverts, read the receipt or error, confirm the account and contract details, and try again only after you understand what failed.
If the approval seems missing, revisit the owner address, network, token type, and active filters. Approval history can help you identify a past interaction, but the current permission state determines whether a revocation is still needed. A permission on Ethereum will not appear as the same on-chain permission on Base or BNB Chain.
Revoke.cash wallet security is most useful when you can identify the exact permission you want to clear. Use revokecash to review that wallet permission and revoke it after you have matched its token contract and spender. Then confirm the receipt and read the updated allowance or operator status.
You are done when each selected ERC-20 allowance reads zero or each selected ERC-721 operator approval reads false.
What might you review next?
How should Permit2 permissions be reviewed?
Review both the ERC-20 allowance granted to the Permit2 contract and any permissions Permit2 grants to individual spenders. They are distinct permissions with different scopes. Identify the token, spender, and any expiration before deciding which one to remove, then verify its current state after the change.
How can developers automate approval monitoring?
Track approval events by chain, owner, token contract, and spender or operator, then query the contracts for current allowance and operator status. Events show changes over time; current contract state tells you which permissions remain active. Alert on new or increased permissions and reconcile the records after confirmed transactions.