Thorswap streaming swaps for reducing pool price impact

Thorswap streaming swaps divide an eligible trade into smaller internal swaps to reduce pool price impact. Smaller execution sizes can lower slip-based liquidity fees, while time between swaps gives arbitrage traders room to rebalance pools. The tradeoff is exposure to changing market prices during execution. One inbound transfer funds the stream, and the protocol consolidates successful output for delivery. Streaming can improve execution when the trade is large relative to pool depth, although the selected route and its settings determine the benefit.

Key takeaway: Smaller sub-swaps can reduce liquidity costs, while longer execution leaves the remaining input exposed to market movement.

One deposit and protocol-level execution

Streaming uses one funding transfer to support multiple internal executions through the selected liquidity protocol. Thorswap exposes this mechanism on eligible THORChain and Maya Protocol routes. Each protocol processes the funded amount in smaller portions. The source-chain deposit does not create a separate wallet transfer for every portion. Successful external-asset output normally leaves the protocol as a consolidated payout after the stream ends. A partial failure can also produce a separate refund in the source asset.

This arrangement distinguishes streaming from manually submitting many independent swaps. Manual splitting repeats the funding and settlement transactions for each trade, adding network costs each time. Protocol-level splitting keeps those transfers separate from its internal execution count. Streaming support belongs to the selected protocol route; an aggregator can also return quotes that use different execution mechanisms.

Price-oriented pacing and rapid execution

Execution speed depends on the stream’s scheduling method, which can prioritize spacing between swaps or processing them as quickly as protocol rules allow. Time-spaced streaming creates gaps that can accommodate pool-rebalancing trades. Rapid streaming seeks faster execution with internal splitting. A fast quote can therefore still use streaming. The execution settings distinguish time-spaced swaps, rapid processing and a single swap.

View image file

In THORChain’s advanced queue, rapid streaming uses an interval of 0. Protocol iteration limits and pool-direction safeguards constrain actual processing. The same-direction market-swap safeguard can defer further execution to another block. A zero interval therefore does not promise immediate settlement or multiple fills of the same stream within every block.

Execution settings and order behavior

Streaming settings define count, timing and price conditions for the selected protocol. Available Thorswap controls depend on the selected route.

Sub-swap count

The quantity parameter specifies how many internal swaps the protocol should attempt. Supported automatic sizing derives the count from the funded amount and pool conditions. Minimum liquidity fees and permitted stream length constrain the count. Increasing it indefinitely does not create unlimited savings.

Timing and price conditions

The order type determines what a timing parameter means and how execution handles an unfavorable price. THORChain distinguishes market streams from queued limit streams.

Market streams

A THORChain market stream with a positive interval spaces executions by protocol blocks. It attempts execution at available pool prices, subject to any encoded trade limit. Failure to satisfy that limit can leave part of the source amount unswapped. The protocol settles that remainder through its refund path.

Queued limit streams

THORChain’s advanced queue supports streaming limit swaps when its operating mode enables them. Their timing field can specify an order lifetime rather than spacing between sub-swaps. Expiration ends the waiting period and triggers settlement of successful fills alongside a refund of unfilled input. The original creator can cancel an eligible queued limit swap through a separate protocol instruction. This capability does not imply that Thorswap offers a corresponding control for every route.

Does splitting a trade fix its exchange rate?

Splitting a trade reduces each execution’s pressure on liquidity, while the exchange rate can still change throughout the stream. Price impact is the movement that a swap causes within a pool. Slippage also includes differences between the quote and execution, including wider market movement. A longer stream spreads execution across different pool states. Later portions can encounter more favorable or less favorable prices, even when their individual liquidity fees are smaller.

THORChain applies an encoded trade limit to each sub-swap in a protected market stream. That limit does not lock the initial quote or ensure that every portion converts. Successfully swapped amounts remain converted if later portions fail. Receiving some destination assets and some refunded source assets can therefore be the correct settlement of one protected stream.

Fees that splitting does not remove

Streaming targets the liquidity fee associated with consuming pool depth; it still incurs source-chain funding costs and destination-chain delivery charges. Any applicable Thorswap service charge also remains part of the selected quote. THORChain deducts its outbound charge from delivered swap output. The applicable liquidity-fee floor can vary by asset class, trading pair and eligible affiliate configuration.

Streaming duration and wallet delivery

Streaming duration covers internal execution, while wallet delivery also depends on source-chain confirmation and the protocol’s outbound processing. THORChain quotes distinguish the estimated streaming period from total estimated swap time. An outbound security delay can remain relevant after the final sub-swap. Some streaming time can overlap that delay, so simply adding every displayed duration can overstate the overall estimate.

Network configuration also bounds permissible market-stream length. Queued limit streams have a separate order lifetime, which bounds how long unfilled input can remain eligible for execution. That lifetime does not guarantee when the recipient will receive assets. Trading halts can prevent further execution, while a signing halt can leave an outbound transfer queued. A completed stream and a confirmed destination transfer describe different states.

Protocol vault exposure during a stream

External assets remain in protocol vaults while a funded stream awaits execution and settlement. Thorswap presents the swap, while the underlying protocol controls vault transactions. Smaller sub-swaps address execution pricing; they do not eliminate vault or signing risk. THORChain halted after a vault exploit on May 15, 2026, then restarted on June 22, 2026. That incident affected protocol availability and settlement, separately from the liquidity benefit that streaming seeks.

Pool conditions that change the benefit

Streaming offers the strongest price-impact rationale when the trade consumes a meaningful share of available pool liquidity. Pool depth needs comparison with the input amount. When a route crosses more than one pool, the less liquid leg can constrain execution. Arbitrage also depends on external liquidity and the cost of rebalancing trades. Extra time helps only when those trades can improve the pool states that subsequent sub-swaps encounter.

A small swap in deep liquidity may already approach the applicable minimum liquidity fee. Further splitting then offers little fee improvement, although longer execution still exposes the remaining input to price movement. The tradeoff changes again when volatility rises or trading availability changes. A deeper pool or a smaller input can make additional waiting less useful.