Wormhole bridge moves tokens and messages between blockchains, with different routes for different jobs. For an occasional transfer, the key question is what asset you will receive. Two tokens can share a name while having different contract addresses, the identifiers that tell them apart on a chain.
What Moves Between Chains?
The Wormhole bridge carries proof of an action on one chain so it can be completed on another. Its token routes use that proof to release or create tokens. Its messaging route carries data for an app to act on, without moving a spendable token by itself.
A transfer starts with a transaction on the source chain. Wormhole’s Guardians, the nodes that watch connected chains, sign a record called a Verified Action Approval, or VAA. That signed record is submitted on the destination chain, where a contract checks it before completing the action. Tokens do not simply travel out of one wallet and into another.
Wormhole connects Solana, Ethereum, Base, and other blockchains. A connected network does not mean every token has every route available. Check the specific asset and destination before sending.
Which Wormhole Route Fits the Job?
There are two main token transfer types, plus a message route for apps. The difference that matters most is whether the receiving chain gets a wrapped token or the token issuer’s own version.
- Wrapped Token Transfers (WTT), also called Token Bridge: The bridge locks an original token and creates a Wormhole-wrapped version on the destination chain. On a return trip, it burns that wrapped token and releases the original. This suits a token transfer when the receiving app accepts the wrapped version. It does not fit when that app requires a different token contract, even if the symbol looks the same.
- Native Token Transfers (NTT): The token issuer sets up a route that uses its own token on each chain. Depending on that setup, a transfer burns tokens and mints them elsewhere, or locks tokens and releases them later. This fits when the receiving app needs the issuer’s native version. It only works for tokens and chains whose issuers have enabled it.
- Wormhole Core messaging: An app sends data, such as an instruction to update a position on another chain. This fits developers building actions across chains. It does not give a wallet holder a token to spend on arrival. A token transfer may use Core messages underneath, but Core messaging alone is not a token route.
These are route types, not three versions of the same asset. Before choosing WTT or NTT, find the token contract the receiving app accepts. That check decides more than the token’s displayed name.
How Do You Make a Token Transfer?
Start with the chain holding your tokens, the receiving chain, and the exact asset you need there. Say you have 100 tokens on Solana and want to use them in an Ethereum app. If that app accepts only the issuer’s Ethereum token, confirm an NTT route exists; a Wormhole-wrapped version may not work there.
A Wormhole bridge between Solana and Ethereum also needs a recipient address on the correct chain. For that token move, use the Wormhole bridge to transfer between the connected blockchains; a custom message that triggers an app action calls for a developer integration. Check the receiving asset and address before approving the source transaction.
To bridge tokens with Wormhole, you submit the source transaction and wait for its signed proof. The destination transaction then mints or releases the receiving token. Delivery may happen automatically through a relayer, a service that submits the proof, or you may need to claim it yourself. Save the source transaction ID until the destination transaction completes.
What Should You Allow for Time and Cost?
Allow for transactions on both chains and time for the source transaction to be confirmed. Completion often takes minutes, but it can take tens of minutes when a chain waits longer for finality, its point of reliable confirmation. A busy network or a delayed destination transaction can add time.
You pay network gas for transactions you submit, usually in that chain’s native coin. Automatic delivery can add a relayer fee; a manual claim may require you to hold gas on the destination chain. Check the amount you will receive before sending. A very small transfer may leave little after delivery costs.
What Do Readers Ask Next?
The remaining questions concern the signed proof, the wait, and the limits on a particular route.
How does the transfer finish if the chains cannot talk directly?
The source transaction creates a record that Guardians sign. A relayer or the user brings that signed proof to the destination chain. Its contract verifies the proof and completes the token action once. This is why a confirmed source transaction can appear before the receiving tokens do.
How long will I wait, and what will I pay?
Expect minutes rather than an instant wallet-to-wallet payment; some routes take tens of minutes. The source chain’s confirmation time and the destination transaction set much of the wait. Costs depend on both chains’ gas and any automatic delivery fee, so use the current quote for your amount and route.
What limits which option I can use?
A Wormhole bridge route depends on the chain, token, and receiving asset. NTT requires the issuer to enable the token on both sides and may have transfer rate limits. WTT can produce a wrapped token that an app will not accept. Check the destination token’s contract first, then use the available route that delivers it.
The right choice is the route that delivers the token your destination actually accepts.
Top comments (0)