Wormhole Bridge: How Your First Cross-Chain Transfer Works

Wormhole bridge moves tokens between blockchains using a message signed by at least 13 of 19 Guardians, allowing an equivalent asset to be delivered on another chain. It connects networks including Solana, Ethereum and Polygon, and its messaging system can also carry instructions between applications. Before transferring, the key question is which token you will receive: an issuer-backed native token or a wrapped version of one from another chain.

What is the Wormhole bridge?

It is the token-transfer use of Wormhole’s cross-chain protocol. A blockchain cannot directly change another blockchain’s records, so Wormhole carries verified information about an action on the sending chain to a contract on the receiving chain. That contract can then release or create the appropriate token.

A route means a particular sending chain, token and receiving chain. Once you know those three details, use Wormhole bridge routes to move tokens or messages between connected blockchains. Check the receiving asset before committing: support for both networks alone does not mean your particular token can travel between them.

How does a transfer work?

A token transfer starts when you approve a transaction on the source chain. Under Wrapped Token Transfers (WTT), also called Token Bridge in Wormhole’s contracts, the source contract locks an original token or burns a previously wrapped one. Wormhole Core publishes a message recording what happened and where the asset should go.

The Guardian Network observes that message. Once at least 13 Guardians sign it, their signatures form a Verified Action Approval, or VAA: proof that the destination contract can verify. A relayer may submit that proof for you, or a manual transfer may require you to submit it on the destination chain. Only after that final transaction does the receiving contract mint a wrapped token or release an original one.

The same messaging mechanism can carry application data instead of a token transfer. For example, a source-chain transaction can send an instruction to a destination-chain application, provided that application has a contract set up to receive and act on it. A signed message proves its origin; it does not, by itself, make every destination action possible.

Which networks and assets can you use?

Wormhole token bridge transfers can span Solana, Ethereum, Polygon and other connected networks, but available assets depend on the route and transfer method. With WTT, a token arriving away from its original chain is generally a Wormhole-wrapped representation. Check its token identity and contract address if you need to use it in another application.

Consider an eligible Ethereum-origin token sent to Solana. If you send 100 units through WTT, the Ethereum contract locks the original units and the Solana contract can mint up to 100 wrapped units, with any applicable charges affecting what reaches your wallet. Sending those wrapped units back burns them on Solana and releases the originals on Ethereum.

Some issuers instead use Native Token Transfers (NTT), which can burn and mint or lock and release tokens under the issuer’s own deployment. This can give you that issuer’s native token on the destination chain rather than a WTT-wrapped asset. The deciding check is the specific token and route, not the network names alone.

What will it cost, and how long will it take?

Costs depend on the chains and how the destination transaction is completed. Expect source-chain gas, plus either destination-chain gas for manual redemption or a relayer charge for automatic completion; compare the quoted amount you will receive. Keep some native gas token in the relevant wallet if you must approve or redeem a transaction yourself.

Timing depends heavily on source-chain finality, then on Guardian signing and destination redemption. Wormhole’s finality figures are around 14 seconds for Solana and 19 minutes for Ethereum, so an Ethereum-origin transfer can take substantially longer before its proof is ready. Network congestion and relayer availability add further time.

How do you make a first transfer?

Start with a wallet that holds the token and enough gas on the sending chain, plus an address you control on the receiving chain. Confirm the token’s route and receiving representation, enter the amount and recipient, then review the destination amount and charges before approving. For a first attempt, a small transfer checks both the address and the asset you actually receive.

Save the source transaction identifier and wait for its confirmation. If the source transaction succeeds but the destination wallet stays empty, check whether the VAA still needs manual redemption before sending the tokens again. Once the destination transaction completes, verify the token contract as well as the balance; wallets may not display a newly received wrapped token automatically.