Connect
Cover: Gated pools: how BlazePhoenix routes through permissioned venues

Gated pools: how BlazePhoenix routes through permissioned venues

How does BlazePhoenix route through venues its Core cannot read?

The BlazePhoenixGate puts venues the Core cannot read natively, from Curve and Balancer to PancakeSwap Infinity, Liquidity Book and Algebra Integral, behind thin wrappers with a CREATE2 identity, admits their adapters by propose, 48 hours, accept, pins the code, and settles by measured delta.

BlazePhoenix Engineering · article updated 2026-11-17 · site dataset through 2026-11-19 · 7 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 — How the BlazePhoenixGate of the 2.0.0 generation routes through Curve, Balancer, PancakeSwap Infinity, Liquidity Book and Algebra Integral venues: wrappers whose address is derived by CREATE2 under the V3 salt, adapters admitted by propose, 48 hours, accept and revoked at once, the factory code-hash pin checked by gateWrapperLive, and swaps settled by measured delta on explicit routes. None of the eight adapters is deployed on mainnet yet.

Português — Como o BlazePhoenixGate da geração 2.0.0 encaminha por venues Curve, Balancer, PancakeSwap Infinity, Liquidity Book e Algebra Integral: wrappers com endereço derivado por CREATE2 sob o salt V3, adapters admitidos por proposta, 48 horas e aceitação e revogados de imediato, o pin do codehash da factory conferido pelo gateWrapperLive, e swaps liquidados pelo delta medido em rotas explícitas. Nenhum dos oito adaptadores está ainda implantado em mainnet.

Español — Cómo el BlazePhoenixGate de la generación 2.0.0 enruta por venues de Curve, Balancer, PancakeSwap Infinity, Liquidity Book y Algebra Integral: wrappers cuya dirección se deriva por CREATE2 con el salt V3, adapters admitidos por propuesta, 48 horas y aceptación y revocados al instante, el pin del codehash de la factory comprobado por gateWrapperLive, y swaps liquidados por el delta medido en rutas explícitas. Ninguno de los ocho adaptadores está desplegado todavía en mainnet.

Français — Comment le BlazePhoenixGate de la génération 2.0.0 route vers des venues Curve, Balancer, PancakeSwap Infinity, Liquidity Book et Algebra Integral : des wrappers dont l'adresse est dérivée par CREATE2 sous le salt V3, des adapters admis par proposition, 48 heures puis acceptation et révoqués sur-le-champ, le pin du codehash de la factory vérifié par gateWrapperLive, et des swaps réglés par le delta mesuré sur des routes explicites. Aucun des huit adaptateurs n'est encore déployé sur le mainnet.

Deutsch — Wie das BlazePhoenixGate der Generation 2.0.0 über Venues von Curve, Balancer, PancakeSwap Infinity, Liquidity Book und Algebra Integral routet: Wrapper, deren Adresse per CREATE2 unter dem V3-Salt abgeleitet wird, Adapter, die per Vorschlag, 48 Stunden und Annahme zugelassen und sofort widerrufen werden, der Codehash-Pin der Factory, den gateWrapperLive prüft, und Swaps, die über das gemessene Delta auf expliziten Routen abgerechnet werden. Keiner der acht Adapter ist bisher im Mainnet bereitgestellt.

Русский — Как BlazePhoenixGate поколения 2.0.0 маршрутизирует через площадки Curve, Balancer, PancakeSwap Infinity, Liquidity Book и Algebra Integral: обёртки, чей адрес выводится через CREATE2 с солью V3, адаптеры, допускаемые по схеме предложение, 48 часов, принятие и отзываемые сразу, привязка к codehash фабрики, которую проверяет gateWrapperLive, и свопы, рассчитываемые по измеренной дельте на явных маршрутах. Ни один из восьми адаптеров пока не развёрнут в mainnet.

