To check the token you receive through Wormhole, match its chain-specific token address to the transfer record, not its name or ticker. The same token can have different addresses on different chains, and a wrapped token has its own address.
A token’s name does not prove its identity.
A token’s name and ticker are labels, not proof that it is the asset you intended to move. Anyone can create a token with a familiar name, so two tokens called “USDC” may be different assets.
Think of a token address like a parcel’s tracking number: the label helps, but the number identifies the item. On Solana, check the token’s mint address; on other chains, check its contract address or token type.
Match the token to the transfer record.
Use the source transaction and destination record to confirm which asset the bridge delivered. Keep the transaction hash from the sending wallet so you can follow the same transfer across both chains.
- Confirm both chains. Check that the source and destination match your intended route.
- Match the original asset. Compare its source-chain address or mint with the transfer details.
- Check the received asset. Confirm the destination address and amount after the transfer completes.
Wormholescan can show the cross-chain transfer record; the destination chain’s block explorer shows the token delivered to your wallet. For example, if you sent a token from Solana to Sui, compare the source mint with the asset type shown on Sui. A matching ticker alone does not establish that they are connected.
On a wormhole bridge transfer, the destination asset may be a wrapped version: a token created to represent the original on another chain. That is why wormhole bridge security depends on checking the token’s origin and destination identifiers, not just its display name. Wormhole’s Token Bridge may mint a wrapped asset on the destination, or release the original asset when a transfer returns to its home chain.
Check the wallet can use the received asset.
If the transfer record says the tokens arrived but your wallet does not show them, look up the destination address in the destination chain’s explorer. The token may need to be added to the wallet display using its verified address; adding it only changes what the wallet shows.
Do not swap, send, or approve the token until its address matches the transfer record and the wallet is on the correct destination chain. The amount can also differ slightly if the route charges a fee, so compare it with the completed transfer details rather than expecting the exact amount sent.
Before acting, ask yourself: does the destination token’s address match the asset and route shown in my transfer record?