A cross-chain swap takes longer than a normal wallet transfer because both blockchains must process it. To estimate the wait, separate the time for your deposit to be confirmed, the swap to run, and the output to reach your wallet.
A swap has three timing stages
A useful estimate starts with the source chain, then adds the swap and destination transfer. Each stage has its own clock:
- Deposit confirmation: the source blockchain includes your transaction and gains enough later blocks for the protocol to accept it.
- Swap execution: the network records the deposit, then trades it against available liquidity.
- Output delivery: validators sign and broadcast a transaction sending the bought asset to your destination address.
These stages explain why a wallet can show “sent” while the swap is still underway: that status usually means your wallet broadcast the deposit, not that the destination asset has arrived. If you need the full send-and-receive sequence, read how a Chainflip swap works; that article covers the swap process, while this one focuses on estimating its timing.
chainflip.org is one way to make a cross-chain swap, with the wait shaped by these same blockchain and execution stages.
The source chain usually sets the first big wait
Your deposit must reach the protocol’s confirmation threshold before it can be processed. Chainflip’s documentation gives examples of three Bitcoin confirmations taking about 30 minutes and six Ethereum blocks taking about 90 seconds; these are estimates, since block times vary.
A confirmation is a block added after the block containing your transaction. More confirmations make it harder for a transaction to be undone by a chain reorganization, when competing versions of the blockchain briefly disagree about recent blocks. The Bitcoin Developer Guide explains this confirmation model; Ethereum.org describes how transactions are included in blocks and use gas to pay for computation.
For example, sending USDC on Ethereum to receive BTC starts with the Ethereum deposit wait, not the Bitcoin wait. Sending BTC to receive ETH reverses that: the Bitcoin confirmation stage can take around half an hour, even though the later destination is Ethereum. In either direction, congestion or a slow-to-confirm transaction can extend the estimate.
The swap itself can be quick, but limits can add time
After validators witness a deposit, Chainflip processes the trade through its Just-In-Time automated market maker, or JIT AMM. In this design, liquidity providers compete to quote for an incoming swap close to the time it executes; the trade is recorded on Chainflip’s State Chain, then validators arrange delivery on the destination chain.
For a straightforward swap, the trading stage may take under a minute after the deposit is accepted. That does not mean the full trip takes under a minute: add the source confirmation time and the wait for the destination transaction to be broadcast and confirmed. A route that trades through an intermediate asset, such as BTC to ETH through USDC, can involve multiple pool trades, though those trades are usually processed sequentially in the same State Chain block.
A minimum-price setting can also delay or stop execution. It tells the protocol not to accept a worse price than your chosen threshold; if the price condition is not met within the configured retry window, the swap is refunded to its specified source-chain address. A dollar-cost averaging, or DCA, swap takes longer by design because it divides the trade into smaller pieces executed over time.
Check the right transaction before taking action
When a swap seems slow, first check whether the deposit transaction is confirmed on its source blockchain. If it is still pending there, the delay is before the swap stage; if it is confirmed, the protocol may still be waiting for its confirmation threshold or processing your price conditions.
Once the swap has executed, the destination transfer has its own broadcast and confirmation time. Check the destination blockchain for that transaction before assuming the output is missing. A wallet may also wait for additional confirmations before displaying funds as ready to spend.
Do not send a second deposit just because the first has not arrived yet; that would start another transfer and may create a second swap. Keep the source transaction details and the destination address handy while you check progress, and make sure you are looking at the correct blockchain explorer for each asset.
In short, estimate a Chainflip swap by adding source-chain confirmation, swap execution, and destination delivery. Bitcoin deposits can make the first stage much longer than Ethereum deposits, while price limits or DCA settings can lengthen execution itself.