A bridge transfer delay is time spent waiting for one of the steps that moves tokens between blockchains to finish. Check the source transaction first, then check whether the destination transaction has completed.
What happens while a transfer is pending?
A cross-chain transfer usually has several steps: your wallet sends a transaction on the first network, the bridge verifies it, and a transaction delivers the tokens on the second network. Each network is a separate blockchain, so the transfer needs time to pass between them.
For a Wormhole transfer, the source transaction locks tokens or burns them, depending on the transfer route. Wormhole’s Guardians then create a signed proof called a VAA, short for Verifiable Action Approval. The destination network checks that proof before releasing or creating the tokens.
Ethereum.org’s glossary defines finality as the point when a transaction can no longer be changed without a major cost. A bridge may wait for enough confirmation that the source transaction is settled. Busy networks, confirmation rules, and the chosen route can all affect the wait.
How can you tell which step is taking time?
Start with the transaction hash, a unique code for your wallet’s transaction. Find it in your wallet’s activity or in the confirmation screen, then look it up on the source network’s block explorer. A block explorer is a public site that shows whether a transaction succeeded, failed, or is still waiting.
For a Portal Bridge transfer, you can also look up the source transaction hash on Wormholescan to follow the bridge steps. Portal Bridge transfers can use manual or automatic completion, so check which route you chose before deciding whether you need to act. Wormhole’s transfer flow describes the same sequence: source transaction, signed proof, and destination completion.
Read the status in order:
- Source pending: the first network has not confirmed your transaction yet.
- Source failed: the transfer did not start; check the wallet’s error and token balance.
- Waiting for proof: the source transaction succeeded, but the signed VAA is not ready.
- Ready to complete: the proof is available; a manual route may need a destination transaction.
- Destination complete: check the receiving wallet’s address and token list.
What should you do if the tokens have not arrived?
Use the status to choose your next step. If the source transaction is pending, wait for the network or check whether your wallet offers a safe way to speed it up. If it failed, do not send again until you confirm the first attempt did not succeed.
If the proof is ready but the destination step is unfinished, check the bridge screen for a “Complete” or “Redeem” action. A manual completion usually needs a wallet connected to the destination network and enough of that network’s native coin to pay its transaction fee. For example, a transfer from Ethereum to Solana needs a Solana wallet and a little SOL for a manual destination transaction.
If the transfer says complete, confirm the recipient address and look for the token in the destination wallet. Some wallets hide new tokens until you add or import them. Check the token’s contract or mint address against the bridge’s transfer details before adding it.
As a quick check, if your source transaction succeeded at 2:14 and the bridge still says “waiting for proof” at 2:16, the delay is before destination delivery; use the status, not the clock alone, to decide what to do. Keep the transaction hash, and avoid repeating the transfer while the first one is still processing.