Gasless vs onchain approvals: who signs and pays
The difference between gasless token approvals and onchain approvals is who submits the authorization: permits start with a signature, but execution still costs gas.
Web3 News Editorial3 min read

Direct ERC-20 approvals make the wallet owner submit and pay for a transaction; gasless permits let the owner sign an authorization for someone else to submit, but both create spending permission through on-chain execution.
A permit is a signed instruction that a smart contract can validate during a transaction. A relayer is a service or other party that submits a signed instruction and pays the transaction fee; “gasless” means the signer avoids that fee, not that execution uses no gas.
What changes when I approve 100 units or sign a permit?
With approve(spender,100), the wallet prompts the owner to send a transaction to the token contract. Once the transaction is confirmed, the spender can use up to 100 units, and the owner has paid the network fee.
With an equivalent ERC-2612 permit, the wallet prompts the owner to sign typed data using EIP-712. The signature authorizes an allowance of 100 units, but signing alone does not update the allowance: someone must submit the permit to the token contract, and that transaction costs gas.
ERC-2612 allows any submitter with the valid signature to call the permit function. The submitter may be a relayer or the spender; the owner does not have to submit or pay for that transaction. The allowance takes effect when the contract accepts the permit on-chain.
Approval-management tools such as revokecash help users inspect and manage permissions their wallets have granted to smart contracts. That is useful for reviewing the on-chain allowance after either flow has executed; a signature that has not been submitted has not yet created that allowance.
When does a permit expire, and how should I check it?
Before signing, inspect the owner, spender, amount, domain, nonce and deadline. The domain binds the typed-data signature to the relevant contract and chain; the nonce prevents the same permit from being accepted repeatedly.
The deadline limits when the permit can be submitted. After it passes, the contract must reject that permit, but an allowance established before the deadline does not automatically expire with it. The allowance remains until it is spent, changed or revoked through a supported on-chain action.
Permit2 uses signatures for token permissions, but it still requires an underlying ERC-20 approval to the Permit2 contract. That initial approval is an on-chain transaction, so signing a Permit2 authorization does not remove every approval transaction or its gas cost.
Choose a direct approval when you are ready to submit a transaction and want to set the allowance on-chain immediately. Choose a permit when the app supports it and you want another party to submit the authorization; review the resulting allowance separately from the permit’s submission deadline.