Why THORChain Routes Source Assets Through RUNE in 2026

On THORChain, a native asset such as BTC does not swap directly against every other supported asset: cross-asset routes pass through RUNE-linked liquidity pools. The protocol’s documentation describes each pool as a pair between RUNE and one connected asset, so a BTC-to-ETH trade uses the BTC:RUNE and RUNE:ETH pools.

This hub structure lets liquidity connect many assets without requiring a separate pool for every possible pair.

Why does THORChain route swaps through RUNE?

THORChain’s pool design makes RUNE the shared asset between connected chains. A direct BTC:ETH pool would require liquidity providers to deposit both BTC and ETH into that pair; adding more assets would mean adding more pairs, each with its own liquidity. With RUNE as the common side, each asset pool can contribute to routes across the network. That concentrates the pool design around a shared hub, though it does not guarantee equal depth or the best price for every route.

In a BTC-to-ETH swap, the network first trades BTC against RUNE in one pool, then trades that RUNE against ETH in the second. THORChain’s swap documentation says the state machine processes these legs as one user-facing swap, so the user sends BTC and receives ETH without handling the intermediate RUNE. For a fuller walkthrough of that path, thor swap explains the cross-chain sequence in more detail.

What does the two-pool route mean for execution?

Each pool leg changes the balance between its two assets, and THORChain’s liquidity documentation says the pool ratio determines the price. The amount received therefore depends on the size of the trade relative to available pool depth across both legs. The route is operationally one swap, but its output reflects two pool calculations, along with network fees such as the destination-chain outbound fee.

The protocol also supports streaming swaps: according to its developer documentation, a trade can be divided into smaller sequential swaps, allowing time for arbitrageurs to rebalance pools between them. That can reduce price impact for a patient trader, while execution takes longer. It does not remove chain fees or guarantee a particular output; a minimum-output limit can define when the swap should stop and be refunded.

How should a trader assess a source-asset route?

For a specific trade, use the route quote to judge the expected output and timing rather than assuming that a supported source asset has a direct pair with the destination. THORChain’s developer guide describes quotes that account for the selected assets, destination address and swap parameters. Check that the destination chain and address match the asset you intend to receive, and compare the quoted output with the amount sent after fees.

• Confirm the source and destination assets are supported and their pools are active.
• Review expected output, price impact, inbound and outbound fees, and estimated completion time.
• Set a minimum output when the interface or integration supports it, especially if the quote may change before execution.
• Consider streaming execution for larger trades when a longer settlement window is acceptable.

The route through RUNE is a liquidity architecture choice: it connects many source assets through shared pools, while exposing each cross-asset trade to the depth and price impact of both pool legs. A quote for the exact route is the practical way to decide whether that trade-off fits a particular swap.