How do swap services handle a chain halt or fork while your trade is in progress

05 September 2026

A swap service typically pauses your trade and holds your deposited coins until the halted chain resumes or the fork resolves. It does not simply cancel the order or lose your funds. The exact handling depends on the type of disruption and the service's internal rules.

Chain halts and forks are rare but real events that break the normal flow of a cross-chain swap. When you deposit coins on chain A, the service must receive confirmation, then send the corresponding coins on chain B. If chain A halts mid-confirmation, the service cannot verify your deposit. If chain B forks while the outgoing transaction is pending, the service may be unsure which fork is canonical. In both cases, the service’s priority is to avoid sending funds to the wrong chain state or losing them entirely.

For a chain halt on the deposit side, most swap services wait for a predetermined number of block confirmations before treating a deposit as final. If chain A stops producing blocks, those confirmations never come. The service sees an unconfirmed or partially confirmed deposit. Its software will flag the order as stalled. Some services set a time limit - commonly 24 to 72 hours - after which they mark the order as failed and allow you to contact support for a manual refund. Others hold the deposit indefinitely until the chain resumes, then process the swap normally. The key point: your coins remain on chain A, controlled by the service’s wallet, and are not lost unless the chain becomes permanently unusable.

For a fork on the deposit chain, the service waits for the network to reach consensus. Most reputable services require a high number of confirmations - often 30 or more - to reduce fork risk. If a fork occurs before that threshold, the service monitors both chains. Once the longest chain (by proof-of-work or validator consensus) becomes clear, the service treats the deposit on that chain as valid and proceeds. Deposits on the orphaned fork are ignored; the service will not credit them. This is why you must wait for sufficient confirmations before a swap is considered irreversible.

On the payout side, a fork is trickier. The service may have already broadcast the outgoing transaction on chain B. If chain B forks after that broadcast, the transaction could exist on both forks or only one. Most services simply let the fork resolve and then check whether the payout was included in the canonical chain. If it was, the swap is complete. If it was not - because the transaction ended up on the orphaned fork - the service will re-send the payout on the winning chain. This can delay your receipt by hours or days. The service bears the cost of the second transaction fee, not you.

Chain halts on the payout side are handled similarly: the service waits. It cannot send coins to a halted chain because the transaction would never confirm. The service holds your outgoing coins in its wallet until the chain resumes, then broadcasts the payout. Some services automatically cancel the order after a long halt (e.g., 72 hours) and return your deposit on chain A, minus any fees incurred.

No swap service can guarantee zero risk during a chain halt or fork. The safety of your coins depends on the service’s operational policies - specifically, how many confirmations it requires, how long it waits before escalating, and whether it has a clear refund process. Before using any service, read its terms or FAQ for its “chain halt” or “fork” policy. If that information is not visible, consider that a red flag.

For a broader view of how these trades work without bridges or centralised accounts, see the hub page “Swapping crypto across chains.” It explains the underlying mechanics that make these scenarios possible - and why disruptions are so rare.

Back to wrapped assets