Cross-chain swaps trade speed against settlement certainty

For a cross-chain swap, wait for enough confirmation on the source chain to protect the deposit, then judge completion by the destination asset arriving. A fast quote or protocol-level transaction does not make Bitcoin or Ethereum transactions final at the same speed. The practical choice is how much confirmation risk and waiting time you accept.

What does finality mean in a cross-chain swap?

Finality means a transaction is settled enough that reversing it is no longer a realistic expectation. Each chain sets that threshold through its own consensus and block rules, so a swap that touches two chains depends on both chains’ settlement processes.

THORChain’s documentation describes a BTC-to-ETH swap as a Bitcoin deposit, internal pool swaps through RUNE, and an outbound transfer of native ETH after the deposit is observed. That is why the thor swap example is useful: one user action can still involve several stages before the destination asset appears.

Why can a faster swap carry more risk?

Speed settings can reduce the time spent waiting for confirmations, but they cannot change the underlying chain’s security model. If the source deposit has too few confirmations, a reorganization could undo it after the swap process has begun; if the destination chain is congested, the outbound transfer can still take time.

THORChain’s documentation says swaps are processed after observation of inbound transactions and describes network fees and price slippage as components of swap cost. In practice, speed and price are separate questions: a quicker path may affect fees or execution conditions, while the quoted output can also change with pool liquidity and trade size.

How should you choose between speed and certainty?

For most users moving a meaningful amount, confirmation certainty is the better priority. Check the swap interface’s minimum confirmations, expected completion time, and refund conditions; use a smaller test transaction if the route or wallet is unfamiliar.

Before sending, compare these details:

• Source-chain confirmation requirement and current network fee.
• Estimated destination amount after fees and slippage.
• Destination address and asset network.
• What happens if the swap times out or the output is delayed.

Choose speed when the amount is small enough that extra confirmation risk is acceptable and a short delay matters. For larger transfers, a longer wait is usually a reasonable cost for stronger confidence that the source deposit will hold, especially when the destination asset is needed for a later transaction.