Why Bitcoin Swaps on Chainflip Take About 30 Minutes

A Bitcoin-funded Chainflip swap often needs roughly 30 minutes before execution because validators wait for Bitcoin confirmations before recording the deposit on Chainflip’s State Chain. Bitcoin produces blocks at an average interval of about 10 minutes, so the wait is an average, not a countdown. The swap itself usually takes seconds once the deposit is witnessed.

Why does Chainflip wait for Bitcoin confirmations?

Validators use a confirmation window, called a safety margin, before they treat a Bitcoin deposit as final. The margin reduces the chance that a chain reorganization—a rollback of recent blocks—could erase a deposit after Chainflip has already acted on it. Chainflip’s protocol documentation lists a two-block safety margin for Bitcoin; its swap guide describes the practical wait as three blocks, about 30 minutes, including the block containing the deposit.

Bitcoin block times vary. A transaction also has to get into a block: if the mempool is busy or its fee rate is low relative to competing transactions, it may wait before its first confirmation. After that, the required blocks still need to arrive. For a closer look at how the chosen assets affect the route, see this fuller guide to chainflip swaps.

What happens after the Bitcoin deposit is confirmed?

Validators witness the deposit by registering it on the State Chain after the confirmation window passes. More than two-thirds of the validator set must submit matching witness records for the event to be finalized. The Just-In-Time automated market maker (JIT AMM) then processes the swap on the State Chain. A route that uses multiple liquidity pools can involve sequential swaps, usually in the same State Chain block.

The explorer’s status gives a practical view of where time is going:

• Awaiting Deposit: the deposit has not been detected.
• Deposit Detected: validators have seen it, and the confirmation window is still in progress.
• Swap Executing: the deposit is confirmed and the AMM is processing the trade.
• Broadcast Requested or Complete: validators are preparing or have sent the output transaction to the destination chain.

The roughly 30-minute estimate covers the Bitcoin-side confirmation wait. It does not mean the destination asset is already in the recipient wallet: Chainflip still has to prepare and broadcast the payout, and the destination chain must process it. Check the swap’s explorer status to tell a source-chain wait from a later payout stage.

Can a Bitcoin swap be faster?

Chainflip Boost can let a swap proceed after the deposit appears in a Bitcoin block, using liquidity-provider collateral in place of waiting for the full confirmation window. The user pays a Boost fee, and the protocol only boosts the deposit if sufficient collateral is available. If it is not, the swap follows the regular confirmation path and no Boost fee applies.

Boost trades a shorter wait for a fee; it does not make Bitcoin blocks arrive faster. If the fee is acceptable and Boost is available for the swap, it can reduce the confirmation delay. Otherwise, allow around 30 minutes for the Bitcoin confirmation stage, with extra time possible for a delayed first block, and check each stage in the explorer. What is confirmed is the deposit’s status and the protocol’s progress; the exact time until payout remains dependent on Bitcoin block production and the destination transaction.