Batched Execution
DEX execution mode that clears swaps in a batch at a single price, rather than transaction-by-transaction. Defends against sandwiches and front-running. CoW Swap on Ethereum is the canonical example; on TON it's still research-stage.
Aliases: batched execution, batch auction, batched dex
Batched Execution is a DEX model that collects swaps over a window (say, 6 seconds) and executes all of them at a single clearing price derived from the batch supply/demand. The goal is to kill MEV attacks that rely on ordering individual transactions.
Why
- Inside one batch there is no “ordering” between swaps — everyone fills at the same price.
- Sandwich attacks become impossible: no “before” and “after” the victim.
- Front-running loses its point — your transaction and the attacker’s would clear at the same price.
Where it runs (outside TON)
- CoW Swap on Ethereum — the original production batched DEX.
- Anoma — an experimental chain with native batching.
On TON as of May 2026
No production batched DEX on TON. The async-message architecture already weakens classical sandwiches, but it doesn’t kill front-running. Prototypes and discussions exist, but the large DEXs (STON.fi, DeDust) stay on classical AMM models with tick-by-tick execution.
Trade-offs
- 5–10 second latency to execution → unsuitable for HFT-style arbitrage.
- Harder to integrate into route aggregators.
See MEV on TON for the longer treatment.