Jump to content
The Coin Wire

Crypto moves, protocols and policy

TWAP and VWAP Order Pacing in Crypto

TWAP vs VWAP order difference in crypto: TWAP sells equal slices over time; VWAP varies slice size with expected market volume to track a volume-weighted benchmark.

By The Coin Wire Editorial4 min read

TWAP and VWAP Order Pacing in Crypto

A TWAP order splits a trade into equal pieces over time, while a VWAP order sizes pieces to match expected market volume. That difference sets the pace: TWAP follows the clock; VWAP trades more when the market is expected to be busier.

How does TWAP pacing differ from VWAP?

TWAP execution trades equal amounts at each interval. The schedule is predictable because the clock determines when each slice is due, regardless of how much trading is happening in the market.

VWAP execution weights slices by a forecast of the market’s volume profile. It aims to trade in step with expected activity, putting more of the order through in busy periods and less in quiet ones. Its pacing can therefore change from one interval to another.

Say you need to sell 100 tokens over 10 hours. A simple TWAP schedule sells 10 tokens per hour. A VWAP schedule might sell more in hours expected to have higher volume and less in quieter hours; the precise quantities depend on the forecast, not just the duration.

The two schedules also measure execution against different benchmarks. TWAP is associated with the average price across a period of time. VWAP is associated with the average price weighted by trading volume across that period. The schedule is designed around its benchmark, but the benchmark itself does not guarantee a particular execution price.

What inputs does each order need?

TWAP needs an order size and a time schedule. Once those are set, equal slices can be calculated without predicting when the market will be active. That simplicity makes the plan easier to understand and gives the trader a fixed pace to monitor.

VWAP needs a forecast of how market volume will be distributed over the trade’s duration, as well as the order size and timing. The schedule depends on that expected volume profile. If actual activity differs from the forecast, the planned pace may no longer match the market’s realized volume pattern.

This is the central trade-off: TWAP gives up volume-sensitive pacing for a more direct schedule, while VWAP uses an estimate to follow liquidity more closely. A trader choosing VWAP must have a usable forecast and a way to execute the varying slices. The extra input makes its schedule less fixed than TWAP’s.

Can a DEX use TWAP or VWAP pacing?

On-chain availability depends on what the exchange contract can schedule. Fraxswap is a decentralized exchange and automated market maker with a time-weighted market maker embedded in the pool. That changes the execution setup for a trader placing a long-term order: Fraxswap can spread it through the pool over the chosen duration instead of requiring the trader to submit every slice by hand.

Fraxswap TWAMM sells a long-term order at a constant rate per block, which follows a TWAP-style schedule. Its pacing does not speed up or slow down as trading volume changes. The pool contract does not have a forecast of future volume with which to build a VWAP schedule, so this embedded mechanism follows time rather than a predicted volume curve.

The distinction matters when taking a strategy from a trading desk to a pool. A VWAP schedule requires an estimate of how volume will arrive; a fixed-rate on-chain order can instead follow elapsed time. Paradigm’s 2021 “TWAMM” paper by White, Robinson and Adams describes time-weighted execution embedded in an automated market maker. Fraxswap documentation describes long-term orders as executing evenly over their chosen duration.

Who should choose a TWAP order or a VWAP order?

Choose a TWAP order when a simple, fixed pace is the priority. Equal slices make the schedule straightforward to plan, and a DEX with long-term order support can run that pace within the pool. For a trader who wants to spread a trade over time without relying on a volume forecast, the clock-based rule is the clearer fit.

Choose a VWAP order when trading in a market with known volume patterns and tools that can use those forecasts. Its changing slice sizes follow expected activity, so more of the order is scheduled for busier periods. The trade-off is dependence on the quality of the forecast and on execution tools that can implement the varying pace.

Before choosing, check what determines each slice: the interval alone for TWAP, or the expected volume profile for VWAP. On a DEX, check whether the pool supports the schedule you want. For a long-term order on Fraxswap, the relevant signal is the chosen duration and the constant per-block pace; a volume-responsive schedule requires volume estimates and execution support beyond that fixed TWAP pattern.