Türkçe — 2.0.0 neslinin BlazePhoenixGate yapısı Curve, Balancer, PancakeSwap Infinity, Liquidity Book ve Algebra Integral venue'larından nasıl rota kurar: adresi V3 salt ile CREATE2 üzerinden türetilen wrapper'lar, öneri, 48 saat ve kabul ile alınan ve anında geri çekilen adapter'lar, gateWrapperLive ile denetlenen factory codehash sabitlemesi ve açık rotalarda ölçülen delta ile kapanan swap'lar. Sekiz adaptörün hiçbiri henüz mainnet'te dağıtılmış değildir.

العربية — كيف يوجّه BlazePhoenixGate من جيل 2.0.0 الصفقات عبر منصات Curve وBalancer وPancakeSwap Infinity وLiquidity Book وAlgebra Integral: أغلفة يُشتق عنوانها عبر CREATE2 بملح V3، ومحوّلات تُقبل بالاقتراح ثم 48 ساعة ثم القبول وتُسحب فورًا، وتثبيت codehash للمصنع يتحقق منه gateWrapperLive، وصفقات تُسوّى بالفرق المقاس على المسارات الصريحة. لم يُنشر أيٌّ من المحوِّلات الثمانية على الـ mainnet بعد.

हिन्दी — 2.0.0 पीढ़ी का BlazePhoenixGate Curve, Balancer, PancakeSwap Infinity, Liquidity Book और Algebra Integral venues से कैसे रूट करता है: wrappers जिनका पता V3 salt के तहत CREATE2 से निकाला जाता है, adapters जो प्रस्ताव, 48 घंटे और स्वीकृति से जुड़ते हैं और तुरंत हटाए जा सकते हैं, factory के codehash का pin जिसे gateWrapperLive जाँचता है, और explicit routes पर मापे गए delta से निपटने वाले swaps। आठों में से कोई भी एडैप्टर अभी mainnet पर डिप्लॉय नहीं हुआ है।

日本語 — 2.0.0 世代の BlazePhoenixGate が Curve、Balancer、PancakeSwap Infinity、Liquidity Book、Algebra Integral の venue を経由してルーティングする仕組み:V3 の salt で CREATE2 によりアドレスが導出される wrapper、提案・48 時間・承認で採用され即時に取り消せる adapter、gateWrapperLive が確認する factory の codehash ピン、明示ルート上で測定した差分で決済される swap。8 つのアダプターはいずれもまだメインネットにデプロイされていません。

中文 — 2.0.0 代的 BlazePhoenixGate 如何经由 Curve、Balancer、PancakeSwap Infinity、Liquidity Book 与 Algebra Integral 场所路由:在 V3 salt 下由 CREATE2 推导地址的 wrapper,经提议、48 小时、接受才被采纳并可立即撤销的 adapter,由 gateWrapperLive 核验的 factory codehash 锁定,以及在显式路由上按实测差额结算的兑换。这八个适配器目前都尚未部署到主网。

한국어 — 2.0.0 세대의 BlazePhoenixGate가 Curve, Balancer, PancakeSwap Infinity, Liquidity Book, Algebra Integral venue를 거쳐 라우팅하는 방식: V3 salt 아래 CREATE2로 주소가 도출되는 wrapper, 제안·48시간·수락으로 채택되고 즉시 철회되는 adapter, gateWrapperLive가 확인하는 factory codehash 고정, 그리고 명시적 경로에서 측정된 차이로 정산되는 스왑. 8개 어댑터는 아직 어느 것도 메인넷에 배포되지 않았습니다.

Bahasa Indonesia — Cara BlazePhoenixGate generasi 2.0.0 merutekan lewat venue Curve, Balancer, PancakeSwap Infinity, Liquidity Book, dan Algebra Integral: wrapper yang alamatnya diturunkan lewat CREATE2 dengan salt V3, adapter yang diterima lewat usulan, 48 jam dan penerimaan serta dapat dicabut seketika, pin codehash factory yang diperiksa gateWrapperLive, dan swap yang diselesaikan dengan delta terukur pada rute eksplisit. Belum ada satu pun dari delapan adapter ini yang di-deploy di mainnet.

