Portal Bridge moves tokens across chains through Wormhole

Portal Bridge moves tokens between blockchains by sending a transfer message from a source chain to a destination chain, where the recipient receives tokens or a wrapped version. Wormhole’s documentation describes this as a process involving a source-chain transaction, a signed message and completion on the destination chain.

When an asset needs to move between chains, use portal bridge, a Wormhole-based token bridge for transfers between Solana, Ethereum and other supported chains. The transfer starts with the token and amount on the source chain and identifies where the value should arrive; the source transaction also needs that chain’s gas token to pay its network fee.

How does a Portal Bridge transfer work?

Wormhole says its wrapped-token flow begins when the source contract locks an original token or burns a token that is already wrapped. The contract publishes a message about the transfer, and Wormhole Guardians observe and sign it as a Verifiable Action Approval, or VAA.

The VAA carries the transfer instruction to the destination chain. A relayer can submit it automatically when that route supports automatic completion; in a manual transfer, the user submits the VAA to the destination contract. The destination contract verifies the message before releasing native tokens or minting a wrapped representation.

What do you receive on the destination chain?

The destination asset depends on the token and route. Wormhole’s docs say a transfer of an original token to a different chain can mint a wrapped representation there; the original remains locked on the source chain until a return transfer burns the wrapped tokens and releases the original.

That distinction matters: a token with the same ticker can have a different contract and chain identity. Check the asset’s chain and contract before using it, especially before sending it to an exchange or a wallet that expects a particular version.

• Source transaction: locks an original token or burns a wrapped one, according to Wormhole’s transfer flow.
• Signed message: records the cross-chain instruction for destination verification.
• Destination completion: releases native tokens or mints a wrapped representation to the recipient.
• Return transfer: burns the wrapped version and releases the original when the transfer path supports that pairing.

Does a bridge transfer finish in one step?

No. Wormhole distinguishes automatic transfers, completed by a relayer, from manual transfers that require the user to submit the VAA on the destination chain. A submitted source transaction therefore does not always mean the destination wallet already holds the asset.

For most users, an automatic route is simpler because it removes the separate redemption step when available. The practical check is the destination wallet: confirm the expected token appears on the intended chain before treating the transfer as complete.