If you have sent Bitcoin for a cross-chain swap, wait for the required confirmations before treating a quiet status as a failure. Bitcoin must confirm the payment first; only then can the swap run and the destination asset be sent.
Why does a Bitcoin swap take longer than one transaction?
A cross-chain swap joins activity on two separate blockchains. For a BTC-to-ETH swap, Bitcoin first records your payment, the swap protocol processes it, and Ethereum then records the ETH payment to your wallet.
For a native-asset route such as BTC to ETH, Chainflip is one way to make the swap. Its validators—network operators that check transactions together—watch the Bitcoin deposit and report it to the protocol.
Bitcoin adds a new block about every 10 minutes on average, though the interval varies. Chainflip’s published flow describes waiting for three Bitcoin blocks, or roughly 30 minutes, before the deposit is treated as final by its State Chain, the part of the protocol that records deposits and runs swaps.
What happens after Bitcoin confirms the deposit?
After the Bitcoin confirmation wait, validators agree that the deposit is real and record it on the State Chain. This shared check helps protect the protocol if Bitcoin reorganises—when it replaces recent blocks with a different version of the chain.
The swap then runs through the JIT AMM, short for “just-in-time automated market maker.” In plain terms, this is the protocol’s system for matching a swap with available trading liquidity. The published example puts this processing at about 48 seconds after the deposit is confirmed.
Some routes use more than one trading pair. For example, BTC to ETH may trade through BTC-to-USDC and then USDC-to-ETH. The protocol can process those trades in sequence, usually in the same State Chain block.
Last, validators send the ETH to the destination address. That payment still needs to be included in an Ethereum block, so your wallet may show the result later than the swap itself. The destination chain and its activity affect this final part.
What should I check if the swap seems stuck?
Start with the Bitcoin transaction ID, often called a txid. Look it up in a Bitcoin block explorer and check whether the transaction is still unconfirmed or has appeared in a block. If it is unconfirmed, the wait is on Bitcoin; the protocol cannot process a deposit it has not yet seen and confirmed.
A common mistake is to send the same amount again because the first transfer has not produced the destination asset yet. Don’t resend while the original payment is pending. Check its confirmation count first, then check whether the protocol has registered it and whether the outgoing payment appears on the destination chain.
Once the Bitcoin deposit has enough confirmations, allow time for the protocol and destination chain to finish their parts. If the deposit is confirmed but there is no outgoing transaction, use the transaction details to identify which stage is waiting. Chainflip’s status records can distinguish a confirmed deposit from a swap that has been processed and a payment that has been sent.
Can the Bitcoin waiting time be shorter?
Some Bitcoin swaps may use Boost, an option that can release a deposit after its first Bitcoin confirmation when enough backing liquidity is available. It can shorten the wait, but it may add a fee; if liquidity is unavailable, the deposit follows the usual confirmation process.
Timing also depends on how quickly your Bitcoin transaction gets into a block. During busy periods, a transaction can wait in Bitcoin’s queue before its confirmation count even begins. A longer wait at that point does not mean the swap has failed.
In practice, separate the process into three checks: Bitcoin inclusion, protocol confirmation and swap, then delivery on the destination chain. Before sending, ask yourself: can I wait for Bitcoin’s confirmation window, and have I checked the destination address carefully?
Top comments (0)