Connect ›
Cover: Pool vitality: liveness as a measured property, not an assumption

Pool vitality: liveness as a measured property, not an assumption

Registries rot: pools die, liquidity migrates, incentives dry up. BlazePhoenix treats a pool's right to receive order flow as something continuously re-earned through measured vitality — real depth, real quoting, real recency.

Known formally as The Vitality Field Ψ in the BlazePhoenix whitepaper.

BlazePhoenix Engineering · updated 2026-07-17 · data through 2026-10-11 · 5 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 — Registries rot as liquidity migrates. BlazePhoenix treats slot occupancy as a lease: pools stay only while measured vitality — real depth, live quoting — keeps winning; decayed incumbents are evicted by measurement, not committee.

Português — Registos apodrecem quando a liquidez migra. A BlazePhoenix trata a ocupação de slot como arrendamento: pools ficam só enquanto a vitalidade medida — profundidade real, cotação viva — continua a vencer; incumbentes decaídos são despejados por medição, não por comité.

Español — Los registros se pudren cuando la liquidez migra. BlazePhoenix trata la ocupación de slots como un alquiler: los pools permanecen solo mientras su vitalidad medida — profundidad real, cotización viva — siga ganando; los titulares decaídos son desalojados por medición, no por comité.

Français — Les registres pourrissent quand la liquidité migre. BlazePhoenix traite l'occupation d'un slot comme un bail : un pool reste tant que sa vitalité mesurée — profondeur réelle, cotation vivante — continue de gagner ; les titulaires décrépits sont évincés par la mesure, pas par un comité.

Deutsch — Register verrotten, wenn Liquidität abwandert. BlazePhoenix behandelt Slot-Belegung als Miete: Pools bleiben nur, solange gemessene Vitalität — echte Tiefe, lebendiges Quoting — weiter gewinnt; verfallene Inhaber werden per Messung entfernt, nicht per Komitee.

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

Türkçe — Likidite göç ettikçe kayıtlar çürür. BlazePhoenix slot işgalini kira sayar: havuzlar ancak ölçülen canlılıkları — gerçek derinlik, canlı fiyatlama — kazandıkça kalır; çürüyen sakinleri komite değil ölçüm tahliye eder.

العربية — تتعفن السجلات حين تهاجر السيولة. تعامل BlazePhoenix شغل الخانة كعقد إيجار: تبقى المجمّعات ما دامت حيويتها المقاسة — عمق حقيقي وتسعير حي — تفوز؛ والمتهالكون يُخلَون بالقياس لا بلجنة.

हिन्दी — लिक्विडिटी के पलायन से रजिस्ट्रियाँ सड़ जाती हैं। BlazePhoenix स्लॉट को किराए की तरह देखता है: पूल तभी टिकते हैं जब मापी गई जीवंतता — वास्तविक गहराई, जीवित कोटिंग — जीतती रहे; क्षीण पूलों को समिति नहीं, माप बेदखल करता है।

日本語 — 流動性が移動すればレジストリは腐ります。BlazePhoenixはスロット占有をリースとして扱います。実際の深さと生きた見積もりという計測されたバイタリティが勝ち続ける限りだけプールは留まり、衰えた在位者は委員会ではなく計測によって追放されます。

中文 — 流动性迁移时,注册表就会腐烂。BlazePhoenix 将槽位占用视为租约:池只有在实测活力——真实深度、活跃报价——持续获胜时才能留下;衰败的在位者由测量驱逐,而非委员会。

한국어 — 유동성이 이동하면 레지스트리는 썩습니다. BlazePhoenix는 슬롯 점유를 임대로 취급합니다. 실측 활력—실제 깊이, 살아있는 견적—이 계속 이기는 동안만 풀이 남고, 쇠락한 기존 풀은 위원회가 아니라 측정이 퇴출합니다.

Bahasa Indonesia — Registri membusuk saat likuiditas bermigrasi. BlazePhoenix memperlakukan slot sebagai sewa: pool bertahan hanya selama vitalitas terukurnya — kedalaman nyata, kuotasi hidup — terus menang; petahana yang lapuk digusur oleh pengukuran, bukan komite.

