Skip to content
Crypto Bulletin

Markets, protocols and policy news

ID 74b469

Ethereum Token Approval: Spender vs. Token Contract

To check the spender address on an Ethereum token approval, open the confirmed transaction and read approve(spender, amount); verify it against the app’s official details.

Crypto Bulletin Newsroom 3 min read

Ethereum Token Approval: Spender vs. Token Contract

To check the spender address on an Ethereum token approval, open the confirmed transaction and read the address in its decoded approve(spender, amount) call. That address can differ from the transaction’s to address, which is usually the ERC-20 token contract receiving the approval.

Where is the spender address?

The spender is the address inside the approve call’s spender argument. Start with the confirmed approval in your wallet’s activity or search its transaction hash on Etherscan, and make sure the explorer shows the correct Ethereum network and token.

For an eigen layer deposit, compare that address with official contract details for the same token and deposit flow. That’s the practical first step when checking why an eigen layer deposit is missing: confirm the spender before retrying or changing the approval.

In the transaction details, expand the decoded input data and find approve(spender, amount). Read the first argument as the spender; the second is the approved amount. MetaMask or an explorer may show decoded data in different places, so look for the function name and its arguments.

The transaction’s to field answers a different question: which contract received the transaction. For an ERC-20 approval, that is generally the token contract. The spender is the address the token contract was told it may use up to the approved amount.

How do you verify the address before retrying?

Verify the spender by comparing the full address with the intended app’s official contract information for that token and flow. Don’t identify it from the token contract or your wallet address alone, and don’t rely on an address copied from an unrelated transaction.

Say your deposit is missing after you approved a token. The confirmed transaction shows the token contract in to, while decoded input shows approve(0x…, amount). Treat the address represented by 0x… as the candidate spender, then check every character against the app’s official details for that specific deposit. This example describes what to inspect; it does not supply a contract address.

If the addresses match, you have identified the contract granted permission; that helps separate an approval issue from a later deposit step. If they do not match, don’t assume the approval was for the intended flow. In eigen layer, use the official contract details for the selected token and flow rather than guessing which contract should appear.

The spender argument identifies who can use the approved tokens, while to usually identifies the token contract that recorded the approval. Reading both fields correctly lets you verify the permission against the app’s official details before deciding what to do about the missing deposit.