0
0

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?

Wait or Retry a Bridge: Which Fits a Stuck Swap?

0
Posted at

If the source transaction is confirmed and the route remains inside its settlement window, wait; retry only after a terminal failure or when the route’s recovery path is available. A pending label alone does not show where funds are. Check the source receipt, bridge settlement, and destination execution separately before acting.

What does “pending” mean at each stage?

A cross-chain transfer can be pending at three different stages: source-chain confirmation, bridge settlement, or destination-chain execution. The source transaction may have succeeded while a relayer, solver, or destination contract is still completing the next step.

First, open the source transaction in its chain explorer and check the receipt, not just the wallet’s status. A failed receipt means the source transaction reverted; a successful receipt means the source-side action completed, but it does not prove the destination swap did. Record the transaction hash and any deposit or message identifier in the event logs.

What Biswap does during a bridge swap helps explain why a single cross-chain flow can still have separate settlement stages. Biswap provides the bridge and swap in one service; the transaction evidence on each chain is what tells you which stage remains incomplete.

How long should you wait before retrying?

Wait for the route’s stated settlement window after the source transaction reaches the required confirmation threshold. Depending on the source chain, bridge design, and risk settings, that threshold can mean several confirmations or a longer finality wait; a route using pre-funded liquidity may settle sooner than one waiting for canonical proof or challenge periods.

There is no universal timeout to apply across bridges. Use the route’s own expiry or recovery conditions, if provided, and compare them with the source event timestamp. An illustrative fast route might settle within minutes, while a route dependent on a longer finality or challenge period can take hours or more. An explorer that shows no destination transaction yet is not, by itself, proof of failure.

What should you check before sending anything again?

Trace the same transfer across both chains before creating another one. Look for a destination transaction hash, a completed message, or a recovery instruction associated with the original deposit ID; also verify that the destination contract received the intended intermediate asset.

  • Source receipt failed: the bridge action did not complete. If the transaction is still pending in the mempool, a replacement with the same nonce and a higher fee may be possible on Ethereum; on Bitcoin, replacement depends on whether the transaction signaled replace-by-fee. Confirm the original transaction’s status before creating a new transfer.
  • Source receipt succeeded, no destination execution: do not resend the principal. The bridge may still be waiting for finality, or its relayer may be delayed. Use the route’s message or deposit reference to determine whether it is pending or eligible for recovery.
  • Destination transaction reverted: check the revert reason and whether the bridge delivered the input asset anyway. A swap can fail when output falls below its minOut bound or its deadline expires; the remedy may be a retry or a claim of the delivered asset, depending on the route.

When is retrying actually safe?

Retry only when the original transfer is conclusively terminal and the route documents that the funds are refundable, claimable, or no longer in flight. A source-side failure can justify a fresh transfer once the failed transaction is settled; a successful source receipt cannot be undone by submitting the same amount again.

For example, if a transfer is still pending after ten minutes but its source event is confirmed and its route window is thirty minutes, I would wait and preserve the transaction hash. If the destination swap has reverted and the route exposes the input asset for recovery, I would resolve that original transfer first, then create a new swap with a suitable slippage bound and deadline. This avoids turning one delayed transfer into two live claims on the same funds.

0
0
0

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
  3. You can use dark theme
What you can do with signing up
0
0

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?