Spender Address in a Token Approval: How ERC-20 Encodes It
What is the spender address in a token approval? It identifies who can transfer your tokens from your wallet, up to the allowance recorded by the token contract.
The Blockheight Editors··2 min read
The spender address in a token approval identifies who may transfer a specified token from your wallet, up to the allowance recorded by that token’s ERC-20 contract.
When you approve a contract to use USDC, the approval records permission; the USDC stays in your wallet until a transfer occurs. The spender can then call transferFrom within the allowance.
A lifi bridge quote can show the route’s spender as estimate.approvalAddress. For background on the risks around that route, see lifi bridge transfer risks, which adds ways to reduce them before a transfer.
ERC-20 defines approve(spender, value) to set permission and allowance(owner, spender) to read the permitted amount. The token contract stores that permission for the owner and spender pair.
Say Alice approves Router R to spend 100 USDC. The USDC contract records an allowance of 100 for R, which can use transferFrom to move USDC from Alice’s wallet; a separate address may receive the tokens.
That distinction matters when you review a wallet prompt. The transaction’s To address is the USDC token contract, because that is where Alice calls approve; Router R is the spender encoded in the approval’s arguments.
The spender is not the token contract or necessarily the eventual recipient. The token contract records the permission, the spender may use it, and the recipient is where a transfer sends tokens.
Before signing, decode the spender argument and compare it with authoritative deployment information for the same chain. For a lifi bridge route, compare it with the quote’s estimate.approvalAddress; the route can involve different bridges or exchanges, so use the address for that quote.
Once the approval is signed, the allowance lets the named spender transfer up to the approved amount from the owner’s balance. The approval itself records that permission; the later transfer depends on the spender using it.