Portal Bridge 2026: Manual vs Relayed Redemption

Portal Bridge in 2026 gives you control over destination execution through manual redemption; a relayed route charges a fee for someone else to submit the proof. For a pending Portal Bridge transfer, check the source transaction and signed proof before paying destination gas or sending again.

What happens between the source transaction and redemption?

A confirmed source transaction starts the transfer, but destination redemption finishes it. These are the key points to check when a transfer appears stuck:

• Source transaction: Did the lock or burn succeed?
• Finality: Have Guardians waited for the source chain’s required commitment?
• VAA: Is the signed transfer message available?
• Redeemer: Will your wallet or a relayer submit it?
• Destination transaction: Was the token minted or released to the specified recipient?

On a standard Wormhole Wrapped Token Transfer, the source Token Bridge locks an original asset or burns its Wormhole-wrapped representation. It then publishes a message containing the amount, token origin, destination chain and recipient. The Wormhole Guardian Network observes that message; a 13-of-19 quorum signs a Verified Action Approval, or VAA. The transfer flow ends only when the destination contract verifies that VAA and mints or releases the token.

Finality is a separate wait from destination execution. A successful source receipt does not mean the VAA is ready, and an available VAA does not mean it has been redeemed. Wormhole Explorer can help distinguish those states using the source transaction hash; the VAA itself is identified by its emitter chain, emitter address and sequence.

Manual redemption puts the destination transaction in your hands. Relayed redemption assigns that transaction to a relayer, which pays destination gas and recovers its cost through the route’s quote. Neither route lets the redeemer change the recipient or amount already committed in the signed message.

How does Portal Bridge give you destination control?

Portal Bridge gives you destination control when the selected route offers manual redemption and you choose to submit the VAA yourself. You connect a wallet on the destination chain, keep enough native gas there, and sign the redemption after the VAA becomes available. That lets you choose when to submit and, on an EVM chain, what gas settings to accept.

Portal Bridge cross-chain transfers with relayed redemption trade that timing and fee control for one source-side action. The relayer watches for the VAA and submits the destination call; an optional native-gas drop-off may also be included in the quote. Relaying is available only where the selected token, route and chain pair support it, so check the actual route shown before signing.

The useful distinction is who submits the proof, not who receives the tokens. A manual redeemer may pay gas from a different wallet, but the VAA still fixes the receiving address. I would choose manual redemption when I already hold destination gas and want to control submission; I would choose a quoted relay when avoiding a destination wallet transaction matters more than that control.

What will each route cost and how long will it take?

Manual redemption costs source-chain gas plus destination-chain gas, and sometimes a source message fee; relayed redemption adds the quoted relay charge instead of requiring you to fund the destination transaction directly. On EVM chains, destination gas depends on gas used, the base and priority fees, and any layer-two data charge. For example, 200,000 gas at 0.1 gwei is 0.00002 ETH before a data charge; the same call at 10 gwei is 0.002 ETH.

Compare the displayed relay quote with the estimated destination cost, including any gas drop-off, rather than assuming one route is cheaper. A small transfer can fail a relayed route’s minimum when its amount cannot cover the fee and requested drop-off. Manual redemption can still be economical if you have native gas on the destination chain, but acquiring that gas solely to claim a small transfer may erase the saving.

The largest wait is often source finality, not the choice of redeemer. Wormhole’s finality reference gives approximate finalized waits of 14 seconds for Solana, 18 minutes for Arbitrum and 19 minutes for Ethereum; VAA assembly and destination inclusion add more time. Relaying can remove your signing step, but it cannot skip the route’s required source finality.

How do you finish a pending or failed redemption?

Finish a pending transfer by locating its source transaction hash, confirming what stage it reached, and redeeming the existing message if it remains unclaimed. The common mistake is sending the assets again because the source transaction succeeded but the destination balance has not changed. That creates a second transfer; it does not repair the first.

To check how to use Portal Bridge for recovery, start with the original source hash in the transfer’s recovery or resume flow. Confirm the source chain, destination chain, token and recipient before signing anything. If the source transaction failed, there is no completed transfer to redeem; if it succeeded but no VAA appears, wait for finality and Guardian signing before retrying.

When the VAA exists, check whether a destination transaction has already redeemed it. If it has, inspect the receiving address and the destination token contract: a Wormhole-wrapped token may need to be added to the wallet display. If it has not, use the route’s recovery flow and fund destination gas for a manual claim. Wormhole’s recovery instructions also describe rebuilding a stuck transfer from its source hash.

A relayed transfer can sometimes be completed manually after the relayer stalls, but use recovery that understands the original route. The relayer’s payload may include fee and gas-drop-off instructions, so treating every automatic transfer as a plain Token Bridge redemption can fail. Check the destination transaction result before retrying: an already-redeemed VAA cannot pay out twice.

Which failures need more than a retry?

A missing VAA, an underfunded destination wallet and a rejected redemption call need different fixes. For a missing VAA, verify source finality and the message identifier. For insufficient gas, fund the wallet that will submit redemption and retry the same VAA; for an on-chain rejection, read the revert reason before paying for another attempt.

Portal Bridge cannot redirect a completed source transfer to a new recipient. The recipient is part of the signed payload, so a wrong address is a delivery problem, not a redeem-button problem. A transfer with a contract payload may also require its designated recipient contract to redeem it; a generic wallet claim will not satisfy that call.

If a manual transfer has sat for more than 24 hours, a changed Guardian set can make old VAA signatures unusable on the destination chain. That does not mean the underlying transfer has expired: the signatures may need updating before redemption, as the signature replacement procedure explains. The practical rule is to identify the first unfinished stage, then act on that same transfer instead of starting another one.