Why a Bridge Transfer Can Fail After Delivery
A delivered status can describe one step in a bridge transfer, not proof that funds reached the intended wallet; check the destination chain and transaction.
BitCurrent Newsroom3 min read
A bridge transfer can fail after delivery when “delivered” refers to a handoff or status update, not confirmed funds in the intended wallet. Cross-chain transfers involve a source transaction and a separate destination action, so check which step the status describes before retrying.
What does “delivered” mean on a bridge?
“Delivered” usually means the bridge or its relayer reports that a message or transfer reached a destination step. The exact meaning depends on the bridge’s status system.
A source transaction can be confirmed while the destination transaction is pending, reverted, or still being indexed by the bridge’s interface. In a relayed transfer, a service passes a message or asset between chains; delivery and final settlement may be separate events. For the handoff mechanics, this relay bridge guide provides more detail. A status label alone does not establish that the destination wallet received spendable tokens.
Why might the funds not appear in my wallet?
The most common explanation is a mismatch between the destination transaction and what the wallet displays. The transaction may be on a different destination chain, use a token the wallet has not added to its asset list, or send funds to an address other than the one you are checking.
Some transfers also deliver a different representation of an asset on the destination chain. That token can have a different contract address from the familiar version. A wallet may not show it automatically, even when the balance exists on-chain.
What should I check before taking action?
Start with the bridge’s transfer record and identify the destination chain, recipient address, token, and destination transaction hash. Open that transaction in the destination chain’s block explorer and check whether it succeeded and which address received the tokens.
If it succeeded, confirm that your wallet is connected to that chain and that you are viewing the right address. Verify a token’s contract address through the bridge’s own transfer details before adding it to a wallet. If the destination transaction is pending or reverted, save both transaction hashes and contact the bridge’s support with the transfer record.
Should I send the transfer again?
Wait until you know whether the first transfer completed on the destination chain. Sending again can create a second transfer if the first one was merely delayed or hidden from the wallet view.
What is confirmed is recorded on-chain: the source transaction and, if present, the destination transaction. What remains open is what a bridge status label means for that specific transfer until its destination result is checked.