বাংলা — 2.0.0 প্রজন্মের BlazePhoenixGate কীভাবে Curve, Balancer, PancakeSwap Infinity, Liquidity Book ও Algebra Integral venue দিয়ে রুট করে: V3 salt-এর অধীনে CREATE2 দিয়ে ঠিকানা নির্ণীত wrapper, প্রস্তাব, 48 ঘণ্টা ও গ্রহণের মাধ্যমে যুক্ত এবং সঙ্গে সঙ্গে প্রত্যাহারযোগ্য adapter, gateWrapperLive-এর যাচাই করা factory codehash pin, আর explicit route-এ মাপা delta দিয়ে নিষ্পন্ন swap। আটটি অ্যাডাপ্টারের কোনোটিই এখনও mainnet-এ ডিপ্লয় করা হয়নি।

Filipino — Paano dumadaan ang BlazePhoenixGate ng 2.0.0 generation sa mga venue ng Curve, Balancer, PancakeSwap Infinity, Liquidity Book at Algebra Integral: mga wrapper na ang address ay hinango sa CREATE2 sa ilalim ng V3 salt, mga adapter na tinatanggap sa mungkahi, 48 oras at pagtanggap at nababawi agad, ang pin ng codehash ng factory na sinusuri ng gateWrapperLive, at mga swap na naaayos sa sinukat na delta sa tahasang ruta. Wala pa sa walong adapter ang naka-deploy sa mainnet.

BlazePhoenixGate is the 2.0.0 contract that lets the BlazePhoenix DEX route through venues the Core cannot read natively. That generation is scheduled to launch on 15 December 2026; it is not deployed yet, and no address is published for it. The DEX main branch carries eight adapters for the Gate: Curve StableSwap-NG; Curve Twocrypto-NG and Tricrypto-NG; Balancer V2; Balancer V3; PancakeSwap Infinity CL; PancakeSwap Infinity Bin; Liquidity Book (LFJ v2.1 and v2.2, Pharaoh DLMM); and Algebra Integral (Blackhole). None of them is deployed on mainnet yet. The Gate places these venues behind thin wrappers, and the venue adapters article describes what each adapter checks.

To the Router, each wrapper looks like a Uniswap V3 pair: it answers swap and uniswapV3SwapCallback, and exposes token0, token1 and fee. Behind it, an adapter for the venue family trades on the real venue.

The Gate is registered in the Hub as one factory row of kind KIND_EXTERNAL (kind 9) in mode MODE_CREATE2_V3. Everything below describes the code in the public repository; the generation that carries it is the one that goes live on the launch date.

What is a Gate wrapper?

A wrapper is an immutable contract with no proxy. Its immutables are the gate that made it, the two tokens, a venue key (family << 16 | slot, which the Hub reads as the fee field), the venue contract it fronts and two auxiliary words for the adapter. Between calls it holds no tokens; its one piece of state is a use counter, vitalSlot.

Wrappers are created by the curator through Gate.create. At creation the Gate asks the family adapter to resolve the pair: the adapter must prove from the venue itself (its registry, factory or vault) that the hinted contract belongs to that venue for those two tokens. The answer is written into the wrapper as an immutable, so the venue behind a slot is fixed for the life of the wrapper. A venue key of 0 is refused, because the Hub reserves fee 0 for the Algebra derivation.

How is a wrapper's address derived?

A wrapper is found by computation, not by a list. The Gate deploys each wrapper with CREATE2 under the same salt formula the Hub uses for Uniswap V3 factories, Core.v3Salt, and with the hash of the wrapper creation code, WRAPPER_INIT_HASH. Anyone can recompute the address from the Gate, the two tokens and the venue key, and Gate.wrapperAddress returns it whether or not the wrapper exists yet.

The Hub admits kind 9 in the MODE_CREATE2_V3 row and refuses it in rows that look addresses up from a factory: a lookup row would trust the factory's answer, and a wrapper's identity is its CREATE2 address and nothing else.

wrapper = CREATE2(gate, keccak256(abi.encode(token0, token1, venueKey)), WRAPPER_INIT_HASH)
# token0 < token1 (sorted), venueKey = family << 16 | slot, venueKey != 0
# the same salt (Core.v3Salt) the Hub derives Uniswap V3 pairs with

