Skip to the article
Onchain Brief

News from across crypto

A Permit Signature Sets a Token Spending Limit

A permit signature for token spending lets a named spender use a stated token amount under set rules; expiry and allowance behavior depend on the permit type.

The Onchain Brief Editors3 min read
A Permit Signature Sets a Token Spending Limit

A permit signature for token spending lets a named service use a stated amount of a token under rules the signer approves. A contract checks the signed permission before spending is enabled, so the token, spender, amount and time limits determine what the signature allows.

In a lifi bridge prompt, the permit may be part of letting a route move your token. For context on the approval behind that step, what a bridge token approval authorizes explains how an allowance gives a service permission to spend.

The signature itself is not a transfer. With ERC-2612, the service submits the signed permit to the token contract, which can establish an allowance. Spending can happen in a separate call, so permit execution and token use may be distinct steps.

What does an ERC-2612 permit allow?

An ERC-2612 signature covers the owner, spender, token value, nonce and deadline in EIP-712 typed data. The nonce prevents the same permit from being used repeatedly. The domain ties the signed data to its context, which is why the signer should verify the token contract and chain shown in the prompt.

Say you sign a permit for 100 USDC naming a bridge service as spender. The service can submit that permit to establish an allowance of 100 USDC. That allowance is the spending permission; the signature does not mean the service has already taken 100 USDC.

Before signing, match the token contract and chain to the assets you intend to move. Confirm that the spender is the service you expect and that the amount fits the action. A larger allowance gives the spender room to use more tokens, within the permission’s terms.

When does the permission expire?

An ERC-2612 deadline limits when someone can submit the permit. It does not automatically set an end time for the allowance created by a valid permit. If the permit is submitted before its deadline, the resulting allowance can remain spendable after that deadline, until it is used or changed.

Permit2 has two permission paths. AllowanceTransfer sets an allowance with its own expiration, which limits how long that allowance can be used. SignatureTransfer authorizes a specific transfer through a signature, rather than first establishing a standing allowance. These are different time rules: check the displayed allowance expiration or transfer details, as well as any signature deadline.

Read the prompt as a spending instruction: identify the token, chain, named spender, amount and applicable expiry. Those details show whether you are authorizing an allowance that can remain active or a particular transfer.