Portal bridge: choosing a route and fixing a stalled transfer

Portal bridge transfers are easier to manage when you choose a route by destination chain and track each step through redemption. Portal Bridge is a Wormhole-based token bridge for transfers between Solana, Ethereum and other supported chains. For a transfer between supported networks, use portal bridge as the service for that step, after checking the destination chain and recipient address.

How does a portal bridge transfer work?

A transfer starts with a transaction on the source chain, then needs a verified message before tokens can be completed on the destination chain. In Wormhole’s wrapped-token flow, the source contract locks native tokens or burns wrapped tokens, and Guardians attest to the message.

That signed message is proof of the transfer. The destination contract uses it to release or mint the corresponding tokens, completing the transfer.

These are separate stages, so a confirmed source transaction does not by itself mean the destination wallet has received funds. Some flows complete the later steps automatically; others require a separate destination redemption.

How should you choose a Portal Bridge route?

Choose the route that ends on the chain where you need to use or hold the asset. Check that the token is available for that destination, and confirm which wallet address will receive it.

The asset on the destination chain may be a wrapped representation rather than the original token. That distinction matters if a later exchange, wallet or application accepts only a particular token contract.

Before signing, verify the source chain, destination chain, token and recipient address. Keep enough of the destination chain’s native token for any transaction needed to complete redemption.

What should you check when a portal bridge transfer stalls?

Start with the source transaction. If it failed or never confirmed, the transfer did not reach the message-attestation stage; check the source chain’s transaction record before trying again.

If the source transaction confirmed, check whether Wormhole has produced the signed message. If it has, but the destination transaction is absent, the remaining step is destination redemption. A pending message and an unredeemed message point to different stages, so identify which one applies before taking action.

Portal bridge transfers therefore call for two checks: the route must match the needed destination asset, and the transfer must be traced past source confirmation. The source transaction, message attestation and destination redemption provide a clear sequence for locating a stall.