Skip to main content

What are Token Approvals?

Token approvals allow users to grant permissions to smart contracts to spend a specified amount of their tokens on their behalf. This is a core feature of ERC20 and similar token standards. This mechanism enables decentralized applications (dApps) to interact with tokens securely and efficiently, allowing for functionalities like trading, lending, and staking.

tip

Token Approvals are required in order to do on-chain swaps.

Why is it Important?​

When approving tokens, users should be cautious about which contracts they grant permissions to. Malicious contracts can potentially drain the user's funds if given unrestricted access. Understanding the security implications helps users protect their assets by limiting approvals to trusted contracts and regularly reviewing and revoking unnecessary permissions.

note

You can use third-party tools like the Ethereum Token Approval Checker to revoke ERC-20 token approvals.

For a security-focused procedure, including how to verify the spender, confirm the revocation, and disconnect the related dApp, see How to Revoke a Suspicious Token Approval.

Before granting a new allowance, follow How to Review a Token Approval Transaction to check the token, spender, contract, amount, and warnings.

Approval Amounts​

An approval can be for a fixed amount or an unlimited allowance. You can increase, decrease, or revoke an approval later.

When you swap a token in Gem Wallet and an approval is needed, Gem Wallet approves an unlimited allowance for that swap's contract (or the Permit2 contract). That way, later swaps of the same token through the same contract don't need a new approval or another network fee. The confirmation screen shows the approval before you confirm. If you stop using a provider, you can revoke it. See How to Revoke a Suspicious Token Approval.

dApps you connect with WalletConnect choose their own approval amount. Gem Wallet shows it, exact or Unlimited, before you confirm.

Input Token Amount Token Approval Screen

Why Did My Swap Use Two Transactions?​

On Ethereum and other EVM networks, swapping a token (not the network's coin, like ETH or BNB) for the first time through a swap contract takes two transactions:

  1. Approve: lets the swap contract use that token.
  2. Swap: the swap itself, sent right after, at the next nonce.

You only tap Confirm once. Gem Wallet signs and sends both, and the Network Fee shown before you confirm includes both transactions. You'll see both in Activity and on the block explorer.

The next time you swap the same token through the same contract, the approval is already in place, so the swap is a single transaction. Swapping a network coin, like ETH to USDC, never needs an approval.

A cross-chain swap can also show two transaction IDs for a different reason: one on each network. See Why Does a Cross-Chain Swap Have Two Transaction IDs?.

Review Permit Signing Requests​

Some dApps request a signed Permit message instead of submitting a separate approval transaction first. Gem Wallet displays the token and approved amount at the top of supported Permit review screens. It can also show the requesting app, selected wallet, network, spender, expiration, and additional message details.

Before signing, verify:

  • The token and amount match the action you initiated.
  • The requesting app and domain are expected.
  • The selected wallet and network are correct.
  • The spender is associated with the intended protocol.
  • The expiration is reasonable.
  • No warning indicates unlimited access, an externally owned spender, or broader NFT permissions than intended.

A Permit signature can authorize token spending even though signing it does not itself require a network fee. Reject the request if any value is missing, unfamiliar, or larger than expected.

See Token Approval vs Permit Signature for a side-by-side explanation of on-chain approvals, Permit messages, fees, submission, and revocation.