π§Ή The Great Revoker
The approvals we can actually see on your Sonic wallet, what each one can take, and a button to take it back. One blind spot, named below, not buried. π
or look without connecting anything β
π Everything else on Sonic
Not ours. We can tell you what you approved and whether the address has any code β we can't vouch for any of it. π
π₯οΈ Audit log
π₯ BLAZE contracts
Every contract we run, and exactly what you have granted each one.
π What even is an approval?
When a dapp wants to move your tokens, it can't just take them. You sign an approval first β a standing permission that says "this contract may move up to X of my token." It stays until you take it back. That's the bit nobody tells you. π«
Most dapps ask for unlimited because it's convenient β one signature forever instead of one per trade. Convenient right up until that contract gets drained, at which point the permission you forgot about is the door. πͺ
Revoking is a transaction, so it costs a little gas, and here it's
one signature per approval β approve() only ever listens
to you, so ten approvals means ten prompts on this page. A smart-account
wallet can bundle several calls into one signature; an ordinary EOA wallet cannot,
and this tool doesn't pretend to. π
π New since BLAZE got pools: swapping on a Sonic DEX means approving a router first, and plenty of front-ends route through Permit2 on top of that. Those are real, standing approvals β they show up under π Everything else on Sonic, and they're exactly the ones worth sweeping once a trade is done. π
One blind spot, stated up front: Uniswap's Permit2 holds allowances inside its own contract. We can show you that you approved Permit2 β we cannot see what Permit2 is allowed to do downstream. Anyone claiming a complete picture of your approvals without an indexer is overselling it, us included. π€·