How Auto-Revoking Works
Everything you should know about Auto-Revoking before you subscribe: how it protects you, what it needs, and where its limits are.
From setup to protection
Grant a revoke-only permission
Connect with MetaMask and grant Revoke.cash an ERC-7715 permission that can only be used to revoke approvals. It cannot transfer funds, sign messages, or do anything else, and you can withdraw it at any time.
Set your rules
Choose what should be revoked automatically: approvals to exploited or risky spenders, approvals older than your staleness threshold, or both. Every wallet on your subscription can tune its own rules.
We keep watch
Revoke.cash continuously monitors your approvals across all supported networks and checks them against your rules and our exploit database, around the clock.
Dangerous approvals get revoked
When an approval matches your rules, a revoke transaction is sent on your behalf and appears in your activity log. Exploit-triggered revokes are treated with higher urgency.
Supported wallets & networks
Auto-Revoking currently requires MetaMask, the first wallet to support ERC-7715 permissions. Granting these permissions requires upgrading your wallet to an ERC-7702 smart account. Support for more wallets and networks will follow as the standard gets adopted. It currently works on 10 networks:
Ethereum
BNB Chain
Polygon
Base
Arbitrum
Optimism
Monad
Linea
Gnosis Chain
UnichainGas fees are included
Your subscription includes a $5 monthly gas budget that pays for automated revoke transactions. When the budget is used up, routine revokes wait for the next monthly cycle, but exploit-triggered revokes still go through. To spend your budget efficiently, individual revokes are capped at $2 and may be deferred temporarily during gas spikes.
What Auto-Revoking is not
Auto-Revoking is best-effort protection: it meaningfully reduces your risk, but it cannot guarantee that losses are prevented. Detection can lag since an exploit must be identified before it can trigger a revoke, and an attacker may act first. On-chain execution depends on conditions outside anyone's control, such as network congestion and gas prices. See our Terms and Conditions for details.