Portal Bridge transfer time during congestion depends on three things: when the source transaction lands, when Wormhole can attest to it, and when the destination transaction completes. A higher network fee can help a pending transaction land sooner, but it cannot shorten the source chain’s required finality wait. Check which stage is slow before paying more or trying again.
Why does Portal Bridge slow down under congestion?
Congestion mainly delays transaction inclusion on the source or destination chain. In a Wormhole Token Bridge transfer, the original token is locked, or an existing Wormhole-wrapped token is burned, on the source chain. Wormhole’s Guardians then observe the transaction and produce a signed message called a VAA; submitting that VAA on the destination mints or releases the token.
A Portal Bridge transfer can therefore look idle even after its source transaction succeeds. Guardians must wait for the required source-chain finality before signing, and the destination transaction still has to land. These are separate waits: raising a gas bid may help a pending transaction, but it does nothing to an already confirmed transaction waiting for finality.
How long should you allow for each leg?
Allow seconds to minutes for an uncongested transaction to land, then add the source chain’s finality time and destination execution. Wormhole lists roughly 14 seconds for Solana finality and about 19 minutes for Ethereum finality on a standard finalized route. Those figures begin after source inclusion; they are not end-to-end delivery promises.
For a Solana-origin transfer, destination execution may be the larger variable once the VAA is ready. For an Ethereum-origin transfer using standard finality, plan for roughly 20 minutes before destination work can finish, plus any time spent waiting for the source transaction to land. A busy destination can extend either direction by minutes or longer.
Direction matters more than the distance between chains. Sending from Solana to Ethereum and sending the same asset back can have very different timelines because the Guardians wait on a different source chain each time. Check the route’s stated completion estimate before treating a fast prior transfer as your benchmark.
Which transfer method saves time or money?
The usual Wormhole Token Bridge choice is manual redemption or automatic relaying, where available for the route. Manual redemption means signing a source transaction, waiting for the VAA, then paying for a destination transaction yourself. An automatic route has a relayer submit that second transaction for a quoted fee, reducing your steps but adding relayer cost; neither method removes the source finality wait.
Compare the full cost, not only the bridge amount. On Ethereum, gas used times gas price gives the transaction fee: for example, a 150,000-gas source transaction costs 0.003 ETH at 20 gwei and 0.012 ETH at 80 gwei. An initial token approval can add another transaction, while manual redemption adds destination gas. Solana’s base fee is 5,000 lamports per signature, with priority fees and any token-account creation cost on top.
First decide which asset must arrive: a Wormhole-wrapped token is not necessarily interchangeable with native USDC at the destination. When a supported token transfer fits that need, use Wormhole Portal Bridge to move it between Solana, Ethereum, and other supported chains through Wormhole. Start the Portal Bridge transfer after comparing the route’s finality wait, quoted relay cost if any, and the gas needed to finish.
What should you do when a transfer seems stuck?
Locate the last completed stage using the source transaction hash and, once available, the destination transaction hash. If the source transaction is still pending, its gas bid may be too low for current demand; replacing that pending transaction through your wallet can help. Do not start a second bridge transfer simply because the first is slow, since both could eventually execute.
If the source transaction is confirmed but no VAA is available, wait for the required finality before changing anything. If the VAA exists but the destination has not completed, check whether your chosen route uses a relayer or requires you to redeem it and pay destination gas. A successful source transaction alone does not put spendable tokens in the destination wallet.
What else should you check?
The remaining questions concern the steps that are easy to mistake for a delay. Their answers depend on the route and on which chain is handling the next transaction.
Can paying more gas shorten the finality wait?
No. A higher gas bid can improve the chance that a pending Ethereum transaction enters a block, but it cannot make an included block reach the finality required by Wormhole sooner. On Solana, a priority fee can similarly help transaction scheduling during contention. Once the source transaction has landed, check for the VAA rather than increasing a fee on that completed transaction.
Can I disconnect my wallet after sending?
That depends on who completes the destination transaction. An automatic route uses a relayer after your source transaction, so your wallet need not stay connected for that step. With manual redemption, you must return to submit the VAA and have the destination chain’s gas token available. Save the source transaction hash so you can find the transfer again.
Why did the destination receive a wrapped token?
Wormhole Token Bridge represents an asset from its original chain with a wrapped token on another chain. Returning it toward its origin burns the wrapped version and releases the original. If your next transaction specifically requires native USDC, check the received asset before sending: a native USDC transfer route, where available, may produce a different result from a wrapped-token route.
When should I choose a different route?
Choose based on the asset you need at the destination, the time allowed, and the total quoted cost. Automatic relaying can save a manual claim when it is offered; manual redemption may suit you if you already hold destination gas and want to handle that step yourself. Portal Bridge transfer time is only the deciding factor when both routes deliver a usable asset at a cost you accept.