How is an adapter admitted, and how is it removed?

In BlazePhoenixGate, an adapter change waits 48 hours (ADAPTER_DELAY). The first step, proposeAdapter, scans the candidate runtime code opcode by opcode, stepping over PUSH data, and refuses DELEGATECALL, CALLCODE and SELFDESTRUCT, as well as empty code and an EIP-7702 delegation designator; it records the code hash. acceptAdapter succeeds once that delay has passed and the code hash still matches the proposal, and it pins that hash.

liveAdapter returns zero when no adapter is set or when the adapter code no longer matches its pin, and every wrapper swap asks liveAdapter again. clearAdapter takes effect at once: from then on the wrappers of that family revert, and other kinds of venue are untouched. After renounceControl the curator can still add a new family or a new wrapper, but can no longer replace or clear an adapter.

StepDelayWhat is checked
proposeAdapterstarts 48 hcode scan, code hash recorded
acceptAdapterafter 48 hcode hash unchanged, then pinned
each swapnoneliveAdapter: code still matches the pin
clearAdapterimmediatethe family stops executing

What does the factory code-hash pin add?

When the Hub admits a factory with addFactory, it stores that factory's code hash, readable as Hub.factoryCodehashOf. A kind 9 leg is accepted through BPC.gateWrapperLive, which does not take the calldata's word that an address is a wrapper. It asks the wrapper which gate made it, requires that gate's current code hash to equal the hash the Hub admitted, recomputes the CREATE2 address from the hop's own tokens and the leg's fee and requires it to equal the wrapper, and requires a live adapter for the family.

Each of those reads is gas-capped and reads as zero on failure, so the check fails closed. The Router's kind 9 path and the Quoter both use it; a leg that fails it reverts with RouterE(19).

How does a swap through a wrapper settle?

The Router calls the wrapper with the Uniswap V3 swap ABI, exact input. The wrapper asks for its input through uniswapV3SwapCallback, measures how much arrived, and reverts if it is less than requested. It forwards exactly that measured amount to the adapter, which trades on the venue and pays the recipient.

Custody is then checked by delta: the adapter must end holding no more of either token than before, and so must the wrapper. The output reported back to the Router is the balance change measured at the recipient, never a figure the adapter returns. The swap never reads the quote, and the floors stay the Router's: each leg must deliver at least 80 percent of its bound, and the transaction must deliver the caller's minimum.

Where are gated venues executed?

In this design, BlazePhoenix runs gated legs on the Router's explicit-route doors: the caller supplies the route, built off-chain and priced with Quoter.previewRouteExact through eth_call. The best-route door, swapBestExactIn, re-enters as the Router itself, and a plan carrying a kind 9 leg is refused there; the Solver does not plan Gate legs.

The companion article on gate vitality explains how a gated venue reports that it is alive and how deep it is, and the trust-minimised routing article places the Gate in the wider trust model. The venue adapters article describes each of the eight adapters.

Do not trust this page — reproduce it

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

git clone https://github.com/blazephoenixxyz-crypto/Blaze-Phoenix-Dex && cd Blaze-Phoenix-Dex && grep -n 'ADAPTER_DELAY\|function clearAdapter\|function liveAdapter\|function wrapperAddress' src/BlazePhoenixGate.sol && grep -n 'function gateWrapperLive' src/BlazePhoenixCore.sol
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). Gated pools: how BlazePhoenix routes through permissioned venues. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/gated-pools-permissioned-venues/
@misc{blazephoenix_gated_pools_permissioned_venues,
  title  = {Gated pools: how BlazePhoenix routes through permissioned venues},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/gated-pools-permissioned-venues/},
  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: EIP-1014 · EIP-7702

Related engineering

Next in Architecture · 1 / 20
Venue adapters and the Gate: one adapter per pool design, admitted by a delay and a code pin ›Eight adapter contracts on the DEX main branch let the 2.0.0 Router reach Curve, Balancer, PancakeSwap Infinity, Liquidity Book and Algebra Integral pools. What an adapter is, what the Gate checks on every swap, and what it does not protect.9 min

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

Go to APP