Before using Wormhole bridge, identify the source token, the transfer route, and the contract that will spend it. This comes first because an approval for the wrong token or spender will not authorize the transfer. Set an allowance that covers the intended amount, confirm it on the source chain, then submit the separate bridge transaction.
-
Check the token, route, spender, and destination asset before approving.
-
Approve only the amount your team intends to transfer.
-
Confirm delivery on the destination chain, then review any remaining allowance.
When does Wormhole bridge need a token approval?
An ERC-20 token usually needs an approval when a contract must pull it from your Ethereum wallet. The approval sets an allowance: the amount a named spender can transfer from that wallet. It does not send tokens across chains. Ethereum’s ERC-20 standard defines the approval and allowance functions.
Approval happens on the source chain, where the tokens currently sit. Native ETH does not use an ERC-20 allowance, and a Solana transfer follows Solana token-account rules rather than Ethereum’s approval transaction. For an SPL token, inspect any delegate authority requested by the transfer; a delegate can spend up to its authorized amount.
Keep token approval separate from a Wormhole message. A team sending only an instruction to a contract on another chain has no token amount to approve for that message. A token transfer may carry a message too, but its source-side token spending still needs the authorization required by the selected route.
How should a treasury choose the spender and amount?
Choose the spender from the actual transfer route, then set the allowance for the planned batch. A route can call a contract other than the one your team expected; approving a familiar address from an old transfer may leave the new transaction unable to spend. Check the source network, token contract, wallet address, and spender address together before signing.
Say your treasury plans to send 5,000 USDC from Ethereum for payouts on Solana. USDC has six decimal places, so an approval for 5,000 USDC represents 5,000,000,000 base units. An allowance of exactly 5,000 covers that batch; an unlimited allowance avoids repeat approvals but leaves more of the wallet’s future balance available to that spender.
Allow time and native gas for both the approval and the source transfer. If the route requires a manual claim, someone must also fund and submit the destination transaction; an available relayer may do that for a fee. These costs vary with network activity and route, so check them before scheduling a payout.
What steps prepare the team for a transfer?
Prepare the transfer in this order: settle the route and destination asset, approve its spender if required, then send and reconcile the transfer. This order matters because the same source token can arrive in different forms depending on the route. For example, a wrapped token on Solana may not meet a payout requirement for native USDC.
For a Wormhole token bridge payout, decide what the recipient must hold before anyone signs an allowance. If the payout needs tokens on another chain, use Wormhole bridge to move them after confirming the spend authorization; if the job only needs an authenticated contract instruction, use its messaging path. Record the chosen source asset and expected destination asset in the team’s approval request.
-
Confirm that the exact token and source-to-destination route are available, and record the recipient address and expected destination token.
-
Read the wallet’s approval request: verify the source chain, token, spender, and amount against the approved payout batch.
-
Wait for the approval to confirm. Check the on-chain allowance for that wallet, token, and spender before submitting the transfer.
-
Send a small first transfer when using a new route or destination asset. Confirm what arrived before releasing the full batch.
For a business wallet, the person reviewing the approval should see the same route details as the person preparing the payout. If an approval is already in place, check its remaining allowance rather than assuming the original amount is still available. A prior transfer may have consumed it.
What happens after approval and the source transfer?
After approval, the source transaction spends the tokens and starts the cross-chain transfer. In Wrapped Token Transfers, the original asset is locked or an existing wrapped asset is burned; Wormhole Guardians then sign a transfer message called a VAA. The destination transaction verifies that message and mints the wrapped asset or releases the original asset, as described in Wormhole’s transfer flow.
When you bridge tokens with Wormhole, a confirmed source transaction alone is therefore not proof of delivery. Reconcile the source transaction, the destination transaction, the recipient balance, and the token’s identity. If the route needs a manual claim, finish that claim before marking the payout complete; afterward, review whether the source allowance should remain for the next batch or be reduced.
What should the team confirm before a live payout?
Confirm why the asset must move, what authority the approval grants, and what token the recipient will receive. Those three answers determine whether the route fits the payout.
Why use it to move tokens?
Use a cross-chain transfer when your treasury holds an asset on one chain but must fund an account on another. The bridge coordinates the source spend and destination delivery through a verified message. For recurring payouts, the practical decision is whether the destination token and claim process match what your recipient can use.
Is it safe to use?
Safety depends on both the bridge route and the permission you grant before using it. Check the spender address and cap the allowance to the approved batch when repeated access is unnecessary. A successful approval proves only that spending permission exists; verify the destination receipt separately before your team closes the payment.
Can tokens go from Solana to Ethereum?
Yes, when the selected Solana token and destination route are supported. Solana-side authorization may involve a token-account delegate rather than an ERC-20 allowance; an ERC-20 approval becomes relevant when that token is later spent on Ethereum. Before acting, ask: Will the exact token delivered on Ethereum satisfy the recipient’s payout requirement?