A separate approval is needed when the source-chain token contract requires you to authorize the bridge contract to spend your tokens before it can start a transfer. On EVM chains, that usually means two transactions: one to set an ERC-20 allowance, then one to call the bridge. Comparing routes means counting both transactions’ gas and checking who receives that allowance.
The approval sets an allowance for one spender
An ERC-20 token balance does not let a bridge contract move tokens by itself. The token owner calls approve(spender, amount), which records an allowance for that specific spender; later, the bridge calls transferFrom(owner, bridge, amount). Wormhole’s published Bridge.sol uses this transferFrom pattern to take custody of source-chain tokens.
The spender should be the contract that will pull the tokens on the source chain, not a destination-chain contract or an address labelled only as a relayer. For a Portal Bridge route using Wrapped Token Transfers, the allowance lets the source Token Bridge take the selected amount before it locks native tokens or burns a wrapped representation and publishes the cross-chain message.
The allowance is separate from the transfer’s other costs. You pay source-chain gas for the approval transaction and again for the bridge call; the latter may also require the chain’s native asset for messaging or relaying fees. If your comparison depends on the route’s service charges, Portal Bridge fees matter alongside those two gas costs, rather than instead of them.
Existing allowance changes the number of transactions
If the token already has enough allowance for the correct spender, the bridge call can usually proceed without another approval. Otherwise, the interface may request an allowance for the exact input amount, or offer a larger allowance to avoid repeating the approval on later transfers. An exact allowance limits how much that contract can pull under the authorization; a maximum allowance is more convenient but leaves more spendable authority if the contract or its permissions are compromised.
For example, suppose you hold 100 USDC and want to bridge 40. With zero allowance, you approve 40 USDC, wait for that transaction to confirm, then submit the bridge call. The approval does not move any tokens or start the cross-chain message; if you reject the second transaction, the allowance remains until used, changed, or revoked.
EIP-20 says interfaces should set an existing nonzero allowance to zero before changing it to another value, because a spender could use the old allowance before the update and then use the new one. Some tokens enforce this reset-to-zero pattern, so an approval update can itself take two transactions. Permit signatures can sometimes authorize spending without a separate on-chain approval, but support depends on both the token and the route; don’t assume a wallet prompt for a signature replaces an allowance transaction in every case.
Check the spender and token behavior before signing
Before approving, verify the token, source chain, spender address, and allowance amount in the wallet prompt. The spender should match the source-side bridge contract shown for that route. If the UI offers maximum approval, choose it only if the repeat-use convenience is worth the broader allowance to you.
Some edge cases make the displayed amount or approval state confusing. A token that charges a transfer fee may deliver less to the bridge than the requested amount, and non-standard tokens can fail on allowance updates or return values; Wormhole’s bridge code measures its balance change for native-token deposits to account for transfer-fee behavior. On Solana, token programs use a different authorization model, so the EVM approve-and-transferFrom sequence does not apply.
For comparing routes, I would count the approval as a separate source-chain transaction whenever the allowance is missing, then compare the combined gas and any route fees. A practical habit: after bridging, review the token’s allowance for that spender and revoke any unused amount you don’t want to leave available.