Claim a Wormhole Transfer When the Destination Wallet Has No Gas

A Wormhole transfer waiting for destination gas usually needs a separate transaction on the destination chain before the tokens reach the recipient. The source transaction locks or burns the asset and publishes a message; after Guardians sign that message as a Verified Action Approval (VAA), a destination contract must verify it and release or mint the tokens. A VAA can be ready while the destination step is still undone.

First check the transfer’s status in the app used to start it, or in Wormholescan using the source transaction hash. Confirm that the source transaction succeeded and that the VAA is available. Then connect the wallet that can submit the destination transaction, switch it to the destination network and make sure it holds that network’s native gas token. A fuller guide to the Wormhole bridge claim process covers more of the recovery path; the key point here is that an available VAA still needs to be redeemed.

Why is a Wormhole transfer waiting for destination gas?

A manual transfer leaves redemption to the recipient or another authorized wallet. The wallet pays the destination network’s transaction fee to submit the VAA to the bridge contract. That fee is separate from the bridged asset and from any fee paid on the source chain. If the destination wallet has no native gas token, the transaction cannot be submitted, even when the source transfer is final and the VAA is ready.

Automatic transfers work differently. A relayer can submit the destination transaction and, where the route supports it, deliver a requested amount of native gas to the recipient. If the relayer has not completed a transfer, first check whether the route was automatic and whether the app offers a recovery or claim action. Do not assume that adding gas alone will restart a relayer. Manual redemption and automatic delivery have different transaction paths.

The VAA is proof of the source message, not a payment or a destination transaction. Once the destination contract verifies it, a wrapped asset is minted or an original asset is released. Until that transaction succeeds, the transfer can remain unclaimed. If the destination transaction already succeeded, the tokens may simply be hidden in the wallet or shown under a different token listing.

How do you claim the transfer?

Use the original transfer app’s claim or redeem option first. It can identify the route and prepare the correct destination transaction. Keep the source transaction hash available, and follow the app’s prompts to connect a wallet on the destination chain. The wallet used to pay gas must be able to submit the redemption; it does not necessarily have to be the original source wallet, though the route may impose its own recipient or caller restrictions.

• Verify the source transaction succeeded, rather than relying on a wallet notification or an approval transaction.
• Check that the VAA is available for that source transaction and that the destination has not already recorded redemption.
• Fund the destination wallet with a small amount of that chain’s native gas token, then retry the claim and review the destination address and fee before signing.
• After submission, use the destination transaction status to confirm redemption; a pending prompt or a submitted transaction alone does not prove the tokens arrived.

If the original app cannot find the transfer, use its documented recovery flow with the source transaction hash. Wormhole’s SDK guide describes manual recovery for supported wrapped-token transfers. The recovery method depends on the route and destination chain; avoid submitting a VAA to a contract or interface unless you have confirmed it matches the transfer. A wrong destination address, unsupported token, incomplete source finality or a route that reserves redemption for a specific caller can prevent completion.

What if the claim still fails?

Separate a missing VAA from a failed redemption. If Guardians have not published the VAA, funding gas will not make the destination claim available; check the source transaction and wait for the message to be attested. If the VAA is ready but the destination transaction fails, inspect its error and confirm the connected network, recipient and gas balance. A reverted transaction may consume gas without redeeming the transfer.

Some routes restrict which application or contract can finalize a message. Wormhole’s documentation notes this for certain CCTP transfers: when the source message names a nonzero destination_caller, only that caller can redeem it, so Portal cannot complete it on the user’s behalf. Return to the app that initiated such a transfer and use its claim flow. For a standard manual wrapped-token transfer, the practical fix is usually to submit the available VAA on the destination chain with enough native gas and the correct wallet.