TWAP is often used by unsophisticated counterparties as a proxy for reducing slippage. requires an end-time, which makes it the wrong tool when you are managing a limit price: if your limit isn't marketable during the window, the algorithm pauses and the order ends up partially or completely unfilled at the deadline. TimePace solves this by executing a fixed quantity per interval with no hard end-time obligation — so a temporarily unmarketable limit simply slows execution instead of stranding the order.
The problem with a deadline
A TWAP is defined by two things: a quantity and a window. It divides the quantity across that window and tries to finish by the end-time. That works when you mostly care about when the order completes.
But many institutional orders are governed by a price, not a clock. You set a limit — "don't pay above X" — and you are willing to wait for the market to come to you. Pair that intent with a TWAP and the mechanics fight you:
While the price sits outside your limit, the TWAP cannot fill, so it pauses.
The clock keeps running regardless.
At the end-time, the unfilled remainder is simply left over — the order is partially or completely unfilled, with no second chance.
The deadline that makes TWAP predictable is exactly what breaks it under a binding limit price.
How TimePace is different
TimePace is a time-paced algorithm that executes a fixed quantity per interval without committing to a hard end-time. It distributes execution evenly, like a TWAP, but it has no end-of-window catch-up obligation. The practical consequences:
If your limit is unmarketable for a stretch, TimePace waits without "spending" a deadline against you.
When the price returns inside your limit, it resumes its per-interval pace.
It will not fire a punishing IOC sweep just to hit a clock — there is no clock to hit.
This makes TimePace the natural fit for orders where the limit price is the real constraint and time is flexible.
TWAP vs. TimePace
Dimension | TWAP | TimePace |
|---|---|---|
Pacing | Quantity ÷ time window | Fixed quantity per interval |
End-time | Hard deadline | No hard end-time obligation |
Catch-up at deadline | IOC sweep to finish on time | None |
Unmarketable limit | Pauses, then leaves remainder unfilled at end-time | Pauses, then resumes when marketable |
Best when | Timing is the priority | A limit price is the priority |
A typical use case
Consider a desk liquidating a position over a day or two with a floor price it won't sell below. A TWAP would force a decision: either set the limit loose enough that the deadline doesn't strand the order (defeating the point of the limit), or accept that much of the order may not fill by the end-time. TimePace lets the desk hold its price discipline and simply trade at a steady pace whenever the market is inside the limit — common for token liquidations and treasury flows that are not time-critical.
Like the rest of the CoinRoutes suite, TimePace runs on the consolidated order book and smart order routing, so each clip still seeks the best net price across venues, and it can post passively rather than always crossing the spread.
When TWAP is still the right call
If you have a genuine deadline — an ETF flow, a settlement cutoff, a hedge that must be on by a certain time — the TWAP's end-time and catch-up behavior are features, not bugs. Use TWAP when finishing on time matters more than holding a price; use TimePace when holding the price matters more than finishing by a particular moment. (For passive execution that is allowed to get ahead of schedule with no catch-up, see Scheduled Post.)
Markets are dynamic and the right settings depend on real-time conditions. Algorithms support execution but do not guarantee outcomes. This article describes what the algorithm does and when to use it, not its proprietary internals.
Frequently asked questions
When should I use TimePace instead of TWAP? Use TimePace when you are managing a limit price and time is flexible. TWAP's hard end-time can leave the order unfilled if the limit is unmarketable during the window; TimePace has no such deadline, so it waits and resumes.
Does TimePace have an end-time at all? It paces a fixed quantity per interval without a hard end-time obligation. You are not committing to finishing by a specific deadline, so an unmarketable limit slows execution rather than stranding it.
What happens to a TWAP if my limit price isn't reached? The TWAP pauses while the limit is unmarketable, but the clock keeps running. At the end-time, any unfilled quantity is simply left over.
Is TimePace passive or aggressive? It can post passively via the platform's posting engine, seeking maker fills and routing each clip for the best net price, rather than always crossing the spread.
Working an order around a limit price? Book a demo to see how TimePace keeps it disciplined.
Related reading: Why CoinRoutes' TWAP Outperforms a Basic TWAP · Scheduled Post vs TWAP · POV vs TWAP · Crypto Execution Algorithms Explained
Request a demo
Find out how CoinRoutes can simplify the way you interact with digital asset markets.
