If you are moving a token to a chain where it has no native version, use a wrapped asset after checking its origin and destination contract. A wrapped asset is a token made on the destination chain to represent a token held or burned elsewhere.
A wrapped token gives another chain a usable version
Blockchains keep separate records, so a token on one chain cannot simply appear on another. A wrapped token is a separate asset contract on the destination chain, with its own address and balance records.
For example, imagine you hold 10 units of a token on Ethereum and want to use them on Solana. If that token has no native Solana version, a bridge can lock the 10 units on Ethereum and create 10 wrapped units on Solana. The wrapped units represent the original; they are not the original Ethereum tokens moved across.
This is why a token’s name and logo are not enough to identify it. On the destination chain, check the token contract address and the stated origin chain. Two assets can share a ticker while having different backing or issuers.
The bridge locks, proves, and then creates the representation
In a typical Wormhole bridge transfer, you approve and send tokens to the source chain’s bridge contract. That contract locks the original tokens and publishes a message describing the amount, destination, and recipient.
The Guardian Network observes that message and signs a proof called a VAA, short for Verified Action Approval. A supermajority of Guardians must sign it; the destination contract checks those signatures before minting wrapped tokens to the recipient’s wallet.
That sequence explains why the transfer has two chain transactions in a manual flow: one to start it and another to claim the tokens. With automatic delivery, a relayer submits the destination transaction for you. The convenience and any delivery fee depend on the route shown in the transfer screen; check the wormhole bridge fees before confirming.
The representation changes when you send it back
When wrapped tokens return to their origin chain, the destination bridge usually burns the wrapped units and releases the same amount from escrow. Burning means removing those units from circulation, so the claim on the locked original is not duplicated.
If you send the wrapped version from one non-origin chain to another, the first chain burns its wrapped units and the next chain mints a new representation. The original remains locked at its origin. This keeps the total claim tied to the original supply, though each step still needs a valid message and destination transaction.
One useful edge case: the destination may already have an official native version of the asset. Some transfer routes can release that native token instead of minting a wrapped one. The transfer screen’s asset details and origin label tell you which version you will receive.
Check the asset and the costs before confirming
Before sending, confirm that the route supports both chains and that the receiving wallet address belongs to the destination chain. Check the exact token you will receive, including its origin and contract address, rather than relying on its symbol.
Keep enough source-chain currency to pay the transaction fee, called gas. A manual transfer may also require destination-chain gas to claim the tokens. Automatic delivery can include a relayer charge, and some routes let you request a small amount of destination gas; the quote can change with chain conditions and the requested service.
For instance, if you are used to buying a token on an exchange and withdrawing it to a network, wallet-to-wallet bridging adds a choice: you must accept a specific destination-chain representation. If the transfer is still pending, check its status before retrying or sending again. Once it completes, you can swap or use the wrapped asset on that chain, but it may not be accepted everywhere the original is.
Wormhole bridge is one route that uses signed cross-chain messages to support these transfers, but the key decision is the asset you receive. Before acting, ask yourself: am I comfortable holding this exact wrapped token on this exact chain?
Top comments (0)