Connect
Cover: Deterministic V4 discovery: finding every hookless pool without a factory, a list, or a deployer to trust

Deterministic V4 discovery: finding every hookless pool without a factory, a list, or a deployer to trust

Uniswap V4 has no factories or registry — every pool is keccak256(PoolKey) in one singleton. BlazePhoenix derives hookless ids over the canonical fee grid and probes them in one gas-free extsload: 99 calls become one, deployer-blind. Hooked pools remain unenumerable on-chain by construction.

Known formally as Singleton Derivation in the BlazePhoenix whitepaper.

BlazePhoenix Engineering · article updated 2026-08-18 · site dataset through 2026-11-19 · 9 min · written from the deployed bytecode

At a glance
LevelAdvanced
Formal nameSingleton Derivation
Reading time9 min
Sections6
Sources cited3
Updated2026-08-18

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

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

English — Uniswap V4 has no factories to scan and no registry to read: every pool of every deployer is keccak256(abi.encode(PoolKey)) inside one PoolManager singleton, and the PoolKeys live only in event logs, so the set is genuinely unenumerable from inside the EVM. BlazePhoenix therefore derives the canonical hookless PoolIds over the standard (fee, tickSpacing) grid and probes them in one batched gas-free extsload — 99 calls become one, deployer-blind, verified against StateView.getSlot0 to the wei on Base. Hooked pools stay unenumerable on-chain by construction; that limit is physics, not a gap.

Português — A Uniswap V4 não tem factories para varrer nem registo para ler: cada pool de cada deployer é keccak256(abi.encode(PoolKey)) dentro de um único singleton PoolManager, e as PoolKeys vivem apenas nos logs de eventos, pelo que o conjunto é genuinamente inenumerável de dentro da EVM. A BlazePhoenix deriva por isso os PoolIds canónicos sem hooks sobre a grelha padrão (fee, tickSpacing) e sonda-os num único extsload em lote sem gás — 99 chamadas tornam-se uma, cega ao deployer, verificada contra StateView.getSlot0 ao wei na Base. As pools com hooks permanecem inenumeráveis on-chain por construção; esse limite é física, não uma lacuna.

Español — Uniswap V4 no tiene factories que escanear ni registro que leer: cada pool de cada deployer es keccak256(abi.encode(PoolKey)) dentro de un único singleton PoolManager, y las PoolKeys viven solo en los logs de eventos, así que el conjunto es genuinamente inenumerable desde dentro de la EVM. BlazePhoenix por eso deriva los PoolIds canónicos sin hooks sobre la malla estándar (fee, tickSpacing) y los sondea en un único extsload por lotes sin gas — 99 llamadas se vuelven una, ciega al deployer, verificada contra StateView.getSlot0 al wei en Base. Las pools con hooks siguen siendo inenumerables on-chain por construcción; ese límite es física, no una carencia.

Français — Uniswap V4 n'a ni factories à scanner ni registre à lire : chaque pool de chaque déployeur est keccak256(abi.encode(PoolKey)) dans un unique singleton PoolManager, et les PoolKeys ne vivent que dans les logs d'événements, si bien que l'ensemble est véritablement inénumérable depuis l'EVM. BlazePhoenix dérive donc les PoolIds canoniques sans hooks sur la grille standard (fee, tickSpacing) et les sonde en un seul extsload groupé sans gaz — 99 appels deviennent un, aveugle au déployeur, vérifié contre StateView.getSlot0 au wei près sur Base. Les pools à hooks restent inénumérables on-chain par construction ; cette limite est de la physique, pas une lacune.

Deutsch — Uniswap V4 hat keine Factories zum Scannen und kein Register zum Lesen: Jeder Pool jedes Deployers ist keccak256(abi.encode(PoolKey)) in einem einzigen PoolManager-Singleton, und die PoolKeys leben nur in Event-Logs — die Menge ist aus der EVM heraus echt unaufzählbar. BlazePhoenix leitet daher die kanonischen hooklosen PoolIds über das Standard-Raster (fee, tickSpacing) her und prüft sie in einem gebündelten, gasfreien extsload — aus 99 Calls wird einer, deployer-blind, auf Base gegen StateView.getSlot0 aufs Wei verifiziert. Hooked Pools bleiben on-chain konstruktionsbedingt unaufzählbar; diese Grenze ist Physik, keine Lücke.

