How a THORSwap route reaches another chain

THORSwap combines liquidity from decentralised exchanges with THORChain’s cross-chain pools to route a source asset into an asset on another chain. The interface can present that route as one swap, but the execution may contain several on-chain transactions and protocol steps. “One flow” describes how the route is selected and initiated; it does not make the chains settle as one atomic transaction.

That distinction matters when a route begins with a token that THORChain does not pool directly. A local DEX can exchange that token for one THORChain supports, after which THORChain can swap it across chains. The fuller account of thor swap explains when the native pool route fits. The useful question is what each leg does, and which network must confirm it.

How does THORSwap move value between chains?

THORSwap selects a route across available liquidity sources; THORChain’s pools provide the cross-chain leg when the route uses its protocol. Each supported THORChain asset has a pool paired with RUNE, the network’s settlement asset. A swap between two pooled assets therefore trades the source asset against RUNE, then RUNE against the destination asset. The user does not need to hold or manually transfer RUNE between those steps.

For a direct native BTC-to-ETH swap, for example, the user sends BTC to a THORChain vault address and specifies the destination in the transaction memo. THORChain nodes observe the inbound transaction. Once the network processes it, the protocol performs the pool swaps and instructs its vaults to send native ETH to the requested address. Threshold-signature transactions allow the node network to authorize vault spending collectively; the user does not deposit BTC with a central exchange or receive a wrapped BTC representation as an intermediate asset.

An aggregated route can add a local DEX leg before or after that cross-chain step. An ERC-20 token that is not in a THORChain pool might first trade against a supported asset on an Ethereum DEX. THORChain can then move value to the destination chain, where another local trade may be needed to reach the requested token. The route’s quote represents those legs together, but each component still follows the settlement rules of its own chain and liquidity source.

What does “one swap” mean in practice?

It means the interface can quote and coordinate a multi-step route from a single intent. It does not mean one transaction covers every chain. The source wallet may need to approve a token contract and submit a swap transaction; a native coin input avoids an ERC-20 approval. The source-chain DEX transaction, THORChain’s inbound deposit, and destination-chain payout are distinct events, even when the interface tracks them as one route.

Before signing, inspect the quoted output, the route, and the destination address. The displayed amount is an estimate based on current pool depth, DEX liquidity, and network fees. Pool trades incur price impact: the larger the swap relative to available liquidity, the more the trade shifts the pool price. The route can also include outbound network fees, source-chain gas, and a fee charged by a DEX or integrator. A quote’s estimated output is not a guaranteed receipt unless the transaction includes and enforces an applicable minimum-output limit.

• Input asset: Check that the token contract and chain match the asset you intend to spend. Similar names and tickers do not identify the same token.
• Route: See whether the quote uses a local DEX, THORChain pools, or both. More legs can extend the number of confirmations and sources of execution risk.
• Output: Confirm the destination chain and address, then compare the minimum acceptable output with the quoted amount after fees.
• Gas: Keep the source chain’s native gas token available. Token approval and transaction submission may require separate gas payments.

What can delay or break the route?

Each chain has its own confirmation and transaction rules, so the full route is not atomic across chains. A source transaction can confirm while a destination payout is still pending. An invalid memo, unsupported asset, or destination address that cannot receive the asset can prevent normal completion; protocol rules may refund an invalid inbound swap, but a refund is another on-chain transaction and can incur fees. A chain congestion event can delay observation or payout without changing the quoted route into a single reversible transaction.

Liquidity is another constraint. THORChain routes only through active pools for supported assets; THORSwap’s added DEX liquidity can widen token choice, but it does not remove pool depth limits, slippage, or network costs. Routes and quotes can change as liquidity and gas conditions change. Treat the quote as a snapshot, and review it again before signing if execution has been delayed.

For most users who want to move between native assets supported by THORChain, the direct pool route has fewer moving parts: it uses the source and destination pools linked through RUNE. An aggregated route is useful when the requested token needs local DEX liquidity to enter or leave that network. In both cases, the interface simplifies route selection; the chains, vaults, pools, and fees still determine how the swap actually settles.