If your bridge transfer is pending, first find out whether the source transaction reached a block; that decides what to do next. A bridge moves value between separate blockchains, and the destination part can take longer than the first part. A status label alone cannot tell you where the delay is.
For an older Bitcoin-to-token route, the RenBridge article can help you identify what the transfer was meant to do and which chain to check. RenBridge was discontinued in 2022, so it cannot complete a new transfer today. For any bridge, start with the transaction hash: the unique code you can search in that chain’s public record.
Did the source transaction confirm?
Check the hash on the blockchain where you sent the asset. If it has no block or confirmation, the bridge has not received a completed source transaction. If it appears as failed, the bridge usually cannot continue from it.
On Ethereum, a transaction can remain pending when its gas fee is too low for current demand. Gas is the network fee for processing a transaction. Ethereum.org explains that a wallet may let you speed up a pending transaction by replacing it with one using the same nonce, a number that orders your transactions. Do this only in the wallet that sent it, and check its instructions first.
For Bitcoin, a transaction in a block has one confirmation; each later block adds another. The Bitcoin Developer Guide says six confirmations take about an hour on average, but the wait varies with block timing. A bridge may require a particular number before it accepts the deposit, so one confirmation does not always mean the bridge is ready.
Why can the destination still be empty?
A confirmed source transaction is only the first stage. The bridge must recognize it, check that it meets its rules, then arrange the matching release or creation of an asset on the destination chain. Some bridges use lock-and-release; others lock an asset and issue a wrapped token, which represents it on another chain.
Say you sent Bitcoin to receive a wrapped token on Ethereum. Your Bitcoin transaction could be confirmed while the bridge waits for more confirmations or completes its checks. Only after that can the destination transaction appear. The two chains keep separate records, so check the source hash on Bitcoin and look for a separate transaction on Ethereum.
Open the status record from the bridge or service you originally used, and compare its source hash and destination address with your own records. If the source is confirmed but no destination transaction appears after the stated wait, keep the hash, amount, time, and destination address together. These details help distinguish a delayed transfer from one sent to the wrong address or network.
Should you retry, wait, or recover the funds?
Retry only after you know what happened to the first attempt. If the source transaction is still pending, sending again may create a second payment. If it confirmed, a second transfer can send more funds without fixing the first one.
If the source transaction failed on Ethereum, the transfer did not complete, though the network may still charge gas for processing the failed attempt. If the source confirmed and the destination is missing, do not assume the funds are lost or send a duplicate. Check the original service’s recovery instructions; refund and recovery options depend on that route’s rules.
If you cannot confirm that the service can still process the route, stop before sending more. This matters for RenBridge: its discontinuation means a new transfer cannot be completed through it. For a current route, use a cross-chain bridge and swap service that handles moving and swapping assets across chains in one flow; verify the route is available before committing funds.