2 Portal Bridge Transfer Modes and When Each Fits

If you need to move a token with Portal Bridge now, the two transfer modes to understand are automatic redemption by a relayer and manual redemption through a destination-chain transaction. Portal Bridge transfers supported tokens between Solana, Ethereum and other supported chains through Wormhole, so you can move an asset to the chain your app uses.

Three checks settle most transfers:

• Match the destination token’s contract or mint to the one your app accepts; a matching ticker is insufficient.
• Check who will submit the destination transaction and pay for it.
• Compare the amount received after fees, not only the amount sent.

What Are the Two Portal Bridge Transfer Modes?

The two modes differ in who submits the signed transfer message on the destination chain. In either mode, the source transaction locks an original token or burns an existing Wormhole-wrapped token. Wormhole Guardians then sign a Verified Action Approval, or VAA, which the destination contract verifies before minting or releasing the asset.

• Automatic redemption — best when you want the destination transaction handled for you. A relayer submits the VAA and recovers its charge through the transfer’s quoted fee. It fits when that relayer supports the chain pair and token; it does not fit when the route is unavailable or its charge outweighs the gas and effort of redeeming yourself.
• Manual redemption — best when you can fund and submit the destination transaction. After the VAA is available, you or another party submits it and pays destination-chain gas. It fits routes without relayer support and transfers where you want to control completion; it does not fit if you have no practical way to fund that transaction.

“Automatic” describes redemption, not an instant transfer. The source chain must reach the finality Wormhole requires, Guardians must sign the message, and the destination transaction must succeed. I would use an available automatic route for a routine app deposit when its received amount is acceptable, then use manual redemption when relaying is unavailable or the quoted difference justifies the extra transaction.

What Token Will Arrive on the Destination Chain?

A wrapped token transfer usually delivers a Wormhole-wrapped representation when the destination is away from the token’s origin chain. Returning that representation to its origin burns it and releases the original token from custody. This distinction matters more than the displayed symbol: an app can reject a valid bridged token because it expects a different contract or mint.

For example, moving Wrapped Ether from Ethereum to Solana through this mechanism locks the Ethereum token and mints its Wormhole-wrapped representation on Solana. Sending that representation back burns it on Solana and releases the escrowed Wrapped Ether on Ethereum. A Portal Bridge transfer can therefore be final on-chain while leaving you with an asset the destination app does not accept.

Check the destination app’s accepted token identifier against the asset the proposed route delivers before committing. A first transfer of a token to a destination chain may also require a metadata attestation before its wrapped version can be created; existence on the source chain alone does not establish that the wrapped asset is ready. If your app needs a different representation, bridging first may leave you needing a separate swap.

There is a small precision edge case. Wormhole’s wrapped token transfer message normalizes amounts to eight decimals: for an 18-decimal token, an illustrative send amount of 1.000000009 transfers 1.00000000, while the extra 0.000000009 remains on the source side. Usually negligible, this matters if a contract or deposit rule requires an exact minimum amount.

What Will Each Mode Cost and How Long Will It Take?

Both modes require source-chain gas; automatic redemption adds a relayer charge, while manual redemption requires destination-chain gas. A token approval can add another source transaction, and creating a destination token account can add a chain-specific cost. Portal Bridge transfer fees therefore depend on the chosen token and route, current network conditions, and who performs redemption; use the amount received and the required gas transactions for the comparison.

Here is a calculation you can replace with your own quote. Say you send 100 tokens worth $2 each, source gas is $1 in either mode, automatic redemption charges 0.30 token, and manual destination gas would cost $0.40. Automatic costs $1 + (0.30 × $2) = $1.60; manual costs $1 + $0.40 = $1.40. The $0.20 difference only helps if you can fund and complete the manual transaction.

Completion time is source finality plus Guardian attestation plus destination redemption, typically measured in minutes but subject to chain congestion and relayer availability. A confirmed source transaction is therefore not proof that the recipient has the token. For manual transfers, aim to redeem within 24 hours: a later Guardian-set change can make the original VAA signatures stale and require refreshed signatures.

How Do You Check That the Transfer Is Complete?

Confirm completion on the destination chain against the exact token contract or mint and recipient address. Before sending, verify the source token, destination chain, amount, recipient and resulting token representation; keep enough native currency for every transaction you must submit. For manual redemption, include destination gas in that check before you commit funds on the source chain.

After initiation, retain the source transaction hash and follow its Wormhole message through attestation to destination redemption. If the source transaction succeeded but no token has arrived, first determine whether the VAA exists and whether redemption succeeded. Do not start a second source transfer to fix an unredeemed first one: submit the existing VAA if manual completion is needed, or investigate the failed destination transaction.

Once redemption is confirmed, inspect the recipient’s balance for the specific destination asset, not merely a familiar ticker. Before acting, ask yourself: will this route deliver the exact token my app accepts, and who will pay to redeem it?