An infinite token approval is an allowance set to the largest value an interface or token supports, commonly type(uint256).max for an ERC-20 token. It lets a named spender call transferFrom up to the remaining allowance without asking the owner to approve each amount separately. It is a convenience choice with an ongoing permission risk; it does not by itself mean that a spender has taken funds.
How ERC-20 allowances work
The ERC-20 approve(spender, amount) function sets the amount that a spender may withdraw, and allowance(owner, spender) reports the remaining permission. A spender uses transferFrom to move tokens within that allowance. Calling approve again replaces the existing allowance with the new value. Token implementations differ in details; for example, some treat the maximum uint256 value as a sentinel and do not decrement it after transfers.
Exact and maximum allowances
An exact approval grants only the amount needed for a particular action, so another interaction may require a new approval transaction. A maximum allowance can reduce repeated approval steps but remains available for later calls until it is spent, changed, or revoked according to the token’s implementation. Wallet interfaces may request different amounts; users should read the token, spender, and amount displayed before signing.
Risk and revocation
If a spender is compromised, malicious, or has a vulnerable authorization path, an outstanding allowance can permit token transfers up to its remaining limit. The risk depends on the specific token and spender contract, its controls, and the wallet’s authorization. Revoking or reducing an allowance changes future permission; it cannot reverse transfers that already happened. Approval-management tools should be checked carefully, including the contract address and network.
Permit2 and other approval flows
Uniswap Permit2 supports one-time signature-based transfers and separate time-limited allowances. Using Permit2 still requires an ERC-20 approval for the Permit2 contract itself, often a maximum allowance. That underlying permission and each Permit2 authorization are distinct. A token-native permit standard such as EIP-2612 uses a signed message when supported by the token; it also does not remove the need to understand the spender and permission being authorized.
Related Terms
See Also
Sources
Last updated: 29 October 2026