Connect ›
Cover: The two-tier capacity clamp: refusing trades a pool cannot absorb

The two-tier capacity clamp: refusing trades a pool cannot absorb

Why BlazePhoenix caps per-pool trade size against real holdings — with the measured case of a 117x phantom quote and a 27% loss that the clamp turns into a refusal.

BlazePhoenix Engineering · updated 2026-10-05 · data through 2026-10-11 · 6 min · written from the deployed bytecode

By Mitra (@Sigmacrit) — anonymous developer of the BlazePhoenix protocol. The code is the résumé.

Abstract in 15 languages · resumo · resumen · 摘要 · 要旨 · ملخص

English — Even honest pools have finite capacity. The two-tier clamp caps each pool's share against its real holdings and refuses trades the candidate set cannot absorb — no_route beats a confident disaster.

Português — Mesmo pools honestos têm capacidade finita. O clamp de dois níveis limita a fatia de cada pool ao que ele realmente detém e recusa trades que o conjunto não absorve — no_route é melhor que um desastre confiante.

Español — Incluso los pools honestos tienen capacidad finita. La pinza de dos niveles limita la parte de cada pool a sus tenencias reales y rechaza operaciones que el conjunto no puede absorber: no_route es mejor que un desastre seguro.

Français — Même un pool honnête a une capacité finie. Le double verrou plafonne la part de chaque pool selon ses avoirs réels et refuse les ordres que l'ensemble ne peut absorber — no_route vaut mieux qu'un désastre assuré.

Deutsch — Auch ehrliche Pools haben endliche Kapazität. Die zweistufige Klammer begrenzt jeden Pool auf seine realen Bestände und verweigert Trades, die das Kandidatenset nicht tragen kann — no_route schlägt ein selbstsicheres Desaster.

Русский — Даже честные пулы имеют конечную ёмкость. Двухуровневый ограничитель урезает долю каждого пула по его реальным запасам и отклоняет сделки, которые набор не может поглотить: no_route лучше уверенной катастрофы.

Türkçe — Dürüst havuzların bile kapasitesi sınırlıdır. İki kademeli kelepçe her havuzun payını gerçek varlıklarıyla sınırlar ve aday kümenin taşıyamayacağı işlemleri reddeder — no_route, emin bir felaketten iyidir.

العربية — حتى المجمّعات النزيهة ذات سعة محدودة. المشبك ثنائي المستوى يحدّ حصة كل مجمّع بما يملكه فعلاً ويرفض الصفقات التي لا تستوعبها المجموعة — إن no_route أفضل من كارثة واثقة.

हिन्दी — ईमानदार पूल की भी क्षमता सीमित होती है। दो-स्तरीय क्लैंप हर पूल का हिस्सा उसकी वास्तविक होल्डिंग तक सीमित करता है और वे ट्रेड ठुकरा देता है जिन्हें सेट सह नहीं सकता — आत्मविश्वासी आपदा से no_route बेहतर है।

日本語 — 誠実なプールでも容量は有限です。二段クランプは各プールの取り分を実保有量で制限し、候補全体で吸収できない取引を拒否します。自信満々の惨事よりno_routeの方が良いのです。

中文 — 即使诚实的池容量也有限。双层钳制将每个池的份额限制在其真实持仓内,并拒绝候选集无法承受的交易——no_route 胜过一场自信的灾难。

한국어 — 정직한 풀도 용량은 유한합니다. 2단 클램프는 각 풀의 몫을 실제 보유량으로 제한하고, 후보군이 감당 못 할 거래는 거부합니다. 자신만만한 재앙보다 no_route가 낫습니다.

Bahasa Indonesia — Pool yang jujur pun kapasitasnya terbatas. Penjepit dua tingkat membatasi porsi tiap pool sesuai kepemilikan nyatanya dan menolak transaksi yang tak dapat diserap — no_route lebih baik daripada bencana yang percaya diri.

