Every ERC-20 approval you sign burns gas, and most wallets don't show you the bill until it's too late. An approval is a separate on-chain transaction from the swap or deposit it enables, so you pay twice: once to grant spending permission, once to use it. On Ethereum mainnet that first transaction can cost more than the trade itself, especially when you're approving a token for the first time. This guide breaks down where the gas goes, when you can avoid it, and how to stop leaking fees on every interaction.
What an approval transaction actually does on-chain
When you call approve on an ERC-20 contract, you're writing a new value into the token's allowance mapping — a record that says "this spender contract may move up to X of my tokens." That write is a storage change, and storage changes are the expensive part of Ethereum gas.
Two costs stack here. The base transaction fee (21,000 gas) plus the cost of the storage slot update. If the allowance slot was previously zero, you pay the full "cold" storage write. If you're updating an existing non-zero allowance, the cost differs because you're modifying rather than initializing. That's why the same approval can cost noticeably different amounts depending on whether you've approved that token to that contract before.
Why the first approval hurts more
Fresh allowances write to empty storage. Repeat approvals to the same spender usually cost less. A wallet that shows you a flat "approval fee" estimate is almost always wrong about which case you're in.
The spender matters
You're not approving a token in the abstract — you're approving a specific contract address. Approve the wrong contract and you've paid gas for a permission that does nothing for you. Check the spender address before you sign, every time.
Where the gas number on your screen comes from
Your wallet estimates gas using current network conditions and a gas limit that's usually padded above the real usage. The estimate you see is a ceiling, not a receipt. Actual cost depends on base fee at inclusion time and how much of the limit the transaction used.
Here's a concrete scenario. Say you're approving USDC to a DEX router during a busy period. Your wallet quotes a gas limit of around 55,000 and a priority tip. If the base fee spikes before your transaction lands, you pay the higher base fee. If you set the tip too low, the transaction sits pending — and a pending approval blocks the swap behind it. Cancel and retry, and you've now paid for two failed attempts plus the real one.
Approval vs. swap gas, side by side
| Action | Typical gas profile | What drives the cost |
|---|---|---|
| Token approval | Moderate, fixed-ish | Storage write to allowance mapping |
| Swap | Higher, variable | Pool state changes, routing complexity |
| Revoke approval | Similar to approval | Storage write back toward zero |
Notice the revoke row. Cleaning up old approvals isn't free either — you're paying gas to reduce your attack surface. That's a security cost worth budgeting for, not a bug.
How to cut approval gas without cutting corners
You've got real levers here. None of them involve skipping security checks.
- Approve only what you need. An exact-amount approval limits exposure if the spender contract is later compromised. Unlimited approvals save gas on repeat use but widen the blast radius.
- Batch where the protocol supports it. Some routers accept a permit signature (EIP-2612) that skips the separate approval transaction entirely — you sign off-chain and the swap consumes the signature.
- Time your transactions. Base fees move. A quiet weekend window can cost a fraction of a peak-hour approval.
- Audit before you revoke. Don't pay gas to revoke approvals you actually use weekly. Do revoke permissions to contracts you no longer touch.
That last point is where platform hygiene matters. If you're trading through MGBX or reviewing positions on BitMEX-adjacent tooling, keep a running list of which contracts hold live allowances. A quarterly sweep of stale approvals is cheaper than discovering an exploit drained a token you forgot you'd approved in 2023.
The mistake that costs the most
Signing approvals blindly. A phishing contract doesn't need your private key — it just needs one approval transaction you didn't read. The gas cost of that approval is trivial compared to what the allowance lets it do afterward.
Read the spender address. Compare it to the official docs. If it doesn't match, don't sign, no matter how small the gas estimate looks. Cheap gas on a malicious approval is the most expensive transaction you'll ever make.
Frequently asked questions
Do I pay gas every time I approve the same token?
Yes. Each approval is its own transaction and each one costs gas. Repeat approvals to the same spender may cost less than the first because the storage slot is already initialized, but you're still paying for a network write. Wallets that let you set an unlimited allowance are trying to spare you these repeat costs — weigh that convenience against the wider exposure it creates.
Can I get an approval refunded if I change my mind?
Not the gas, no. Once the transaction is mined, the fee is gone. You can revoke the allowance, but that's a second transaction with its own gas cost. Treat every approval as a one-way spend and decide the allowance amount before you sign, not after.
Why is my approval gas estimate higher than my friend's for the same token?
Different wallets, different gas limits, different network conditions at signing time, and different prior approval history for that spender. Estimates are also padded. The only number that matters is the actual fee on the mined transaction, which you can check on any block explorer afterward.
Open your wallet's approval dashboard today and count how many live allowances you've granted to contracts you no longer use. That number is your real exposure — start revoking the oldest ones first.