A pending cross-chain transfer is not always a lost transfer. First check whether the source transaction is still waiting, completed, or failed; then check whether the destination action ran. A bridge may need time to confirm the source and deliver the funds, so sending the same transfer again too soon can create a second payment.
Where is the transfer stuck?
A cross-chain transfer can involve more than one transaction. Your wallet sends assets or a swap request on the source chain, then a bridge service arranges delivery or a trade on the destination chain. A relayer is a service or participant that passes the transfer information between those steps.
Check the source transaction hash in the source chain’s block explorer, a site that shows public transaction records. If you are tracking a relay bridge transfer, compare its source and destination status before retrying; a source success can coexist with a destination action that is still waiting.
Read the transaction result, not only the wallet’s spinner. On Ethereum, a receipt marked successful means the transaction ran without reverting; a failed receipt means its contract action did not complete. Other chains show equivalent transaction details in their explorers, though labels differ.
- Pending: The source transaction has not been included in a block. Network congestion or a low fee may be holding it up.
- Source confirmed: The source action ran, but the bridge may still need final confirmation or a destination transaction.
- Destination failed: The source may have completed while the receiving action failed, for example because execution ran out of gas or a swap condition was no longer met.
- Completed: Check the destination wallet and its chain. The received token may have a different name or address than the source asset.
What should you do before retrying?
Match the source and destination records using the transaction hash or transfer identifier shown by the service. A hash is the transaction’s unique reference. If the source is still pending, check whether your wallet supports replacing that same transaction; do not start a separate bridge transfer just because the first one is slow.
If the source succeeded, look for a destination transaction or a status that says the bridge is still processing. In some designs, the bridge waits for source-chain finality, meaning enough agreement that the source block is unlikely to change. In others, a liquidity provider—a service that supplies tokens for a swap or payout—may need to complete the delivery. These steps take different amounts of time across chains and services.
If the destination transaction failed, read its failure reason before taking action. A swap can fail when the received amount would fall below the minimum you accepted, often called slippage tolerance, the allowed price movement. The source asset may then remain recoverable or require another action, depending on the bridge design; confirm the service’s status before sending again.
When is it safe to take another step?
Retry only after you know what happened to the first transfer. A failed source transaction usually means the requested transfer did not run, though the network may still charge a transaction fee. A successful source transaction is different: the assets may already be committed to delivery, so a second transfer could move extra funds.
For a relay bridge transfer, use the original record to decide whether it needs more time, a destination-side action, or a fresh source transaction. If the status stays unchanged beyond the service’s stated processing window, contact its support through its official site and share the transaction hash; never share your recovery phrase or private key.
Before acting, ask yourself: have I confirmed the first transfer’s source and destination outcomes, or am I about to pay twice because one screen still says “pending”?
Top comments (0)