Connect ›
Cover: The Hub: a self-curating pool registry with fitness eviction

The Hub: a self-curating pool registry with fitness eviction

How BlazePhoenix keeps its candidate-pool set honest on-chain: a packed 256-bit slot registry capped at 16 slots, where a challenger must beat the incumbent by a 25% fitness margin to evict it.

Known formally as The Self-Healing Registry in the BlazePhoenix whitepaper.

BlazePhoenix Engineering · updated 2026-07-17 · 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 — The Hub keeps the candidate-pool registry on-chain: 16 packed slots per pair, where a challenger must beat the weakest incumbent's measured fitness by 25% to evict it — curation as a contest, not a whitelist.

Português — O Hub mantém o registo de pools candidatos on-chain: 16 slots compactados por par, onde um desafiante tem de superar em 25% a aptidão medida do incumbente mais fraco para o despejar — curadoria como concurso, não whitelist.

Español — El Hub mantiene el registro de pools candidatos en cadena: 16 slots empaquetados por par, donde un aspirante debe superar en un 25% la aptitud medida del titular más débil para expulsarlo — curaduría como concurso, no lista blanca.

Français — Le Hub conserve le registre des pools candidats on-chain : 16 slots compactés par paire, où un challenger doit dépasser de 25 % la fitness mesurée du plus faible titulaire pour l'évincer — une curation par concours, pas une whitelist.

Deutsch — Der Hub führt das Kandidaten-Pool-Register on-chain: 16 gepackte Slots pro Paar, wobei ein Herausforderer die gemessene Fitness des schwächsten Inhabers um 25 % übertreffen muss — Kuration als Wettbewerb, nicht als Whitelist.

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

Türkçe — Hub, aday havuz kaydını zincir üstünde tutar: çift başına 16 paket slot; bir meydan okuyucu, en zayıf mevcut havuzun ölçülen uygunluğunu %25 aşmadan onu çıkaramaz — beyaz liste değil, yarışma olarak küratörlük.

العربية — يحفظ الـHub سجل المجمّعات المرشحة على السلسلة: 16 خانة مضغوطة لكل زوج، حيث يجب على المنافس تجاوز لياقة أضعف شاغل بنسبة 25% ليطرده — تنسيق بالمسابقة لا بقائمة بيضاء.

हिन्दी — Hub उम्मीदवार पूल रजिस्ट्री ऑन-चेन रखता है: प्रति जोड़ी 16 पैक्ड स्लॉट, जहां चुनौती देने वाले को सबसे कमजोर मौजूदा पूल की मापी गई फिटनेस को 25% से हराना होता है — क्यूरेशन एक प्रतियोगिता है, व्हाइटलिस्ट नहीं।

日本語 — Hubは候補プールの登録簿をオンチェーンで保持します。ペアごとに16のパック済みスロットがあり、挑戦者は最弱の現職の計測フィットネスを25%上回らなければ追い出せません。キュレーションはホワイトリストではなく競争です。

中文 — Hub 将候选池注册表保存在链上:每个交易对 16 个紧凑槽位,挑战者必须以 25% 的优势超过最弱在位者的实测适应度才能将其驱逐——策展是竞赛,而非白名单。

한국어 — Hub는 후보 풀 레지스트리를 온체인에 보관합니다. 페어당 16개의 압축 슬롯이 있으며, 도전자는 가장 약한 기존 풀의 측정된 적합도를 25% 능가해야 퇴출시킬 수 있습니다. 큐레이션은 화이트리스트가 아니라 경쟁입니다.

Bahasa Indonesia — Hub menyimpan registri pool kandidat secara on-chain: 16 slot terkemas per pasangan, di mana penantang harus mengalahkan fitness terukur petahana terlemah sebesar 25% untuk menggusurnya — kurasi sebagai kontes, bukan whitelist.

বাংলা — Hub প্রার্থী-পুল রেজিস্ট্রি অন-চেইনে রাখে: প্রতি জোড়ায় ১৬টি প্যাকড স্লট, যেখানে চ্যালেঞ্জারকে দুর্বলতম বিদ্যমান পুলের পরিমাপকৃত ফিটনেস ২৫% ছাড়িয়ে যেতে হয় তাকে সরাতে — কিউরেশন একটি প্রতিযোগিতা, হোয়াইটলিস্ট নয়।

Filipino — Iniingatan ng Hub ang registry ng kandidatong pool on-chain: 16 packed slots bawat pares, kung saan kailangang lampasan ng hamon ang sinukat na fitness ng pinakamahinang nakaupo nang 25% para mapalitan ito — kurasyon bilang paligsahan, hindi whitelist.

An aggregator is only as good as its candidate set. Off-chain aggregators curate pool lists on servers — opaque, editable, and a single point of quiet manipulation. The BlazePhoenix Hub keeps the candidate registry ON-CHAIN: per token pair, a fixed array of at most 16 slots (MAX_SLOTS = 16), each slot packed into a single 256-bit storage word so that reading the whole registry costs one cold SLOAD per slot and updates stay cheap.

Anyone can propose a pool. Admission is not a vote and not a whitelist: it is a fitness contest. A challenger pool must demonstrate fitness — quoting capability against real held depth, the same capital-anchored measurement the Solver uses — that beats the weakest incumbent by at least a 25% margin (EVICTION_MARGIN) to take its slot.

Why a 25% margin and not a simple better-than

A bare better-than rule invites slot-thrashing: two near-equal pools evicting each other every block, burning gas and destabilizing routing. The hysteresis margin makes eviction meaningful — a new pool must be clearly better, not momentarily lucky. The margin also prices attacks: to occupy a slot you must sustain 25% superior real fitness, which for a phantom pool means actually holding superior depth (see the capital-anchor article).

Discovery is deterministic too: discoverFor derives expected pool addresses via CREATE2, so the registry can verify a candidate is the pool it claims to be rather than a proxy wearing its clothes.

Do not trust this page — reproduce it

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

Read the verified source of the Hub on Basescan (/verify lists the address): MAX_SLOTS = 16 is a compile-time constant with no getter, so the cap cannot be raised by any call. Then read any pair's slots directly from storage
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 Hub: a self-curating pool registry with fitness eviction. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/hub-slot-registry
@misc{blazephoenix_hub_slot_registry,
  title  = {The Hub: a self-curating pool registry with fitness eviction},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/hub-slot-registry},
  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 · 16 / 19
CREATE2 discovery: verifying a pool is who it claims to be ›How the BlazePhoenix Hub uses deterministic CREATE2 addresses (EIP-1014) to derive where a pool MUST live before trusting it — impersonation becomes an address mismatch instead of an exploit.5 min