Wormhole bridge routes: how to choose where your token goes

A wormhole bridge transfer can deliver a wrapped version of a token or the token’s native form, depending on the route available for that asset and chain pair. That difference matters if you plan to trade, deposit or use the tokens after they arrive. Wormhole moves tokens and messages between Solana, Ethereum and many other blockchains. If you need to move an asset or message between chains, use the Wormhole bridge for cross-chain transfers for that step. First check which token the destination needs and whether you can complete the final transaction there.

How does a Wormhole bridge move tokens?

A transfer starts when you send tokens to a bridge contract on the source chain. The contract records the transfer, and Wormhole’s Guardian network signs a proof of it. That signed proof is then used on the destination chain to release tokens held there or mint a token that represents the original. This proof is often called a VAA, short for Verifiable Action Approval.

With Wrapped Token Transfers, or WTT, the source token is locked or burned. The destination contract releases the original token when available, or mints a wrapped version. A wrapped token is a representation of an asset from another chain. Its address and accepted use can differ from the original, so check the token contract before sending funds into another app.

Which Wormhole bridge route should you choose?

Choose based on the token you need at the destination, not just the chain names. The asset’s issuer may have set up Native Token Transfers (NTT), which move its own token across chains without creating a Wormhole-wrapped version. WTT can move a broader range of supported assets, but the destination may receive a wrapped token. Availability depends on the token and route.

• Choose NTT when the token issuer supports it on both chains and you need that issuer’s native token.
• Choose WTT when the token is supported through Wormhole’s wrapped-token system and that wrapped form is accepted where you plan to use it.
• Check whether the route completes automatically or needs a second transaction on the destination chain. A manual route means you submit that transaction yourself.
• Compare the expected result with the destination app’s accepted token and network before confirming.

What should you check before sending?

Confirm the source and destination chains, token, amount and recipient address. Addresses can look different across networks, and a wallet address on one chain may not be usable on another. Make sure you can access the destination wallet and pay its transaction fee if you need to complete the transfer manually.

For example, sending a token to a chain where it arrives as a wrapped asset may work for holding, but a lending app on that chain might accept only the native token. In that case, a route that preserves the issuer’s token form is a better fit if it is available. The practical rule is simple: check what arrives and what the next app accepts before you send. A bridge moves value between chains; it does not make every version of a token interchangeable.