Revoke Token Approval

WHAT IT DOES

This tool connects to your EVM wallet and reads all active token approval allowances for ERC-20, ERC-721, and ERC-1155 tokens. For each approval, it shows the spender address (the contract or wallet authorized to move your tokens), the exact approved amount (or "unlimited" for max uint256), the token contract address, and the block number or timestamp when the approval was set. It also displays your current wallet address and the network chain ID to confirm you're on the right network. The interface presents approvals in a sortable, filterable list so you can identify stale or suspicious allowances at a glance. You can revoke any approval directly by submitting a transaction to set the allowance to zero, which removes that spender's permission to transfer your tokens.

HOW TO USE

Connect your EVM wallet (MetaMask, WalletConnect, Coinbase Wallet, etc.) to the tool. The tool automatically detects your current network and wallet address. It then scans the blockchain for all approval events and current allowance states associated with your address. The results appear as a table with spender addresses, token symbols, approved amounts, and timestamps. To revoke an approval, click the "Revoke" button next to the entry, confirm the transaction in your wallet (this costs gas), and wait for the transaction to confirm. After confirmation, the approval is removed and the list updates automatically. You can also revoke multiple approvals in sequence, though each requires its own transaction.

TECHNICAL MECHANISM: MULTI-RPC LOG SCANNING WITH ADAPTIVE BACKOFF

Unlike simpler tools that call allowance() once per token, this tool reconstructs approval state by scanning historical Transfer and Approval events across the entire lifetime of each token contract relevant to your address. It fetches logs in parallel using multiple public RPC endpoints. Because public RPCs enforce different max block range limits (some allow 10,000 blocks, others only 2,000), the scanner dynamically chunks requests per endpoint and reduces chunk size on 403/429 errors with exponential backoff (starting at 2048 blocks, halving on failure). A failed chunk on one RPC does not abort the scan; the tool retries that chunk on a different RPC endpoint. It also cross-references current allowance() calls as a final verification, because some proxies emit events inconsistently. This hybrid approach catches approvals that are still active even if the token contract does not emit an Approval event for every state change.

WHAT IT CANNOT SEE

This tool cannot detect approvals set via non-standard proxy patterns where the allowance storage is not at the standard ERC-20 slot or where the proxy does not forward allowance() calls correctly. It cannot see approvals that were set and then modified through mechanisms that do not emit standard Approval/ApprovalForAll events. It cannot revoke approvals that are governed by contracts you do not own or that use custom authorization logic outside the ERC-20/721/1155 standards. It cannot detect approvals that were set by other addresses (only your connected wallet). It cannot see allowances on tokens that do not implement the standard allowance() or isApprovedForAll() functions. It cannot operate on non-EVM chains or on private/permissioned blockchains. Gas fees for revocation transactions are not covered by this tool.

PLEASE NOTE

This tool works exclusively on Ethereum Virtual Machine (EVM) compatible chains including Ethereum Mainnet, Polygon, Arbitrum, Optimism, Base, BSC, Avalanche C-Chain, and others. It does not support Solana, Bitcoin, Cosmos, or any non-EVM architecture. Always verify the network shown matches the network where you hold your tokens before attempting revocation. Revoking an approval does not recover already-transferred tokens; it only prevents future transfers by that spender. Some spenders (like DEX routers) may require active approvals for normal function — revoking them will break those services until you re-approve.