Skip to content

Analysis · DeFi

Token approvals and signed permits: the standing permissions Ethereum users forget

An ERC-20 approval lets another address move your tokens until it is used up or changed. A permit grants the same thing with a signature instead of a transaction. Both outlast the trade that needed them.

By Etherelysium Editorial TeamUpdated 18 November 20263 min read

Token approvals and signed permits: the standing permissions Ethereum users forget
Share X LinkedIn

Many wallet losses on Ethereum are not hacks in the technical sense. A user granted a permission, and the permission kept working long after the reason for it was forgotten. Understanding how token permissions work is a better defence than any single tool.

What an approval is

ERC-20 tokens do not let a contract reach into your wallet. Instead you grant an allowance. The token standard describes approve as allowing a spender “to withdraw from your account multiple times, up to the _value amount”, and notes that calling it again “overwrites the current allowance”. The spender then uses transferFrom to move tokens on your behalf.

Three properties surprise people:

  • It persists. The allowance is not consumed by the trade it was granted for. It remains until spent or changed.
  • It is often unlimited. Interfaces frequently request the maximum value to avoid asking again. That covers your entire balance of the token, including tokens you receive later.
  • It is tied to an address, not an app. You are trusting a contract address. If a website is compromised and asks you to approve a different address, nothing on screen needs to look wrong.

Permits: approvals by signature

ERC-2612 lets tokens accept approvals as signed messages instead of transactions: permit “allows users to modify the allowance mapping using a signed message”. You pay no gas to sign, and someone else submits it. The standard notes that a deadline can be set so high that a permit “effectively never expires”, that anyone can front-run its submission, and that a relayer can sit on a signed permit and choose not to submit it.

The practical difference: a permit does not appear anywhere until someone uses it. A malicious site that collects a permit signature can wait. Some marketplace orders and wider permission schemes work the same way, which is why not every grant appears in an explorer’s approvals view.

Since Pectra: delegation is a bigger grant

EIP-7702, live since May 2025, adds a third kind of signature: an authorization that sets your address to run another contract’s code. Its specification warns that delegated code “has unrestricted access to the account”. That is not a token allowance; it is closer to handing over the account. Our explainer on smart accounts after Pectra covers it.

Checking what you have granted

Approvals are public data. A block explorer’s token-approvals view for your own address lists every spender and allowance, per token, without connecting a wallet or signing anything. If a site insists on a wallet connection before it will show your approvals, close it. Look for spenders you cannot tie to a protocol you used on purpose, protocols you no longer use, and unlimited allowances on large balances. What you do about them is your decision, taken through an interface you already trust and reached by a route you already know; after any public incident, fake “revoke” and “checker” sites appear quickly.

What reviewing approvals does not cover

A leaked seed phrase, which gives away the whole account. A malicious transaction you sign yourself. Off-chain signatures that have not yet been used. Assets held on an exchange, which have no on-chain approvals of yours attached.

The Settlement Test

  • What settles: an approve call settles as an ordinary transaction and the allowance is stored on-chain; a permit settles only when someone submits it.
  • What it costs: gas for each approval or change; nothing for signing a permit, which is part of why permit phishing is cheap to attempt. See our gas and fees page.
  • What breaks: a compromised spender contract or front end can drain any allowance it holds, at any time, for as long as the allowance exists.

Before approving anything, confirm the spender address, prefer a specific amount over unlimited for one-off actions, and read every signature request as if it were a transfer. Related: who can change the contract you approved.

Primary sources

Educational content, human-edited and possibly AI-assisted. It describes how systems work and is not financial, legal or tax advice. Report an error via our corrections page.

More in DeFi

Related articles

See all