Revoke.cash

• Name: Revoke.cash
• URL: https://revoke.cash/
• Category: wallet security / token-approval management / wallet-hygiene tooling
• Tags: ethereum-ecosystem
• Summary: Revoke.cash is approval-hygiene tooling for EVM users. Useful, sometimes very useful, but keep it in proportion: this is mainly a cleanup utility plus warning and education surfaces around lingering token authority. It is not the wallet, not the custody stack, and not a recovery service.
• What it does:
  • Lets users inspect which contracts have token/NFT spending approvals on their wallets and revoke or reduce those approvals when no longer needed
  • Supports multichain approval management across a large EVM network set, with chain support implemented through RPCs, explorer APIs, and related infrastructure in the public codebase
  • Publishes an educational “Learn” section covering wallet basics, token approvals, Permit/Permit2, and common scam patterns to help users understand what the tool is mitigating
  • Operates a browser-security extension line aimed at warning users about risky allowance signatures and related phishing flows
  • Maintains open-source repos for the approvals dashboard, chain metadata/support, browser extension work, and known approval-exploit data
• Key claims:
  • The homepage positions Revoke.cash as a tool to “take back control” of a wallet by revoking lingering token approvals that dapps can otherwise keep using indefinitely
  • Official copy repeatedly frames the product as preventative wallet hygiene: useful periodically, useful after scams to limit further damage, but not capable of recovering already stolen assets
  • The About page says the project was started in 2019, expanded into a broader security toolkit, and is maintained as open-source web3 infrastructure funded by donations and grants rather than by a token or VC raise
  • The public app repository reveals unusually concrete technical scope for a consumer security product, including chain-addition criteria, dependency on RPC / explorer / indexer surfaces, and support for many EVM networks
  • The GitHub organization shows Revoke.cash is more than a single website: it also ships browser-extension code, approval-exploit lists, and related data repos that reinforce its role as operational wallet-security infrastructure
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were Revoke.cash’s official homepage, About/Learn pages, verified GitHub organization, main application repository, and browser-extension repository; see ../whitepapers/revoke-cash-primary-sources-2026-04-25.md.
• Sources:
  • https://revoke.cash/
  • https://revoke.cash/about
  • https://revoke.cash/learn
  • https://github.com/RevokeCash
  • https://github.com/RevokeCash/revoke.cash
  • https://github.com/RevokeCash/browser-extension

Internal linkages

• Best upward comparisons: blockaid and blowfish.
• Keep rabby nearby when the question is how wallet clients surface approval risk before or after cleanup becomes necessary.

Control surface

• The onchain part is plain enough: approvals live onchain and revocation is just another transaction.

• The leverage sits around that core utility: which chains and approval types are supported, how signatures are labeled, what gets flagged as risky, and how forcefully the product pushes users toward routine cleanup.

• Treat Revoke.cash as useful wallet-hygiene infrastructure, not as the wallet or the deeper account-policy stack.

• Last reviewed: 2026-06-04 UTC