Send the tokens to a blockchain and token format the recipient can actually access, or choose a different delivery method. First confirm the destination network, the recipient’s address for that network, and whether their wallet can display and send the token; a transfer can arrive successfully while remaining unusable in their app.
Check what the recipient’s wallet supports
Ask the recipient which blockchain they can use and whether their wallet supports the specific token there. A wallet may support a network but not show every token on it, or it may show a token on one network while lacking access to another.
Check the destination network as well as the address. Some networks use addresses with similar formats, but an address that looks right is not proof that the recipient can access funds sent on a particular chain. Copy the address from the recipient’s wallet with the intended network selected.
These are different problems: if a wallet supports the destination chain but does not list the token, the token may still arrive and be visible after the recipient adds its contract address. If the wallet cannot connect to that chain at all, adding a token entry will not help; the recipient needs a compatible wallet or another route.
Choose a transfer route that ends with usable funds
A cross-chain bridge moves an asset from one blockchain to another, often by locking or burning it on the source chain and releasing or creating a corresponding token on the destination. For supported routes, wormhole bridge uses cross-chain messages verified by Guardians; the recipient still needs a wallet that can access the destination chain and token.
Before sending, check the route’s supported source and destination networks, the token you will receive, and any extra action required to claim or redeem it. For example, if a route supports moving a token from Solana to Base, confirm that the recipient can use the token’s resulting form on Base. A token with the same ticker may be a different asset or a bridged representation.
Use this order to avoid sending funds into a wallet the recipient cannot use:
- Have the recipient name a supported destination network and copy its address from a wallet on that network.
- On the bridge or exchange, select the matching source network, destination network, and token.
- Read the quoted amount and fees, then check whether the transfer needs a separate claim or destination-side gas to move the funds later.
- Send a small test amount if the route and fees make a test practical; confirm it arrives before sending the rest.
The total cost can include a source-chain transaction fee, a bridge fee, and a destination-chain fee. These vary with network demand and route design. Keep some of the destination chain’s native token available if the recipient will need to approve, swap, or send the received asset; receiving a token does not always provide the funds needed for those actions.
Verify the arrival before deciding what to do next
After the transfer, use the bridge’s status and the destination chain’s transaction record to confirm completion. Check the recipient address, token contract, and amount on that chain. A balance missing from the wallet’s screen may mean the app has not added the token, while a transaction that has not completed needs more time or a status check.
If the token arrived but the wallet cannot use it, ask the recipient to connect a wallet that supports that chain, or use an exchange route only when the exchange accepts deposits on the exact network and token. Never ask for a seed phrase or private key to “fix” a wallet display issue.
When comparing routes, people researching wormhole bridge should check the destination token and wallet support alongside the transfer fee. The right choice changes if the recipient can access the chain but needs a token added; if they cannot access the chain, choose a route that delivers to one they can use.
Top comments (0)