Why a BTC-to-ETH Swap Can Take Longer Than Expected

A BTC-to-ETH swap can take minutes or longer; the route, Bitcoin confirmations, protocol processing and Ethereum payout determine the wait. In a direct cross-chain swap, you send BTC on Bitcoin and receive ETH on Ethereum, so two blockchains and a coordinating protocol have to do their parts. The swap itself may be quick, but it cannot skip the time needed to observe and settle transactions.

What happens after you send BTC?

In a THORChain swap, your Bitcoin transaction sends BTC to an inbound vault address and includes instructions for the destination asset and address. Bifrost, the service run by THORChain nodes to watch external chains, reports the deposit; nodes agree it is valid and the protocol processes it. In the pools, BTC is exchanged for RUNE, then RUNE for ETH. The vault network signs an outbound Ethereum transaction that sends ETH to your specified address.

Think of it as a relay: Bitcoin hands the deposit to the protocol, and the protocol hands the payout to Ethereum. Each handoff has its own clock. A fuller account of that route appears in thor swap. The THORChain developer guide describes this as one user-directed swap, even though the protocol performs two pool exchanges internally.

How long does each step take?

The first wait is for the BTC transaction to be included in a Bitcoin block and reach the confirmation threshold required by the route. Bitcoin targets an average block interval of about ten minutes, but blocks do not arrive on a timer: one may come sooner, while another takes longer. Protocols may require additional confirmations, especially to reduce the risk of processing a deposit that is later reversed.

After the deposit is accepted, node observation, processing and the outbound signing queue add time. The Ethereum transaction then has to be broadcast and included in a block. Inclusion makes the payout visible on-chain; Ethereum finality, which gives stronger assurance that a block will not be reversed, takes longer. A wallet or swap interface may show the payout before that finality point.

There is no single duration that applies to every BTC-to-ETH swap. THORChain’s quote response, for example, separates estimated inbound confirmation time, outbound delay and any streaming-swap time. Those are estimates for a particular quote, not a standing promise. A congested chain, a slow Bitcoin confirmation, a large outbound subject to throttling, or a network halt can extend the wait.

How can you estimate the wait before sending?

Use the current quote for the exact route and amount. Read its timing fields alongside the expected output and expiry, then refresh the quote just before sending. A quote can become stale as network conditions or protocol settings change, and an old deposit address or expired instructions may no longer be valid. Check the transaction status on the relevant chain explorer if the interface has not updated.

• Confirm that the source is native BTC and the destination is native ETH on Ethereum; wrapped assets and other networks have different steps.
• Check the estimated inbound confirmations and time. Bitcoin block intervals vary, so treat this as a forecast.
• Look for streaming or outbound-delay estimates. Streaming may split the protocol’s conversion across several internal steps.
• After the deposit confirms, track the payout transaction on Ethereum to see whether it has been broadcast and included.

For planning, rely on the live quote’s full estimate, not just the time until the BTC deposit appears in a block. If timing matters, leave room for both chains and the protocol’s processing queue; the BTC confirmation is only the first leg.