বাংলা — তারল্য সরে গেলে রেজিস্ট্রি পচে যায়। BlazePhoenix স্লট দখলকে ভাড়া হিসেবে দেখে: পুল ততক্ষণই থাকে যতক্ষণ পরিমাপকৃত প্রাণশক্তি — প্রকৃত গভীরতা, জীবন্ত কোটিং — জিততে থাকে; ক্ষয়প্রাপ্তদের কমিটি নয়, পরিমাপই উচ্ছেদ করে।

Filipino — Nabubulok ang mga registry kapag lumipat ang liquidity. Itinuturing ng BlazePhoenix na upa ang pag-okupa ng slot: nananatili ang pool habang panalo ang sinusukat na sigla nito — totoong lalim, buhay na pag-quote; ang mga nanghinang nakaupo ay pinapaalis ng sukatan, hindi ng komite.

Every pool list in DeFi is a snapshot of a market that no longer exists. Liquidity migrates to new fee tiers, incentives end, LPs leave — and the registry still lists the corpse. Routing through dead pools is not a neutral mistake: stale candidates waste gas on every quote, dilute the median the router reasons over, and in the worst case become the manipulation surface described in the phantom-liquidity article.

BlazePhoenix treats slot occupancy as a lease, not a deed. A pool's vitality — its measured ability to actually serve flow — is what keeps it in the Hub's 16 slots: real held depth (balanceOf, not self-reported reserves), live quoting capability at relevant sizes, and the fitness contest that lets any challenger evict a decayed incumbent by beating it with a clear 25% margin.

The exact math (from the deployed bytecode)

Vitality is a swap-count EMA that decays on the wall clock: the stored swap count is shifted right once per 24,576 seconds of silence, so it halves roughly every 6.8 hours and reaches zero after about 9 days — a pool alive right now keeps its full count, a pool silent for a week is nearly weightless. The composite fitness is psi = vitality × 2^depthBucket, where the depth bucket is log10(depth/1e15) capped at 15, so each order of magnitude of real depth DOUBLES the weight. Pools touching a bridge token earn +25%; concentrated-liquidity kinds earn +5%.

Admission at a full 16-slot table requires the newcomer's projected fitness to beat the weakest incumbent by a strict 25% margin — and discovery itself is throttled by freshness: the full CREATE2 sweep is skipped only when at least 3 registered venues were active within the last 3,600 seconds, so hot pairs stay cheap to quote while quiet pairs always re-discover.

Death by measurement, not by committee

No governance vote decides a pool is dead. It simply stops winning measurements: its real balance no longer supports competitive quotes, a healthier pool demonstrates superior fitness, and the eviction rule does the rest. The registry stays alive the same way the quotes stay honest — by continuously re-deriving the truth from chain state instead of remembering yesterday's.

This is the quiet thesis across the whole system: solvency is re-computed per block, floors are re-derived per execution, candidates are re-measured per challenge. Nothing is trusted because it was once true.

The field, as an equation

Two quantities, one packed slot. Vitality v is the swap count right-shifted once per 24,576 seconds of silence — a halving roughly every 6.8 hours, zero after about 9 days. Composite fitness Ψ multiplies it by two raised to the depth bucket b (so each decade of real depth doubles the weight), with a +25% bridge bonus β and a +5% concentration bonus κ:

v=swaps≫⌊age16⌋,Ψ=v·2b(1+14β)(1+120κ),b=min(15,⌊log10depth1015⌋)
Original to BlazePhoenix (Core.vitality / psi / depthBucket). Admission at a full 16-slot table needs Ψ_new > 1.25 · Ψ_min — a single-SLOAD score that decays with no keeper and cannot be inflated by a hair-thin position, because depth enters as bucketed real magnitude.

Do not trust this page — reproduce it

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

read a slot's pool, then check its real depth: cast call <token> "balanceOf(address)(uint256)" <pool> --rpc-url https://mainnet.base.org — compare against what it advertises
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). Pool vitality: liveness as a measured property, not an assumption. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/pool-vitality
@misc{blazephoenix_pool_vitality,
  title  = {Pool vitality: liveness as a measured property, not an assumption},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/pool-vitality},
  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 Routing & pricing · 18 / 19
The Monoslot: a routing engine's whole memory in one storage word ›Every pool's full state — vitality, depth bucket, kind, fee, timestamps, bridge bit — packed into a single 256-bit slot, so scoring a candidate costs one SLOAD. Measured on a Base fork, a warm swap reads one word where the obvious layout reads several.5 min