Русский — В Uniswap V4 нет фабрик для сканирования и реестра для чтения: каждый пул любого деплоера — это keccak256(abi.encode(PoolKey)) внутри одного синглтона PoolManager, а сами PoolKey живут только в логах событий, так что множество по-настоящему неперечислимо изнутри EVM. Поэтому BlazePhoenix выводит канонические безхуковые PoolId по стандартной сетке (fee, tickSpacing) и прощупывает их одним пакетным extsload без газа — 99 вызовов становятся одним, вслепую к деплоеру, сверено со StateView.getSlot0 до wei на Base. Пулы с хуками остаются неперечислимыми он-чейн по построению; этот предел — физика, а не пробел.

Türkçe — Uniswap V4'te taranacak factory ve okunacak kütük yoktur: her deployer'ın her havuzu tek bir PoolManager singleton'ı içinde keccak256(abi.encode(PoolKey))'dir ve PoolKey'ler yalnızca olay kayıtlarında yaşar; küme EVM içinden gerçekten sayılamazdır. Bu yüzden BlazePhoenix kanonik hooksuz PoolId'leri standart (fee, tickSpacing) ızgarası üzerinde türetir ve tek bir toplu, gazsız extsload ile yoklar — 99 çağrı bire iner, deployer-körü, Base'de StateView.getSlot0'a wei'ine kadar doğrulanmış. Hook'lu havuzlar yapı gereği zincir üstünde sayılamaz kalır; bu sınır fizik, eksik değil.

العربية — ليس في Uniswap V4 مصانع تُمسح ولا سجل يُقرأ: كل مجمّع لأي ناشر هو keccak256(abi.encode(PoolKey)) داخل singleton واحد هو PoolManager، ومفاتيح PoolKey لا تعيش إلا في سجلات الأحداث، فالمجموعة غير قابلة للتعداد حقاً من داخل EVM. لذلك تشتق BlazePhoenix معرّفات المجمّعات القانونية بلا خطافات على الشبكة القياسية (fee, tickSpacing) وتسبرها في extsload واحد مجمّع بلا غاز — 99 استدعاء تصير واحداً، بعمى عن الناشر، متحقَّقاً منه مقابل StateView.getSlot0 حتى الـwei على Base. المجمّعات ذات الخطافات تبقى غير قابلة للتعداد على السلسلة بحكم البناء؛ وهذا الحد فيزياء لا ثغرة.

हिन्दी — Uniswap V4 में स्कैन करने को factories नहीं और पढ़ने को रजिस्ट्री नहीं: हर deployer का हर पूल एक ही PoolManager singleton के भीतर keccak256(abi.encode(PoolKey)) है, और PoolKey केवल इवेंट-लॉग में रहती हैं, इसलिए यह समुच्चय EVM के भीतर से वाकई अगणनीय है। इसलिए BlazePhoenix मानक (fee, tickSpacing) ग्रिड पर विहित हुक-रहित PoolId व्युत्पन्न करता है और उन्हें एक ही बैच्ड, गैस-मुक्त extsload में टटोलता है — 99 कॉल एक बन जाती हैं, deployer से अंधी, Base पर StateView.getSlot0 से wei तक सत्यापित। हुक वाले पूल रचना से ही ऑन-चेन अगणनीय रहते हैं; वह सीमा भौतिकी है, कमी नहीं।

