Plan for roughly 20–30 minutes or more when a Bitcoin deposit must wait for confirmations. A cross-chain swap has several stages: the source blockchain confirms your deposit, the swap protocol processes it, and the destination blockchain records the outgoing transaction. The slowest stage usually sets the pace.

With Chainflip, for example, validators watch the source chain and wait for its required confirmations before the deposit is accepted. The protocol then swaps the assets and sends the result to your destination address. This lets you receive native ETH on Ethereum without first converting your BTC into a wrapped token.

What determines the wait

The time depends first on the blockchain you send from. Bitcoin blocks average about ten minutes, but they do not arrive on a perfect schedule. A protocol also waits for a set number of confirmations—later blocks that make it safer to treat a transaction as settled—before it acts on a deposit.

Next comes swap processing. Once the deposit is accepted, the protocol records it, trades through any required asset pools, and prepares the outgoing transfer. That stage may take seconds or minutes; if the route uses intermediate assets, those trades can still happen within the same processing window.

Finally, the destination chain must include the outgoing transaction in a block. Network activity and transaction fees can affect this wait. So a fast swap stage does not mean the ETH appears immediately after you send BTC.

Follow a BTC-to-ETH swap from start to finish

Imagine you send BTC and want ETH in your Ethereum wallet. A published Chainflip example allows about 30 minutes for the Bitcoin deposit-confirmation stage, then about 48 seconds for swap processing. Those are illustrative estimates; actual timing varies with block arrivals and protocol settings.

1. Send the BTC. The transaction first needs to reach a Bitcoin block. If it waits in the network’s queue, confirmation has not started.
2. Wait for the required confirmations. The protocol watches later Bitcoin blocks before recognizing the deposit. This is why a BTC-to-ETH swap can take longer than one that starts on a faster-confirming chain.
3. Allow for the trade. After the deposit is recognized, the protocol processes the swap. A route that needs more than one asset pool may involve multiple trades.
4. Wait for Ethereum. The protocol broadcasts ETH to your destination address, and Ethereum must include that transaction in a block before your wallet reflects it.

In this example, the deposit stage dominates: 30 minutes plus roughly a minute for processing, followed by the Ethereum transaction’s inclusion time. Treat that as a planning estimate, not a delivery promise.

How to tell whether the wait is normal

Check the transaction status on the source chain first. If your Bitcoin transfer has no confirmation, the swap cannot proceed through the usual confirmation path. If it is confirmed, allow time for the protocol to register the deposit, process the trade, and broadcast the destination transaction.

Before sending, verify that the destination address belongs to an Ethereum wallet you control and that it can receive ETH. Keep your transaction ID so you can check whether the source transfer has confirmed. For a first swap, choose an amount you are comfortable managing and check the current estimate for the exact source and destination pair before sending.