বাংলা — সৎ পুলেরও ধারণক্ষমতা সীমিত। দ্বি-স্তরীয় ক্ল্যাম্প প্রতিটি পুলের অংশ তার প্রকৃত হোল্ডিংয়ে সীমাবদ্ধ রাখে এবং যে ট্রেড সেটটি সামলাতে পারে না তা প্রত্যাখ্যান করে — আত্মবিশ্বাসী বিপর্যয়ের চেয়ে no_route ভালো।

Filipino — Kahit tapat na pool ay may hangganan ang kapasidad. Nililimitahan ng two-tier clamp ang bahagi ng bawat pool ayon sa totoong hawak nito at tinatanggihan ang trade na hindi kaya ng set — mas mabuti ang no_route kaysa kumpiyansang sakuna.

Even an honest pool has finite capacity. Push 10,000 tokens into a pool that holds 6,200 of the counter-asset and the math still "works" — the price just collapses under you. In our measured replay, routing 89% of a 10,000-unit trade into a pool holding 6,200 produced a 27% realized loss and burned about 7 million gas across the retry cascade. Nothing reverted; the user simply got destroyed by slippage that the naive route accepted.

The pathological version is worse: one thin pool quoted 117x the honest output for a size it could never absorb — a phantom quote that a volume-maximizing router would chase off a cliff.

Two tiers of refusal

Tier one caps any single pool's share of a route at what its real holdings can absorb without pathological impact (the deployed Solver caps concentration drain at 30% of a pool's measured balance). Tier two clamps the aggregate: if the candidate set's combined real capacity cannot carry the trade at acceptable impact, the plan is refused — previewPlan returns no route rather than a bad one.

A refusal is a feature. The worst quote is not a slightly-worse price; it is a confidently-wrong plan. BlazePhoenix would rather return no_route than manufacture an executable disaster.

The clamp, as an equation

Let B be a pool's real held balance of the output token (balanceOf, not reserves), q the output the naive route wants from it, and s the input committed to that leg. Tier one caps the promise at 30% of B; tier two — triggered only when the promise q exceeds the pool's WHOLE holdings — cuts the committed input s in the promise's own ratio and cascades the freed capital to the next leg:

cap=0.30B,keep=s·capqwhenq>B
Original to BlazePhoenix (Solver two-tier clamp, MAX_CONC_DRAIN_BPS = 3000). The vector solved: a 117x phantom quote (494k promised from a 4.2k book) becomes a refusal, and a 27%-loss cascade becomes a small honest fill plus a refund.

Do not trust this page — reproduce it

Every claim above is checkable against the chain. Start here:

Prepare https://blazephoenix.xyz/api/quote/prepare?chain=base&in=WETH&out=<thin-token>&amountIn=<huge>, run the returned eth_call on your node and POST it to /api/quote/decode: the output is clamped to what the pools hold, or no_route — never a fantasy quote
Cite this article

Licensed CC BY 4.0 — quote, translate and reuse freely, including commercially, with attribution and a link. Copy a ready-made citation:

BlazePhoenix (2026). The two-tier capacity clamp: refusing trades a pool cannot absorb. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/capacity-clamp
@misc{blazephoenix_capacity_clamp,
  title  = {The two-tier capacity clamp: refusing trades a pool cannot absorb},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/capacity-clamp},
  note   = {Accessed: reproduce the claim with the command above}
}

Writing an answer, a wiki entry or a paper? The claim above is reproducible against the chain before you quote it — which is the only sound basis for citing a technical source at all.

Contracts are verified on every chain we deploy to — addresses in the protocol manifest. Deeper formal treatment: the whitepaper (PDF).

Related engineering

Next in Invariants & security · 1 / 17
The believability band: a manipulation-robust price without an oracle ›Why BlazePhoenix defends pricing with a band around a capital-anchored reference instead of trusting a single quote — resistant to one poisoned pool. The band shipped at ±4% and was widened to ±5% against live venue data — because a tolerance is a measurement, not a decoration.7 min