Bitcoin confirmations can add around an hour to a cross-chain swap, but the exact wait depends on Bitcoin’s block timing, the fee attached to your transaction and the receiving system’s confirmation requirement.
Each confirmation adds another block after yours
A Bitcoin transaction is unconfirmed while it waits in the mempool, the network’s queue of pending transactions. When a miner includes it in a block, it has one confirmation; each new block built on top adds another.
Bitcoin targets an average block interval of about 10 minutes, so six confirmations take roughly an hour on average. Blocks do not arrive on a fixed schedule, though, and the Bitcoin Developer Guide presents six confirmations as a common security benchmark, not a guaranteed processing time or universal rule.
The swap waits for Bitcoin before it can continue
In a wallet-to-wallet cross-chain swap, you send BTC to an address for the swap. The service watches the Bitcoin network, detects the deposit and waits for enough confirmations before treating it as safe to process. It can then arrange the exchange and broadcast a separate transaction on the destination chain.
That creates two distinct waits: Bitcoin confirmations before processing, then the destination network’s own processing and confirmation time. A transaction showing as confirmed in your wallet may still be below the swap’s required threshold, so check its confirmation count and the swap’s status before deciding it is stuck.
The required count can vary because each service sets its own threshold to manage reorganisation risk: a reorganisation happens when the network replaces recent blocks with a competing history. THORChain’s public documentation, for example, describes waiting for enough confirmations to make a reorganisation economically infeasible; the same principle explains why a cross-chain swap may keep waiting after Bitcoin has included your transaction.
Your fee and the required count set the practical wait
A low miner fee can leave your transaction unconfirmed for longer when blocks are busy. Once it is in a block, the confirmation pace depends on new blocks arriving and on how many the receiving service requires. For example, if a deposit is included in a block and the service requires six confirmations, five more blocks must follow before that threshold is reached.
Before sending, check the Bitcoin address and network, choose a fee suitable for current demand, and keep the transaction ID. If the deposit is pending, use a block explorer or wallet to check whether it has entered a block; if it has, compare its confirmation count with the swap’s status. Avoid sending a second deposit just because the first is still waiting.
For someone moving from an exchange, the key change is that the Bitcoin deposit and the destination payout are separate on-chain events, with a confirmation wait between them. A cross-chain service such as thor swap coordinates the asset move across chains in one flow, while Bitcoin’s confirmations determine when the BTC side is ready to proceed.
Top comments (0)