Wormhole bridge transfers: how to move tokens across chains

A wormhole bridge moves tokens from one blockchain to another by verifying a message about the transfer and completing the token movement on the destination chain. The tokens do not travel directly between networks: the source chain records the transfer, and a bridge mechanism releases or creates the corresponding asset elsewhere.

Before sending, check that the source and destination chains, token and receiving address match your intention. If you need to move assets between supported networks, use the wormhole bridge, a Wormhole cross-chain protocol service for moving tokens and messages between Solana, Ethereum and many other blockchains.

How does a wormhole bridge transfer work?

A transfer starts when a user sends tokens to a bridge contract on the source chain. For a wrapped-token route, that contract locks the original tokens and emits a message describing the transfer. Wormhole Guardians observe and sign the message, producing a verifiable action approval, or VAA, that can be submitted on the destination chain.

Once the destination contract verifies the signed message, it completes the transfer. Depending on the route and token setup, it may mint a wrapped version of the asset or release tokens held in escrow. Some projects instead use native-token transfer systems that burn tokens on one chain and mint them on another; the asset representation depends on the route.

What should you check before moving tokens?

Confirm the destination network and address before approving a transaction. Addresses can use different formats across blockchains, and a valid address on one chain may not be usable on another. Review the asset name and contract details shown for the destination token, since a wrapped token can have a different contract from the original.

• Choose the source chain that currently holds the asset.
• Choose a destination chain supported for that transfer.
• Check the receiving address against the destination network.
• Review the token amount and transaction details before signing.

A bridge transfer also involves separate chain transactions or steps: one records the send, while another completes delivery. In some flows, the destination step must be completed after the signed message is available. Keep the transaction record and check the transfer status through the service used to start it.

Is a bridged token the same as the original?

Not always. A wrapped asset represents tokens locked on another chain, while a native-token route can preserve the project’s token through its own mint-and-burn arrangement. The distinction matters when choosing where to trade, hold or use the received asset.

For most users, the practical choice is to use a route that supports the token and both chains, then verify the destination representation before signing. The transfer is complete only when the destination step succeeds; the exact route and final token form depend on the chains and token involved.