Why Your BTC-to-ETH Swap Is Waiting on Bitcoin

A BTC-to-ETH swap waits on Bitcoin when the BTC deposit has not yet been confirmed on Bitcoin’s blockchain. Seeing the transaction in a wallet or explorer only shows it was broadcast; it does not mean the swap protocol can safely act on it. Bitcoin block times vary, and a low transaction fee can leave a payment waiting longer for inclusion. For a fuller walkthrough of the native route and its wallet steps, see this guide to thor swap. The key first check is the Bitcoin transaction status, not the ETH balance.

Why does a BTC-to-ETH swap depend on Bitcoin confirmations?

The swap starts with an ordinary Bitcoin transaction from your wallet to the protocol’s Bitcoin deposit address. Bitcoin nodes can relay that transaction before a miner includes it in a block, but until then it has zero confirmations. A confirmation means the transaction has entered a block; each later block adds another confirmation and makes reversal harder. The Bitcoin developer guide explains why recipients treat unconfirmed payments differently: conflicting transactions can compete before one is recorded in the chain.

That wait is part of the trade-off of swapping native BTC directly. The protocol has to observe the deposit on Bitcoin before it can account for the funds and proceed. Bitcoin block discovery is probabilistic: roughly ten minutes is an average between blocks, not a deadline for any particular transaction. When demand for block space is high, a fee rate below miners’ current priorities can add more delay. A swap interface cannot make Bitcoin confirm faster by updating its own status screen.

What happens after Bitcoin confirms?

Once the deposit is confirmed and observed, the protocol processes the swap through its connected liquidity pools. In THORChain’s design, BTC first swaps against RUNE in the BTC pool, then RUNE swaps against ETH in the ETH pool; the user receives native ETH from a protocol vault. RUNE is the internal link between the pools, not an asset the user needs to handle. The THORChain swap documentation describes this two-pool route.

Bitcoin confirmation is only the first external-chain step. The protocol still has to observe and process the inbound transfer, execute the pool swaps, and arrange an outbound Ethereum transaction. A delay after Bitcoin confirms can therefore point to protocol processing or the Ethereum payout rather than a Bitcoin problem. The outbound transaction has its own network fee and confirmation time. Unlike an exchange that can show an internal account balance before a withdrawal, a native cross-chain swap depends on activity on both chains. THORChain’s native swap explanation describes the inbound, internal, and outbound stages.

How can you tell where the swap is waiting?

Start with the BTC transaction ID shown by the sending wallet. Look it up on a Bitcoin explorer and compare its status with the swap interface; the distinction between “unconfirmed” and “confirmed” narrows the cause considerably.

• No transaction ID: Check whether the wallet actually broadcast the send and whether it shows a pending or failed transaction.
• Zero confirmations: The swap is still waiting on Bitcoin. Check the fee rate and whether the transaction appears in the mempool; the Bitcoin FAQ notes that low-fee transactions may wait longer for a block.
• Confirmed BTC, no swap progress: Compare the destination address and amount with the swap details, then check the protocol’s transaction status. The protocol must observe the confirmed inbound transaction before proceeding.
• Swap processed, ETH not visible: Look for the outbound Ethereum transaction and check its status on Ethereum. A sent payout and a confirmed payout are different stages.

Use the transaction IDs and the swap’s own status to identify the stage before taking action. Avoid sending a second deposit just because the first one appears slow: the first transaction may still confirm, and a duplicate deposit can start another swap. If the BTC transaction remains unconfirmed, check whether your wallet offers a fee-bump option and follow that wallet’s instructions. If Bitcoin shows confirmation but the swap status remains unchanged, consult the swap interface’s support or status guidance with the transaction ID.

How does this compare with other ways to trade BTC for ETH?

A centralized exchange can credit a deposit according to its own confirmation policy, then match a BTC-to-ETH trade on its internal order book. That can make the trading step feel faster, but the deposit and any later withdrawal still depend on the exchange’s processes and custody. A bridge or wrapped-asset route changes the mechanics again: it can avoid a direct native BTC-to-ETH swap, but introduces a wrapped representation and the bridge’s own operating assumptions. THORChain’s pool route keeps the swap native, while exposing the user to Bitcoin’s confirmation wait, pool price impact, and an Ethereum payout.

There is no universal countdown for a pending BTC-to-ETH swap. The useful signals are the Bitcoin transaction’s confirmation count, whether the protocol has observed the deposit, whether the two pool swaps have executed, and whether an Ethereum outbound transaction has been broadcast and confirmed. Those checkpoints show whether the delay is still on Bitcoin or has moved to another part of the route.