Chainflip swaps: how to diagnose a pending transfer

A pending Chainflip swap is a transfer moving through separate source-chain, validator, State Chain, and destination-chain steps. First, your wallet broadcasts the deposit on the source chain; then validators watch for it and record it on Chainflip’s State Chain after the required confirmation process. The State Chain executes the swap, and validators arrange a separate payout to your destination address. Each step has its own transaction record, so “pending” alone does not say where the delay is.

What does each pending swap stage mean?

The stage shown by the tracker tells you which transaction to inspect. If it is waiting for a deposit, check the source-chain transaction hash in that chain’s block explorer: a wallet may show a transfer as submitted while it is still unconfirmed. Once confirmed, the deposit still needs to be detected and witnessed by validators before the State Chain records it. Bitcoin deposits can take longer to reach this point than deposits on faster chains because confirmation rules differ.

The tracker and the source-chain explorer answer different questions. The explorer shows whether the deposit transaction was included and confirmed; the swap tracker shows whether the protocol has registered and processed it. For a fuller account of how routes affect the swap, see this chainflip reference. Keep the source transaction hash and swap ID: one identifies the deposit, the other helps locate the swap’s later steps.

Why can a confirmed deposit still be pending?

A confirmed deposit is not the same as a completed swap. Validators must agree that the deposit is valid and register it on the State Chain. The State Chain then applies the swap route through its available liquidity. If the route crosses more than one pool, the protocol processes those pool swaps in sequence. A tracker that has not advanced may therefore point to witnessing or execution, rather than a problem with the wallet transaction.

Execution can also depend on the protections set when the swap was opened. A minimum price or other supported slippage limit can prevent execution at an unacceptable rate. If the swap cannot meet its conditions within its configured retry period, the protocol can send a refund to the refund address specified for that swap. A refund is a separate transaction, so it may need time to appear on the source chain.

What should you check before taking action?

Match the tracker details against the transfer you made before sending anything else. Check these points:

• Confirm the source transaction succeeded on the correct chain, and note its hash.
• Compare the deposit address, asset, and amount with the swap details.
• Check whether the tracker shows deposit detection, swap execution, payout, or refund.
• Verify the destination address and look for a separate payout transaction on its chain.

A deposit channel is temporary; Chainflip’s documentation says channels close after 24 hours. If a deposit was sent to an expired channel, or the asset or address does not match the swap, do not assume the tracker will resolve it automatically. Preserve the swap ID and transaction hashes, then use the publication or service’s official support route. Never share a recovery phrase or sign an unrelated transaction to “release” a pending swap.

What does a pending payout mean?

If the swap has executed but the payout is pending, the output transaction has not yet completed on the destination chain. Egress, Chainflip’s process for sending assets out, can batch transfers before validators sign and broadcast them. Check the tracker for a payout transaction hash; once it exists, use the destination chain’s explorer to see whether it is confirmed. The practical rule is simple: identify the stage first, then follow that stage’s transaction record.