A First Cross-Chain Swap: Pool Depth Versus Withdrawal

A first cross-chain swap trades one supported asset for another through THORChain’s liquidity pools; it does not withdraw someone else’s pool share. That distinction matters because pool depth sets the trade’s price impact, while a withdrawal returns an existing liquidity provider’s portion of a pool. THORChain’s documentation describes each supported asset as paired with RUNE, the asset that links pools together. A swap from BTC to ETH therefore passes through the BTC:RUNE and RUNE:ETH pools, even though the user submits one swap request and does not need to handle RUNE.

How does a THORChain cross-chain swap work?

A cross-chain swap sends the input asset to a THORChain vault, where the network processes it through the relevant pools and arranges an outbound transfer of the requested asset. The Swappers documentation describes the two-pool route: the input asset is swapped to RUNE, then RUNE is swapped to the destination asset. The network’s nodes observe the inbound transaction and sign outbound transactions through its vault system, according to THORChain’s documentation on Bifrost, TSS and vaults.

For a first swap, the practical sequence is to choose an input asset and destination, connect a compatible wallet, and review the route, estimated output, fees and slippage before confirming. THORChain’s usage guide notes that a token on a smart-contract chain may require a separate approval before the swap itself. The fuller comparison of swap and bridge routes is covered in thor swap; here, the key point is that a swap uses pool liquidity, while a bridge route moves assets between networks under a different mechanism.

What does pool depth mean for swap capacity?

Pool depth is the amount of each asset available in a pool, and it influences how much a swap moves the pool’s price. THORChain’s Continuous Liquidity Pool documentation describes a slip-based fee: larger trades relative to pool balances create more price impact and incur a larger liquidity fee. A route between two non-RUNE assets touches two pools, so the size and balance of both pools affect the result.

“Capacity” is therefore better understood as an estimate of how much can be traded at an acceptable cost, rather than as a simple yes-or-no limit. A shallow pool can still process a trade, but the output may be less attractive because the trade shifts its balance. The displayed estimate can also change before execution as pool balances and network fees move. THORChain’s Swap documentation lists both price slippage and outbound fees among swap costs; the inbound transaction also requires a fee on the source chain.

Before confirming, compare the quoted output with the minimum output you are willing to accept, and check that the destination address belongs to the intended chain. These are especially useful checks for a first cross-chain transaction: the source and destination assets may use different address formats, and the amount received is not simply the spot price multiplied by the input amount.

How is withdrawing liquidity different from swapping?

A liquidity withdrawal returns a provider’s share of a pool; it is not a way for a new swapper to claim the pool’s assets at a chosen price. THORChain’s Liquidity Providers documentation says that a provider receives their ownership percentage of the pool, including the assets earned, when withdrawing. That amount depends on the pool at withdrawal time, so it need not match the value originally deposited.

Withdrawals and swaps also affect the pool differently. A swap changes the asset ratio by exchanging one side for the other, with the slip-based fee tied to trade size. A withdrawal removes the provider’s proportional share of the pool and incurs an outbound network fee, as the documentation explains. For a provider, removing liquidity can make sense when they want to end that position; for someone who simply wants one asset exchanged for another, a swap is the relevant operation.

The closest alternatives answer different needs. A centralized exchange matches trades through an account-based service and may offer order-book pricing; a bridge transfers assets between networks, often through a bridge-specific design. THORChain’s pool route instead uses RUNE-linked liquidity and returns the requested native asset where supported. There is no universal winner: pool depth and fees matter for the swap, while custody model, available assets and the mechanics of the alternative matter for the other routes.

What should a first-time swapper watch next?

For most readers making a straightforward exchange, the swap is the direct choice; withdrawing liquidity only applies if they already own a provider position. The decision should turn on the quoted output and the route’s costs, not on the idea that a pool has a fixed amount of “capacity.” THORChain’s documents explain that fees vary with pool conditions and network gas, so the useful signals are the active status of both pools, their depth and balance, the estimated slip and fees, and the minimum output shown at confirmation.

• Check that both assets are supported and that the pools are active; THORChain’s Swappers documentation says swaps are available only after pools leave the bootstrap phase.
• Compare the quoted output and minimum received with the amount you expect after fees.
• Confirm the destination address and chain, and leave enough of the input asset for the source-chain transaction fee.
• After submission, follow the inbound transaction and the outbound transaction separately; they occur on different chains.

Those signals show whether the route remains practical as liquidity and network conditions change. A first swap is simplest when the user treats the quote as a pool-based execution estimate, understands that a withdrawal is a separate liquidity-provider action, and checks both legs of the cross-chain transfer.