Virtual reserves do not mean tokens are available without limit

Virtual reserves describe the local pricing curve. They are not a claim that an equal quantity of tokens physically sits in the position or can be withdrawn by one trade before the range ends.

A numerical position

Use a hypothetical fee-free position with liquidity parameter L = 1,000, current price P = 1 and a price range from 0.81 to 1.21. Treat both token units consistently and let P mean token1 per token0.

At P = 1, the virtual reserve values are L / sqrt(P) = 1,000 token0 and L × sqrt(P) = 1,000 token1. The actual position holdings within these bounds are different:

Real token0 = 1,000 × (1 − 1 / 1.1) ≈ 90.909091

Real token1 = 1,000 × (1 − 0.9) = 100

The formulas and the distinction between real holdings and virtual liquidity are described in Uniswap's liquidity math primer. The values here are invented for illustration.

The boundary limits the local calculation

Adding token0 moves price downward. Reaching the lower price bound requires approximately 1,000 × (1 / 0.9 − 1) = 111.111111 token0 and releases the 100 real token1 in this position.

You cannot keep applying this position's 1,000-by-1,000 virtual curve indefinitely after that boundary. Additional execution requires the liquidity active in subsequent ranges, if any, and remains subject to the transaction's limits.

Use the right reserve concept

Virtual values help calculate local movement efficiently. Real token holdings help describe inventory. Total pool balances combine many positions and possibly other accounting amounts. A liquidity report should name which one it shows.

Do not add virtual reserves across unrelated ranges and present the result as deposited token value. Nor should you conclude a pool is underfunded merely because its real holdings are smaller than its virtual numbers. The distinction is part of concentrated-liquidity pricing, not evidence of a missing reserve.