日本語 — Uniswap V4にはスキャンすべきファクトリーも読むべきレジストリもありません。あらゆるデプロイヤーのあらゆるプールは、一つのPoolManagerシングルトン内部のkeccak256(abi.encode(PoolKey))であり、PoolKey自体はイベントログにしか存在しないため、その集合はEVM内部から本当に列挙不能です。そこでBlazePhoenixは標準の(fee, tickSpacing)グリッド上で正準のフックなしPoolIdを導出し、一度のバッチ化されたガス不要のextsloadで探査します。99回の呼び出しが1回になり、デプロイヤーに盲目で、BaseでStateView.getSlot0とweiまで一致することを検証済みです。フック付きプールは構成上オンチェーンで列挙不能のままです。その限界は物理であって欠落ではありません。

中文 — Uniswap V4 没有可扫描的工厂、没有可读的注册表:任何部署者的任何池都是唯一 PoolManager 单例内部的 keccak256(abi.encode(PoolKey)),而 PoolKey 本身只存在于事件日志中,因此这个集合在 EVM 内部是真正不可枚举的。BlazePhoenix 于是在标准 (fee, tickSpacing) 网格上推导规范的无钩子 PoolId,并用一次批量、零 gas 的 extsload 探测——99 次调用变成一次,对部署者视而不见,在 Base 上与 StateView.getSlot0 精确到 wei 相互验证。带钩子的池按构造在链上仍不可枚举;那个界限是物理,不是缺口。

한국어 — Uniswap V4에는 스캔할 팩토리도 읽을 레지스트리도 없습니다. 모든 배포자의 모든 풀은 단 하나의 PoolManager 싱글턴 안의 keccak256(abi.encode(PoolKey))이고, PoolKey 자체는 이벤트 로그에만 존재하므로 그 집합은 EVM 내부에서 정말로 열거 불가능합니다. 그래서 BlazePhoenix는 표준 (fee, tickSpacing) 격자 위에서 정준 훅 없는 PoolId들을 도출하고, 한 번의 배치된 가스 없는 extsload로 탐사합니다 — 99번의 호출이 한 번이 되고, 배포자를 보지 않으며, Base에서 StateView.getSlot0과 wei 단위까지 일치함이 검증되었습니다. 훅이 있는 풀은 구조상 온체인에서 열거 불가능한 채로 남습니다. 그 한계는 물리이지 공백이 아닙니다.

Bahasa Indonesia — Uniswap V4 tak punya factory untuk dipindai dan tak punya registri untuk dibaca: setiap pool dari setiap deployer adalah keccak256(abi.encode(PoolKey)) di dalam satu singleton PoolManager, dan PoolKey hanya hidup di log peristiwa, jadi himpunannya sungguh tak terenumerasi dari dalam EVM. Karena itu BlazePhoenix menurunkan PoolId kanonik tanpa hook di atas kisi standar (fee, tickSpacing) dan memeriksanya dalam satu extsload berkelompok bebas gas — 99 panggilan menjadi satu, buta-deployer, terverifikasi terhadap StateView.getSlot0 hingga ke wei di Base. Pool ber-hook tetap tak terenumerasi on-chain menurut konstruksi; batas itu fisika, bukan celah.

বাংলা — Uniswap V4-এ স্ক্যান করার factory নেই, পড়ার রেজিস্ট্রি নেই: প্রতিটি ডিপ্লয়ারের প্রতিটি পুল হলো এক PoolManager singleton-এর ভেতরে keccak256(abi.encode(PoolKey)), আর PoolKey-গুলো শুধু ইভেন্ট-লগে থাকে, তাই সেটটি EVM-এর ভেতর থেকে সত্যিই অগণনাযোগ্য। তাই BlazePhoenix প্রমিত (fee, tickSpacing) গ্রিডে বিধিসম্মত হুকবিহীন PoolId নিষ্পন্ন করে এবং একটিমাত্র ব্যাচড, গ্যাসবিহীন extsload-এ সেগুলো পরখ করে — ৯৯টি কল একটিতে নামে, ডিপ্লয়ারে অন্ধ, Base-এ StateView.getSlot0-এর সঙ্গে wei পর্যন্ত যাচাইকৃত। হুকযুক্ত পুল গঠনগতভাবেই অন-চেইনে অগণনাযোগ্য থাকে; সেই সীমা পদার্থবিদ্যা, ফাঁক নয়।

