A direct bridge moves your tokens through a cross-chain message. A liquidity-assisted route pays from funds already available on the destination chain. The first can be easier to trace and may deliver a wrapped token; the second can be faster or deliver a familiar local token, but its quote may include a fee or price impact.

  • Check the token you will receive, not only its ticker.
  • Compare the amount delivered, total fees, and estimated time.
  • Keep enough source-chain gas to start, and destination-chain gas to use the funds.

What is the difference between the two routes?

A direct route sends proof of your deposit across chains, then releases or creates tokens on the destination. With Wrapped Token Transfers (WTT), the bridge locks the original tokens or burns wrapped ones, then mints equivalent wrapped tokens or unlocks originals on the other chain. A signed message, called an attestation, is the proof that allows the destination step.

A liquidity-assisted route uses tokens already held on the destination chain. A solver, a service that fulfils transfers, can pay you there first and settle the source-side funds later. Think of the direct route as a parcel sent through the post; liquidity is a local shop handing you the item while the supplier settles the invoice afterward.

For an occasional user, Portal Bridge can show eligible routes for a selected transfer; compare those options as a direct message-based trip versus a faster, liquidity-backed handoff. The route depends on the token and chain pair, so you may see only one option.

What do speed and cost depend on?

A direct transfer waits for the source chain to confirm the deposit and for the destination step to become available. With a manual route, you may need to submit a second transaction on the destination chain. An automatic relayer can submit it for you, usually for a fee. Some liquidity-backed routes can deliver in seconds, while a direct route can take longer, especially when the source chain has slower finality.

There is no single bridge fee to expect. Your source transaction uses gas, the network fee paid to process it. A relayer or solver may charge a service fee; a swap can also have price impact, meaning the quoted rate worsens as the trade uses available liquidity. Check the final amount after fees and the quote’s expiry time before you confirm.

Speed is not the only trade-off. A direct WTT route may leave you with a wrapped version of the token, which can have different uses and liquidity from the destination chain’s native version. A liquidity-assisted route may deliver the destination’s familiar token, but depends on available funds and the route’s quoted exchange rate.

How should you choose and finish safely?

Choose the route by the asset you need at the end. If you need a specific native token for an app or exchange, confirm the destination token’s name and contract details. If either route gives you the same useful asset, I would pick the one with a clear quote, acceptable delivery time, and lower total cost.

Before sending, check the source and destination networks, token, amount, and recipient address. Confirm that your destination wallet can receive the asset, and leave some destination gas for a later transaction. A wrong address or unsupported token can be difficult or impossible to recover.

After confirming, save the source transaction ID and use the transfer status or Wormhole Explorer to follow the message. If a direct transfer is still waiting, check whether it needs a destination claim; if you chose automatic delivery, allow time for the relayer to finish. Don’t start a duplicate transfer just because the balance has not appeared yet.