Concentrated Liquidity Makes Every Range an Execution Bet

Uniswap v3’s concentrated-liquidity design changed a market-making range from a risk limit into the exact interval where orders can consume an LP’s inventory. When v3 reached Ethereum on May 5, 2021, its tick-indexed pool replaced v2’s zero-to-infinity allocation with provider-defined bands. The responsible component is the core swap loop, not the router or interface: it reads the current square-root price and active liquidity, spends input until the next initialized tick, applies that tick’s liquidity change, then continues. One atomic order can therefore cross several different depths.

What happens to one order inside a concentrated range?

The same capital produces a better fill inside a narrow band because it represents more virtual liquidity there. Consider one isolated position, a starting price of $100, $10,000 of capital and no fee. Using the v3 reserve equations, placing that capital from $90 to $110 creates about 20.4 times the active liquidity of a full-range constant-product position.

Now send $1,000 of quote token into each pool to buy the base token. The full-range pool begins with 50 base tokens and $5,000 quote; the order receives 8.33 base at an average $120, leaving the marginal price at $144. The $90–$110 position returns about 9.90 base at an average $100.98, with the marginal price near $101.97. The order remains inside the band, so no boundary is crossed. Holding capital, starting price and fee treatment constant, concentration cuts this modeled average execution premium from 20% to about 0.98%.

Verified mechanism: this result follows from the position’s reserve curve and tick accounting. It is not a forecast that fee income will rise 20.4-fold; realized fees also depend on competing active liquidity, volume and time in range.

Why does a narrow market-making range fail?

A narrow range fails when price reaches a boundary, because that position’s active liquidity becomes zero. On the upward path in this example, swappers progressively buy its base token; at $110 the position holds only quote token and stops earning fees. A reversal reactivates it and can trade the inventory back, so a range order is not automatically a completed, one-way limit order.

This is the transfer hidden by the better fill. Traders get dense inventory near the midpoint; the LP bears faster inventory conversion, adverse selection and the cost of withdrawing and reminting around a new price. Aggregate pool value is a poor execution measure when much of it sits outside the current tick.

How should market makers choose range width?

Market makers should set width from expected price movement over their management horizon, then test whether fees can cover boundary and rebalance costs. A practical concentrated-liquidity reference can help frame the range decision, but the live tick map is what an order actually encounters.

• Uptime: estimate how often price would have remained inside the band over the intended holding period.
• Inventory: model the one-token position reached at either boundary, not only the balanced deposit.
• Competition: measure the LP’s share of active liquidity at each tick, where fees are allocated.
• Maintenance: subtract transaction costs, idle time and price movement during every rebalance.

Does concentrated liquidity improve execution?

Concentrated liquidity improves execution decisively while relevant ranges remain funded, but it makes depth conditional rather than permanent. The modeled $1,000 order shows the mechanism: roughly 9.90 base delivered instead of 8.33 with identical capital and fees excluded. The trade-off belongs mainly to the market maker, although a trader crossing an underfunded boundary can still meet an abrupt slippage cliff.

In a live pool, inspect the current tick, active liquidity and initialized ticks on both sides; then request quotes for increasing order sizes and note where marginal price jumps. That test reveals whether the displayed range is executable depth or merely capital waiting elsewhere.