Filipino — Walang factories na maiiskan at walang registry na mababasa ang Uniswap V4: bawat pool ng bawat deployer ay keccak256(abi.encode(PoolKey)) sa loob ng iisang PoolManager singleton, at ang mga PoolKey ay nabubuhay lamang sa mga event log, kaya ang set ay tunay na hindi maisa-isa mula sa loob ng EVM. Kaya hinahango ng BlazePhoenix ang mga kanonikal na hookless na PoolId sa karaniwang (fee, tickSpacing) na grid at sinusuri ang mga ito sa iisang batched at walang-gas na extsload — 99 na tawag ay nagiging isa, bulag sa deployer, napatunayan laban sa StateView.getSlot0 hanggang sa wei sa Base. Ang mga pool na may hook ay nananatiling hindi maisa-isa on-chain ayon sa konstruksyon; ang hangganang iyon ay pisika, hindi puwang.

To discover a Uniswap V2 or V3 pool you derive an address: CREATE2 makes the pool of a token pair a pure function of factory, salt and init code, so you can compute where it MUST live and check (that is the sibling technique — see create2-discovery). V4 deletes the thing that derivation stood on. There are no per-pool contracts and no factories: every pool of every deployer lives as a storage entry inside ONE PoolManager singleton per chain. There is nothing to scan.

That sounds like it makes discovery harder. It makes it cleaner. Because there is exactly one creation path — PoolManager.initialize(PoolKey, sqrtPrice) — every pool that has ever existed, from any deployer, is identified the same way: PoolId = keccak256(abi.encode(PoolKey)). The pool is not something you look up in a directory; it is the hash of its own definition. The deployer is erased from the trust model — you never ask who made a pool, only whether the id you derived reads back a live price.

The meta-pattern: you cannot enumerate, but you can derive

A PoolKey is five fields — currency0, currency1, fee, tickSpacing, hooks. The singleton keys its state by the keccak of those five, and — this is the load-bearing fact — the PoolKeys themselves are never stored on-chain; they exist only in the Initialize event log. A contract cannot read logs. So there is no on-chain function that returns "all pools for USDC/WETH": the set is genuinely unenumerable from inside the EVM.

But the same asymmetry that forbids enumeration grants derivation. Serious hookless liquidity clusters on a tiny, industry-standard grid of (fee, tickSpacing) tiers. For a pair, we can DERIVE the four canonical PoolIds — hooks fixed to address(0) — and ask the singleton whether each exists. That is not a lookup against a list we maintain; it is arithmetic anyone reproduces, and it works for a pool deployed one block ago by someone we have never heard of.

The whole discovery, as one equation and one read

The id is one hash over the five-field key; existence is one storage read on the singleton at the slot that key hashes to. Both are pure functions — no registry, no admin, no gas:

id=keccak256(abi.encode(c0,c1,fee,ts,0)),exists⇔sqrtPid≠0
PoolId over the hookless (hooks = 0) canonical key; the pool exists iff extsload of its slot0 (base = keccak256(abi.encode(id, 6)), low 160 bits) returns a non-zero sqrtPriceX96. Verified live on Base: for WETH/USDC all four canonical tiers read non-zero, and this slot0 read matches the canonical StateView.getSlot0 to the wei at the same block.

One call, zero gas, deployer-blind

The Hub's V4 derive-scan sorts the pair, derives the canonical hookless ids, and reads them all through one batched extsload on the singleton, returning the tiers that hold a live price and liquidity. It is a view function — an eth_call — so it costs no gas, and it is deterministic: the same inputs give the same ids at every block. What it replaces is worth naming: not a 99-call factory sweep, and not an admin allowlist of "approved" pools. There is nothing to approve, because a pool cannot lie about its own id.

