A pending bridge transfer usually means the source transaction has completed but the destination step has not; it does not automatically mean your tokens are lost. The key condition is the source transaction’s status: until it is confirmed, wait, and once it is confirmed, check whether the transfer still needs an attestation or a destination claim.
Find out which step is still pending
A cross-chain transfer has at least two parts: a transaction on the source chain and delivery on the destination chain. The source contract locks or burns tokens and emits a message; Guardians verify that message and sign a VAA, or Verified Action Approval, which acts as proof for the destination contract. The destination contract then releases or mints tokens, sometimes after you submit the VAA yourself.
Start with the transaction hash from the app you used, and open it in the source chain’s block explorer. If it is still pending, failed, or dropped, the bridge has no confirmed transfer to finish; check the wallet or network before trying again. If it succeeded, note the source and destination networks, token, amount, and recipient address, then check the bridge app’s transfer status.
Wormhole bridge supported chains help you confirm that both networks in your transfer have a supported route before you wait for delivery. For a Wormhole transfer, a successful source transaction may still be waiting for Guardian signatures or for redemption on the destination. A transfer page or explorer may show these as separate stages, so look for the last completed step rather than relying on a single “pending” label.
Wait for the attestation before trying to claim
If the source transaction succeeded but there is no attestation yet, wait for the message to be observed and signed. The VAA identifies the source message and carries the Guardian signatures; it is not the destination transaction itself. Network congestion, the source chain’s confirmation requirements, and the route used can all affect how long this stage takes.
For example, say you send tokens from Base to Sui through a route shown in the bridge app. After the Base transaction succeeds, check whether the app reports the VAA as available. If it does not, keep the transaction hash and wait; sending a second transfer will create a separate transfer and could leave you with two transfers to track.
Once the VAA is available, see whether the app completes the destination step automatically. Some routes use a relayer to submit it for you; others require you to press a “Redeem,” “Claim,” or similar button and approve a transaction with your destination wallet. Follow the route’s own prompt, since the app that initiated the transfer may be the only one allowed to complete certain message types.
Complete a manual claim with the right wallet and gas
A manual claim needs the destination wallet that can receive the tokens, the transfer’s VAA, and enough of the destination chain’s native token to pay transaction gas. Gas is the network fee for submitting the claim; it is separate from any bridge or relayer fee shown when you started the transfer. If the wallet has no native gas token, the claim can remain unfinished even though the VAA is ready.
Reconnect the wallet on the destination network, open the original bridge app’s transfer record, and use its claim action if available. Check that the displayed recipient and amount match your intended transfer before signing. If you used a different recipient address at send time, the tokens go to that address, not necessarily the wallet currently connected.
After signing, wait for the destination transaction to confirm, then check its hash in the destination explorer and verify the token balance there. The asset may have a different token address or representation on the destination chain, so search by the token contract or inspect the app’s transfer details instead of assuming the familiar ticker proves it is the same asset.
Know when to stop and ask the app for help
If the source transaction failed, do not attempt a destination claim. If the source succeeded and the VAA is available but the claim fails, read the wallet’s error and check the destination network, recipient, and gas balance before retrying. A reverted destination transaction generally does not complete delivery; it may still cost gas.
If the app says the message can only be completed by the original application, return to that app rather than trying unrelated claim tools. Keep both transaction hashes, the transfer identifier, and a screenshot of the status for support. In your place, I’d wait while the VAA is still being produced, then make one careful claim from the original app as soon as it is ready.