A Wormhole transfer happens in two parts. The tokens leave the source chain first. Then someone redeems the signed transfer on the destination chain, which releases the tokens there. If the second part never happened, the tokens have left one chain and not arrived on the other. This is how most transfers left on Portal ended up, after Portal stopped supporting Algorand.
Most of these can be finished here, from your own wallets.
1. Find the transfer
- On the Activity page, enter the sending or receiving address, or connect the wallets. It lists Token Bridge transfers to and from Algorand, checks on chain whether each one was redeemed, and has a Continue link for the ones that were not.
- On the Redeem page, paste the source transaction hash, the Wormholescan ID (chain/emitter/sequence) or the signed VAA.
2. See why it stopped
It is not signed yet
The guardians sign a transfer from Ethereum, Celo, Arbitrum, Optimism and Base only once it is final on Ethereum, which takes 15 to 30 minutes. Other chains take seconds. A transfer can also be held for up to 24 hours by Wormhole's Governor: a large one always is, and a smaller one is when it would take the value sent from the source chain in the past 24 hours above a daily limit. Wait, then try again: the transfer is signed when the wait ends.
It is signed but not redeemed
Redeem it on the Redeem page with a wallet on the destination chain. The tokens always go to the recipient in the transfer, so on Algorand and the EVM chains any wallet can pay for the redeem. Three cases need the recipient's own wallet:
- On Algorand, a recipient that has not opted in to the asset. Redeem from the recipient's account, and the opt-in goes into the redeem. It sets aside 0.1 ALGO of minimum balance.
- On NEAR, a recipient that has not registered with the bridge. The recipient's redeem registers it, for 0.002 NEAR.
- On Solana, every redeem. This site redeems only from the wallet that owns the token account the transfer pays.
The wallet also needs the destination chain's coin for fees: ALGO on Algorand, ETH on Ethereum, SOL on Solana, and so on.
It was signed before late June 2026
Wormhole replaced its guardian set in late June 2026, and the bridge contracts stopped accepting signatures from the old set a day later. Algorand and the EVM chains enforce this from 26 or 27 June, and Solana from 11 July. A transfer signed before then cannot be redeemed with its original signatures, with one exception. The Redeem page says when a transfer's signatures have expired, except for transfers to NEAR.
On Solana, a redeem first verifies the signatures and posts the transfer to Solana, then completes it from the posted copy. If the posting happened before the old set expired, the transfer can still be completed: the Redeem page finds the posted copy and goes straight to the last step.
Otherwise the current guardians have to sign it again first. 16 of the 19 current guardians were also in the previous set, so for a transfer signed by that set, Wormholescan's records may hold enough current signatures to rebuild a valid VAA. Older sets share fewer: in the older transfers we checked, at most 11 current guardians had signed, short of the 13 a VAA needs. Those need the guardians to observe the source transaction again. This site cannot do either yet. Ask Wormhole whether the guardians can sign the transfer again, and include the source transaction and the Wormholescan ID.
It carries a payload for another app
Some transfers carry extra data for an app on the destination chain, such as a swap. This site redeems only plain token transfers. Use the app that sent the transfer.
It was already redeemed
The Activity page shows the redeem, and the tokens are in the recipient's account. On Algorand they are a Wormhole-wrapped asset, so the wallet may list them under the token's own name, such as WETH or USDC, with a different asset ID from the one you expected.
What cannot be undone
A transfer cannot be cancelled or sent back once it has left the source chain. It can only be redeemed, to the recipient written in it. A transfer to a wrong address on the right chain pays that address.
More answers are in the FAQ.