Concentrated liquidity, explained

The problem it solves

A constant product pool spreads its capital across every conceivable price, from nearly zero to nearly infinite. That is elegant and it is extraordinarily wasteful, because almost none of that range will ever be visited. Capital sits reserved for prices the token will never reach.

Concentrated liquidity fixes the waste. A provider says, in effect, that they expect trading to happen between two prices and place their capital only there. Inside that band the pool is far deeper than the same money would produce if spread thin; outside it, that provider is simply absent.

The result is that the same capital supports much more trading, which is genuinely better for everyone when the ranges are set sensibly. It also introduces a failure mode that plain pools do not have, and that failure mode is what this page is really about.

How ranges actually work

Each position has a lower and an upper bound. The pool's overall depth at any given price is the sum of every position whose range covers that price.

Three consequences follow, and all three matter more than they sound.

• Depth is not uniform. It varies by price, and can change sharply between one level and the next as ranges begin and end.
• Positions go inactive silently. When price moves past a bound, that capital stops participating. Nothing is announced, nothing errors, the money is simply not available where trading is happening.
• The composition shifts. A position that price has moved through ends up holding entirely one side of the pair rather than a mix.

Nobody is notified when any of this happens. A provider who set a range at launch and stopped paying attention may be contributing nothing today while their capital is still nominally in the pool, counted in every total anyone reads.

Why a well funded pool can be empty

This is the practical core of it, and it explains a category of confusing results.

Suppose a token launched at some price and providers placed ranges around it. Over a few weeks the price drifts well below those bands. Every one of those positions is now inactive at the current price. The pool still reports a substantial total, because the capital is still there, and anyone trading now is executing against whatever thin liquidity happens to cover the current level.

The symptoms are distinctive once you know to look for them. Swaps that were nearly free start moving the price noticeably. Slippage failures appear on a configuration that worked last week. The chart develops steps. Nothing in your setup changed; the market moved out from under the liquidity.

This is also why comparing two pools by their headline figures is close to meaningless. One with a smaller total but ranges covering the current price can be far deeper where it counts than a larger one whose ranges have drifted. The Orca guide covers what this does to a campaign in practice.

What to read instead of TVL

1. Simulate a realistic buy. Any aggregator quotes it and reports impact without executing.
2. Simulate the sell. Ranges are frequently asymmetric around the current price, so the two directions can differ substantially.
3. Try a larger size. If impact grows smoothly, the range is well populated. If it jumps sharply, you are crossing out of it.
4. Repeat before each campaign. A reading from last week describes last week, and ranges drift without anyone doing anything.

Step three is the one specific to this pool type and it is the most informative. On a plain pool, impact grows predictably with size. On a concentrated pool, a sudden jump between two similar order sizes tells you exactly where the liquidity ends.

What it means when you trade

For anyone routing activity, concentrated pools are excellent or awkward depending on one variable, and the variable is not under your control.

When the price sits inside well populated ranges, execution is genuinely better than a plain pool of the same size. Small swaps cost almost nothing in impact, slippage failures are rare, and the chart contribution is smooth. This is the case the design was built for.

When it does not, everything reverses, and the failure is abrupt rather than gradual. That abruptness is the part worth planning around: a campaign that ran cleanly yesterday can produce steps and failures today with identical settings.

Two defences work. Keep swaps small enough that a single order does not consume a whole range, which the impact explainer covers as a general principle that applies with extra force here. And spread across every venue holding the token, so that one pool drifting out of range degrades part of a campaign rather than all of it.

There is a timing pattern worth knowing because it produces the worst version of this. Ranges are most often set at launch, when the price is at its least settled, and by whoever seeded the pool in a hurry. Price then does what new tokens do, which is move a long way in the first days. The result is that a large share of tokens have their liquidity positioned around a price that stopped being relevant within a week of launch, and nobody involved has looked at it since. If you inherited a pool or set one up months ago and have not checked, assume this has happened until a simulated trade tells you otherwise.

If you are the one providing liquidity

Token teams frequently seed their own pool and choose a concentrated position because it is more capital efficient. That is a real advantage with a real obligation attached.

A range is a bet on where trading will happen. When the price leaves it, your capital stops working and your token's effective depth collapses, which is the thing that decides whether a visitor arriving from any campaign or announcement can actually buy. Nobody tells you this has happened. You find out from a community member describing bad fills, or you do not find out at all.

The honest recommendation for a team without someone monitoring positions is a wider range than feels efficient, or a plain pool that never needs attention. Capital efficiency is worth less than reliability when the failure mode is invisible and lands on your buyers rather than on you. Whichever you choose, the test in the liquidity guide is worth running on your own token periodically, because it measures the experience a real buyer will have rather than the number on your dashboard.