The discovered pools merge into the router's candidate set alongside V2/V3 venues; the best output wins, and the contract-enforced iron floor makes admission safe without trusting the pool — the worst a bad pool can do is fail to fill or deliver less, which the floor catches. Identity-free discovery, execution-time safety.

The honest limit: hooked pools are physics, not a gap

The derive-scan finds HOOKLESS pools. Hooked pools carry an arbitrary hook contract, and a hook address is 160 bits with only its low 14 bits constrained (those encode the hook's permission flags, mined into the address via CREATE2). The other ~146 bits are free. You cannot iterate 2^146 addresses, and the only record of which hooks exist for a pair is the Initialize log a contract cannot read. So hooked-pool enumeration on-chain is impossible — for anyone, not just us. It is a property of V4's design, and pretending otherwise would be the kind of unverifiable claim this protocol exists to avoid.

Measured on Base: for WETH/USDC, all four canonical hookless tiers exist. For memecoins the picture is exactly what the design predicts — BRETT/WETH and DEGEN/WETH each expose one hookless canonical pool that the derive-scan finds; a token whose V4 liquidity lives behind a hook (dynamic fees, anti-snipe) exposes none to this call. Those are reachable only through an off-chain feed of the Initialize logs — which stays allowlist-free, because a submitted key still self-proves against the singleton.

The bits that classify what you cannot enumerate

Enumeration is impossible, but classification is free and objective — three small bit-patterns handle every V4 pool without trusting a soul. The hook's low 14 bits say what it may do (beforeSwap, afterSwap, return-delta) straight from its address. The pool's fee field says whether the fee is dynamic: bit 23, the flag 0x800000, distinguishes a dynamic-fee pool (its live fee set by the hook) from a static one, and static fees never reach that bit. And the current fee of a dynamic pool is not a mystery either — it lives in slot0's lpFee field, read in the same extsload that reads the price. Derive the id, read the slot, and the pool's price, liquidity and live fee are all in hand — no oracle, no registry, no permission.

Do not trust this page — reproduce it

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

reproduce a derivation end to end (Base WETH/USDC, 0.05% tier): PID=$(cast keccak $(cast abi-encode "f(address,address,uint24,int24,address)" 0x4200000000000000000000000000000000000006 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 500 10 0x0000000000000000000000000000000000000000)); cast call 0xa3c0c9b65bad0b08107aa264b0f3db444b867a71 "getSlot0(bytes32)(uint160,int24,uint24,uint24)" $PID --rpc-url https://mainnet.base.org — a non-zero sqrtPriceX96 is the pool, derived not looked up
Cite this article

Licensed CC BY-NC-ND 4.0: quote and cite it with attribution and a link. Commercial use and derivative versions need written permission from BlazePhoenix; translations are made by BlazePhoenix. Copy a ready-made citation:

BlazePhoenix (2026). Deterministic V4 discovery: finding every hookless pool without a factory, a list, or a deployer to trust. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/deterministic-v4-discovery/
@misc{blazephoenix_deterministic_v4_discovery,
  title  = {Deterministic V4 discovery: finding every hookless pool without a factory, a list, or a deployer to trust},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/deterministic-v4-discovery/},
  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). Sources cited: Uniswap v4-core: PoolManager.sol (singleton, initialize, Initialize event), src/types/PoolId.sol (keccak of the key), src/libraries/StateLibrary.sol (POOLS_SLOT = 6, slot0 packing), src/libraries/Hooks.sol (14 permission-flag bits). · Uniswap v4-core LPFeeLibrary: DYNAMIC_FEE_FLAG = 0x800000. · EIP-1014 (CREATE2) — the V2/V3 sibling derivation.

Related engineering

Next in Foundations · 17 / 33
BlazePhoenix V2: gasless, chain-agnostic, and engineered so whole classes of bug cannot occur ›An overview of the BlazePhoenix V2 redesign — the primitives it is built on, what changes versus V1, and its status: specified, pre-launch; independent audit not done yet.7 min

Questions, a partnership or a bug to report? Contact us or email contact@blazephoenix.xyz

Go to APP