Why Choose Streaming Swaps for a Large Cross-Chain Order?

Choose a streaming swap when your order is large relative to the route’s pool depth and you can accept slower, market-rate execution; choose a regular swap when completion time and a firm minimum output matter more. The key comparison is not “one transaction or many” at the wallet: streaming uses one inbound transaction but executes the trade internally in sub-swaps.

If your quote on thor swap offers a price-optimized route, compare its estimated output and completion time with the regular route before choosing. The interface can aggregate routes across protocols, so check which protocol will execute the selected leg and whether streaming applies to that route. The word “streaming” alone does not guarantee the same execution behavior on every path.

What does a streaming swap change inside the trade?

A streaming swap divides the order into smaller swaps executed over time, then combines the proceeds into one outbound transaction. On THORChain, the pool’s slip-based fee rises with swap size relative to pool depth, so smaller sub-swaps can reduce the impact of any one execution. The inbound and final outbound transactions still incur their network costs.

The time between sub-swaps gives arbitrageurs an opportunity to bring the pool price back toward the external market. That can improve the average execution price, but it is not a guaranteed rebate: arbitrage may be slow, the market may move against the order, and every sub-swap still executes at the available market rate. The result depends on the pool and price path during the stream.

Consider two orders of the same dollar value. One is modest compared with the pool; streaming may add delay without meaningfully changing its average price. The other is large against a shallow pool; streaming can lower the per-swap price impact, though it remains exposed to movement in the asset’s external price while the remaining amount is unfilled.

When is streaming better than splitting the order yourself?

Streaming is generally the more practical choice when you want smaller internal executions without submitting and monitoring a series of separate wallet transactions. Manual splitting gives you control over each new decision: you can pause between orders, reassess the quote, or stop sending further funds after a market move. It also means paying for repeated inbound and outbound network transactions, depending on the route.

That distinction matters in a pair of contrasting cases. A trader moving a large amount through a deep pool may prefer one regular swap: the expected price-impact saving from staging could be too small to justify waiting. A trader crossing a shallow pool may prefer streaming because the large single execution would move the pool price more sharply, provided the trader accepts the longer exposure and cannot rely on a guaranteed final rate.

Don’t split mechanically into equal chunks based on a rule of thumb. Pool depth, expected price impact, network fees, route availability and the market’s volatility all affect the choice. Compare the quoted output after fees, then ask whether the possible improvement is large enough to compensate for both the time and the additional price risk.

What can go wrong while a stream is running?

The main trade-off is exposure to market movement during execution. A favorable move can improve the final result; an unfavorable move can erase the benefit of smaller sub-swaps. Streaming reduces the impact of order size on an individual pool execution, but it does not cap the loss from a changing market price.

Cancellation is a critical check: THORSwap’s documentation describes streaming V1 as non-cancelable once started. It also states that Layer 1 asset swaps, such as BTC or ETH swaps, are limited to a 24-hour streaming period under the documented setup. Confirm the options shown for your route before signing; don’t assume you can stop a stream, choose its duration, or set the number of sub-swaps yourself.

There is also a route risk. A quote may involve a protocol or leg that does not support streaming, or the best displayed route may change before submission. If the interface does not clearly identify price-optimized streaming for the route you intend to use, compare the regular quote and execution conditions instead of inferring that the order will be staged.

How should you choose between the routes?

Compare three things on the same asset pair and amount: estimated net output, expected completion time, and whether the execution can be stopped. The net output should account for protocol fees and network costs, not just the spot rate. For a large cross-chain order, compare the route’s expected slippage against the possible price movement while it runs.

If the order is large relative to the pool, the stream is supported, and you can tolerate waiting without cancellation, price-optimized execution may be worth the exposure. If the pool is deep, timing is important, or you need control over each execution, a regular swap or deliberately staged manual orders may fit better. Use thor swap to compare available route quotes, then choose according to the cost of delay and the amount of price risk you are willing to carry.

For a large order, choose streaming to reduce size-driven pool impact only when its time and market exposure cost less to you than executing the order at once.