What Are Token Approvals? The Permission That Drains Wallets
You've signed dozens of these. Here's what each one actually granted.
Merlin
Author

The first time you swap a token on any EVM chain, your wallet asks you to sign two things. The second is the swap. The first is an approval, and it's the one most people don't read.
An approval is you granting a contract permission to move a specific token out of your wallet. Not the swap itself, the permission to perform swaps. That permission persists after the transaction, and it's the mechanism behind a large share of everything covered in how wallets get drained.
Why they exist
Tokens on EVM chains follow a standard where the contract holding your tokens and the contract doing something with them are separate. A DEX can't reach into your wallet and take tokens. You have to tell the token contract "this DEX is allowed to move up to X of my tokens," and then the DEX can execute within that limit.
That's a sensible design. The problem is what the default limit became.
The unlimited approval problem
Most interfaces request unlimited approval by default. Not "move 500 of my tokens for this swap" but "move any amount of this token, forever." It's done for convenience so you don't have to approve before every trade.
Which means after a year of trading you've granted unlimited access to your tokens to dozens of contracts, from sites you've forgotten, some of which may no longer be maintained, some of which may get exploited later. Every one of those approvals is live until you revoke it.
An approval doesn't expire. It doesn't care whether you still use the site. It's a standing permission, and if the contract you granted it to is ever compromised, the attacker inherits it.
How drains actually use them
Two main patterns.
A malicious site gets you to approve. You visit something that looks legitimate, connect your wallet, and it requests an approval for a token you hold. The request is dressed up as a mint, a claim, a verification. You sign it. Nothing happens immediately. Later, the contract you approved moves your tokens out. Because you already signed, no further interaction from you is needed.
A legitimate contract gets exploited. You approved a real DEX two years ago. It gets hacked. The attacker now has whatever permissions every user granted, including yours, and drains what they can.
Neither requires your seed phrase. That's the important part. People assume "I never shared my seed" means they're safe, and approvals are the reason that's wrong.
On Solana it works differently
Worth being clear because most approval content is EVM-only.
Solana's token model doesn't use the same standing-approval pattern for ordinary swaps. Drains there more commonly work by getting you to sign a transaction that directly transfers tokens or changes account authority. So the "revoke your approvals" advice is primarily an EVM thing, and on Solana the equivalent discipline is reading what a transaction actually does before signing it, since the damage is usually done in the signature itself.
The general principle holds on both: signing is the moment of risk, not connecting.
How to check yours
Approval checker tools let you paste a wallet address and see every live approval across chains, which contract holds it, and for how much. Most also let you revoke from the same screen.
The first time you run one after a year of trading, the list is usually startling.
How to revoke
Revoking is a transaction, so it costs gas, and it sets the allowance back to zero. On expensive chains that adds up if you've got dozens, so prioritise: unlimited approvals to contracts you don't recognise first, then anything you no longer use, then the rest.
Worth doing every month or two rather than once. Approvals accumulate.
The habits that prevent it
Approve exact amounts where the interface allows it. Slightly more friction, meaningfully less exposure.
Use separate wallets. A trading wallet accumulates approvals. Your holdings shouldn't be in it. The reasoning is in the wallet setup guide, and approvals are most of that reasoning.
Read approval requests. Which token, which contract, what amount. If you're on a site claiming to mint an NFT and it wants unlimited approval on your USDC, that's the tell.
Be suspicious of approvals on sites you arrived at via a link. Legitimate services don't need permission on tokens unrelated to what you're doing there.
Revoke after using something once. If you tried a new DEX and won't return, the approval doesn't need to outlive the visit.
Where trading bots fit
A Telegram bot generates its own wallet, which means it's a fresh address with no approval history, and the approvals it grants are to the routers it trades through. That's cleaner than a browser wallet that's been connecting to sites for a year.
It's also why custody matters. The bot's wallet is only as safe as the key infrastructure behind it, which is covered in what non-custodial actually means.
Axxel runs on Turnkey's key infrastructure across Ethereum, Base, BSC, Solana and Robinhood Chain, with market, limit, trailing and sniper orders, stop loss and take profit, MEV protection and configurable slippage. Flat 0.9%, non-custodial, no subscription.
The wallet you trade from will accumulate approvals. That's normal. The mistake is letting it also hold everything you own.
Crypto trading carries risk. Most memecoins lose value. Nothing here is financial advice. Axxel is not available in all regions.


