For the complete documentation index, see llms.txt. This page is also available as Markdown.

Batching Solver

Turbine has a built-in solver that settles orders in batches.

Batches over Turbine + Ethereum Liquidity

Every batch includes:

  • Turbine Orders: Turbine orders that track the market.

  • Turbine Pools: Turbine pools that track the market.

  • On-chain liquidity: All AMM pools and PMM quotes from Tycho.

Limit Order vs. Spread Order Batching

Limit Order Batching: In limit order markets, you only match if an opposite trade arrives before the market moves, which rarely happens. So you usually get stuck or overpay; only when the market is less volatile do you settle at market rate.

Limit Order Batching -> Few P2P Trades

Spread Order Batching: In Turbine, orders and pools follow the market price. Orders match peer-to-peer, no matter where the market moves. The longer an order stays in Turbine, the higher the chance of settling peer-to-peer. As a result, CoWs are the default, and orders rarely get stuck. Worst case, you pay market rate (AMM router price).

Spread Order Batching -> Many P2P Trades
Limit Order Markets
Spread Order Market

⛔️ Stuck Orders

A lot 😔

Rarely ☺️

🤕 Paid Too Much

A lot 😔

Rarely ☺️

🤝 P2P Trade

Rarely 😔

A lot ☺️

Market Rate

Rarely 😔

Sometimes

Fair Settlement

In Turbine, all orders for the same pair in the same batch clear at the same uniform clearing price.

Default = Market Rate

Because Turbine includes all on-chain liquidity (via Fynd), the worst price you settle at is what you'd get from optimally routing across all on-chain liquidity.

Peer-to-peer trades and Turbine LP pools give you the surplus above the AMM routes.

Last updated

Was this helpful?