How a VWAP order works on Stacked Markets

VWAP — volume-weighted average price — is both a benchmark and an execution strategy. Instead of hitting the market with a single large order, you slice it into smaller child orders timed to match natural volume patterns. The result is a filled position whose average entry approximates the market's VWAP over the window, with meaningfully less market impact. This article covers the mechanics end to end.

What VWAP means

VWAP is the ratio of total notional value traded to total volume traded over a given period. For each trade, multiply price by volume, sum those products, then divide by total volume. The result is a single price that reflects where most actual trading activity occurred — weighted by size.

Traders use VWAP two ways. First, as a benchmark: did you buy below VWAP or above it? Buying below VWAP means you got better-than-average execution for the period. Second, as an execution strategy: slice a large parent order into smaller child orders timed to match natural volume patterns, aiming to fill the full position at or near the VWAP benchmark. The second use is the more technically demanding one — and what this article covers.

Why VWAP matters on a CLOB

A central limit order book matches buyers and sellers at discrete price levels. Every resting order has a price and a size. Send a large market order and it eats through multiple levels in sequence, pushing your fill price progressively worse as it consumes available liquidity. That slippage is not a fee — it is a structural cost that scales with order size relative to available depth.

On an AMM, there is no order book to read, no depth to parse, and no meaningful VWAP benchmark to target. The CLOB structure is a prerequisite. Hyperliquid's on-chain CLOB provides the transparent, verifiable depth that makes VWAP-style execution meaningful for orders routed through Stacked Markets.

How VWAP execution works algorithmically

Slicing and volume weighting

A VWAP algorithm starts with a parent order: total size, direction, and a time window. It divides that window into intervals — typically one-minute or five-minute buckets — and calculates a target participation rate for each interval based on expected volume.

At each interval, the algorithm sends a child order sized to match the target participation rate. If the market moves against you, some implementations pause or reduce child order size to avoid chasing. Others hold to schedule regardless. That design choice reflects a trade-off between benchmark tracking and adverse selection risk.

VWAP vs TWAP: the key difference

TWAP distributes equal-sized slices evenly across the window, regardless of volume. Easier to implement, fully predictable. The weakness is that it ignores liquidity — equal-sized slices sent into thin intervals carry higher market impact per unit than slices sent into deep ones. VWAP solves that by concentrating size where liquidity is naturally available.

How the on-chain CLOB enables VWAP-style execution

Stacked Markets routes all orders through Hyperliquid's on-chain CLOB. That routing has specific properties that matter for VWAP execution.

Practical use cases on Stacked Markets

• 1
  Building a large position without moving the market If current book depth does not support a single-fill entry at acceptable slippage, a VWAP schedule lets you accumulate over hours rather than minutes. You participate alongside natural volume rather than announcing your full size at once.
• 2
  Exiting a position during a trending move Closing a large position into a running move requires care. Dumping full size into a rally or selloff can accelerate the reversal against you. A VWAP schedule distributes your exit across the move, capturing more of the trend while reducing impact.
• 3
  Benchmarking your own execution quality Calculate the session VWAP after the fact and compare it to your average fill. Consistent fills below VWAP on buys and above VWAP on sells is a measurable edge. Stacked Markets' on-chain fill data makes that calculation straightforward.
• 4
  Reducing adverse selection on thinner markets Smaller perp markets on Hyperliquid's CLOB can have meaningful spread and limited top-of-book depth. Spreading a position entry across multiple intervals, each sized to a fraction of available depth, reduces the probability that a single large order triggers a cascade of cancellations.

Risks and limitations

VWAP execution is not free of risk. The failure modes matter as much as the mechanics.

• Forecast
  Volume forecast error. If the historical volume profile does not match actual intraday volume, child orders will be mis-timed. You may concentrate size in thin intervals and underparticipate in deep ones — producing worse execution than a simple TWAP would have.
• Trend
  Trend risk during execution. VWAP assumes indifference to short-term price movement within the window. If the market moves strongly against your direction during the schedule, later child orders fill at progressively worse prices. VWAP is not a hedge against directional risk during execution.
• Front-run
  Predictability and front-running. A mechanical schedule is readable. Sophisticated participants who detect a pattern of same-size, same-interval orders can trade ahead of it. Introducing randomness in child order size and timing reduces this risk but complicates benchmark tracking.
• Cancels
  Cancellation and partial fills. Child orders routed as IOC slippage-bounded limits cancel if they cannot fill within the bound. In fast-moving markets, this can leave your schedule behind. The remaining size must be addressed separately.
• Execution
  Custody and execution risk are yours. Stacked Markets holds nothing. The risk management decisions around schedule design, slippage bounds, and timing belong entirely to you. There is no counterparty absorbing your execution errors.

The non-custodial angle: who signs each child order

This is where Stacked Markets differs structurally from any CEX-based VWAP tool.

FAQs