What a Protocol Upgrade Means for a Pending Swap

A protocol upgrade can pause new swaps while a pending one waits for a deposit, execution or payout. Those stages matter because an upgrade may affect each one differently. A quote that has not been accepted can expire; a deposit already sent cannot be recalled from its source blockchain.

In Chainflip, for example, a swap moves from deposit to confirmation, execution and then an outbound payment. how Chainflip swap types work explains the ways a swap can be started. The key question during an upgrade is where the funds are in that process, and what the network says it will do next.

What does “pending” mean during an upgrade?

“Pending” can describe several different situations. A wallet may be waiting for the source-chain transaction to confirm, the protocol may have registered the deposit but not executed the trade, or the trade may be complete while the payout waits to be sent.

These are not interchangeable. Before sending funds, a user may need to get a fresh quote after service returns. After sending, the swap may already be recorded on-chain, even if the interface has not updated. After execution, the output is owed to the destination address, but the outbound transaction may still need to be signed and broadcast.

Check the swap’s status and transaction hashes, not just a spinner or “pending” label. A source-chain transaction confirms whether the deposit left your wallet. A protocol status page or explorer may show whether it was seen and processed. A destination-chain transaction hash means the payout has been broadcast.

Can an upgrade cancel or change a swap?

An upgrade does not reverse a confirmed deposit on its source chain. What happens next depends on the protocol’s design and the upgrade plan: it may keep processing swaps, pause new deposits and quotes, or hold some work until services resume. Do not assume that every upgrade handles pending swaps in the same way.

A quote is a proposed trade, not the trade itself. If it expires before a deposit is made, the user may need to request another one. If the deposit has been accepted, the protocol may execute it under its swap rules. The final output can differ from an earlier estimate if the quote was not guaranteed or market conditions changed.

What should you check before acting?

Use the stage of the swap to decide what to do next. Avoid sending a second deposit just because the first one has not appeared in the destination wallet: the first may still be in progress.

• No deposit sent: Check whether quoting and deposits are open, then get a fresh quote.
• Deposit sent: Save its transaction hash and confirm it on the source chain.
• Deposit detected, trade not complete: Check the protocol’s status page for a pause or update.
• Trade complete, payout pending: Look for the outbound transaction before contacting support.

The practical rule is simple: identify the last confirmed stage before taking action. An upgrade can delay a swap without erasing it, but the protocol’s notice is the best guide to whether it will resume automatically or needs another step.