Use Wormhole bridge when both blockchains support a transfer for your exact token, and you can use the token that arrives. Check that token first: a wrapped version can differ from one issued directly on the destination chain. Then compare the amount you will receive, the fees, and how the transfer finishes.
Wormhole Sends Proof Before Tokens Arrive
Wormhole moves tokens between blockchains by recording an action on one chain and proving it to another. The Wormhole bridge also carries messages: instructions that an application can use on a different chain. A token transfer uses those messages to tell the receiving chain what to release or create.
For a common route called Wrapped Token Transfers, the source chain locks the original tokens. If you send 100 tokens issued on Solana to Polygon, the destination can create 100 Wormhole-wrapped tokens. “Wrapped” means they represent the locked originals. Sending them back burns the wrapped tokens and releases the originals on Solana.
A Wormhole token bridge transfer therefore depends on both the chain pair and the exact asset. When you are ready to move that asset, use wormholebridge.org to carry out the cross-chain token transfer through Wormhole. Check what token will arrive before you commit, since a familiar name or ticker does not prove two tokens have the same issuer.
After the source transaction, Wormhole’s Guardians observe its message. At least 13 of 19 Guardians sign a proof called a VAA. The destination chain checks that proof before completing the transfer. The tokens do not travel through a wallet between chains; each chain records its part of the transfer.
The Asset and Destination Decide the Route
Start by checking the token on the source chain and the form you need at the destination. Wormhole bridge supported chains include Solana, Ethereum, and Polygon, but chain support alone does not guarantee a route for every token. A token may also need its details registered on the destination chain before its first wrapped transfer.
Consider two transfers of 100 tokens. If the token was issued on Solana and uses Wrapped Token Transfers to reach Polygon, you receive its Wormhole-wrapped form. If its issuer has set up Native Token Transfers on both chains, you can instead receive the issuer’s token on Polygon. That difference matters if you plan to deposit it into an app that accepts only one form.
Native Token Transfers, often shortened to NTT, let a token issuer manage its supply across chains. Depending on the token’s setup, a transfer burns tokens on one chain and creates them on another, or locks and releases them. NTT is available only for tokens whose issuers have set it up; it is not an automatic choice for every asset.
Before choosing a transfer, check four concrete details:
- The source chain, destination chain, and exact token address.
- The token address and name of the asset you will receive.
- Whether delivery is automatic or needs a destination transaction from you.
- Whether the receiving wallet or app accepts that form of the token.
A bridge also may carry an instruction alongside tokens, such as one meant for an application on the destination chain. That requires an application built to read and act on the message. Sending tokens to an ordinary wallet address does not by itself trigger a swap, deposit, or other action.
A Transfer Needs a Source and a Destination Action
A transfer finishes only after the receiving chain processes the signed proof. For a Wormhole token bridge transfer, you first authorize the source transaction with a wallet that holds the token. On some chains, spending a token also requires a separate approval transaction. Read the wallet request and confirm the chain, token, amount, and recipient address.
Next, the source transaction locks or burns the tokens and publishes the message. Guardians sign its proof after the required confirmation level. A relayer—a service that submits the proof on the destination chain—can complete an automatic transfer. With a manual transfer, you must submit the proof and pay for that destination transaction yourself.
Keep the source transaction record until the destination action succeeds. A confirmed source transaction means the transfer has started; it does not mean the receiving wallet already holds the token. If delivery pauses, check whether the proof is ready and whether the destination transaction still needs to be completed.
Wrapped Token Transfers have a small precision edge case. Their cross-chain transfer amount uses at most eight digits after the decimal point. If a token uses more, a tiny remainder may stay in the sending wallet. For example, an 18-decimal token amount can be rounded down to eight decimal places for the transfer.
Fees and Completion Time Depend on the Route
Your cost depends on network gas, the delivery method, and any fee shown for completing the transfer. Gas is the payment for a blockchain transaction. Expect source-chain gas, plus destination-chain gas if you complete the transfer manually. Automatic delivery can include a relayer fee instead, so compare the final amount received.
The Wormhole bridge has no single arrival time for every chain pair. The wait depends on source-chain confirmation, Guardian signing, and the destination transaction. A route that waits for Ethereum finality can take around 15–20 minutes before its proof is ready; other routes may be faster. Check the transfer’s status before trying to send the same amount again.
Make your choice from the receiving end. Confirm the destination accepts the token form, compare the quoted amount after costs, and decide who will complete delivery. Then fund the sending wallet for gas, verify the recipient address on the destination chain, and start the transfer.
Top comments (0)