# Claimed versus measured: every clamp takes the measurement

> Canonical: https://blazephoenix.xyz/learn/claimed-versus-measured/
> License: CC BY-NC-ND 4.0 (attribution + link) · © 2026 BlazePhoenix
> Updated: 2026-11-16

The chain decides. Each of the router's floors and caps is a minimum or a maximum between a claimed value and a measured one, and the operator is chosen per limit so that the measured value binds: a maximum on a floor, a minimum on a capacity cap. The direction changes, the winner does not.

## The short answer

The chain decides. The router's floors and caps are each a minimum or a maximum between what was claimed and what was measured, and the operator is chosen per limit so that the measured value is the one that binds. On a floor that operator is a maximum; on a capacity cap it is a minimum. The direction changes, the winner does not.

## Why the operator is not always min

On a floor, min(claimed, measured) with a deflated claim returns the deflated figure and relaxes the floor. That is the attack a maximum closes. On a promise (how much a pool can deliver), the opposite holds: a claim above what the pool has ever held must be cut down to the measurement. So the same principle needs a maximum in one place and a minimum in the other.

## Four clamps, side by side



## The capacity clamp, in one sentence

The single-tick concentrated-liquidity formula models the current tick's liquidity as if it spanned every price, so on a thin pool it can promise far more than the pool holds (117 times more in one observed case). A concentrated leg on a pool-shaped venue is therefore clamped to 30 % of the pool's measured real output-token balance. The clamp does not reach V4 legs, where the singleton holds every pool's tokens in one balance; the floor is that leg's bound.

## The quote margin, read as a formula

In the Quoter, n is the leg count and a the number of constant-product legs priced on an assumed fee. The terms are BASE_SAFETY_BPS 0, PER_LEG_SAFETY 1, ASSUMED_FEE_SAFETY 5, under one shared cap SAFETY_CAP_BPS of 10. A buffer without a ceiling stops being a buffer and becomes a floor, so the cap is part of the rule.

```
s = min( max(0, n - 2) + 5a , 10 )  basis points
```

## Check it yourself



**Verify it yourself:** In a clean checkout of Blaze-Phoenix-Dex at 969bcc6: sed -n 400,408p src/BlazePhoenixCore.sol; sed -n 146,148p src/BlazePhoenixQuoter.sol; sed -n 172p src/BlazePhoenixQuoter.sol; git grep -n "MAX_CONC_DRAIN_BPS". Whitepaper 2.4: sections 10 (capacity clamp), 11.3 (floors) and 12 (Quoter margins).

Related: https://blazephoenix.xyz/learn/capacity-clamp/ · https://blazephoenix.xyz/learn/iron-floor/ · https://blazephoenix.xyz/learn/monotonicity-against-the-caller/ · https://blazephoenix.xyz/learn/the-measurement-law/
