Connect
Cover: A venue is data: how the Gate admits venues the Core cannot price natively

A venue is data: how the Gate admits venues the Core cannot price natively

How can a router use a venue it cannot price by reading storage, without trusting it?

For venues that cannot be priced from a few storage slots, an immutable wrapper looks like a V3 pair to the Router, an adapter enters through a 48-hour delay and an opcode scan, and the Router still measures the delta at the recipient.

Known formally as The Gate: kind 9 wrappers and the 48-hour adapter admission in the BlazePhoenix whitepaper.

BlazePhoenix Engineering · article updated 2026-11-16 · site dataset through 2026-11-19 · 8 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 — A router can use a venue it cannot price from storage by treating the venue as data, never as an authority. An immutable wrapper speaks the V3 swap ABI, an adapter enters through a 48-hour delay and an opcode scan, and the Router still measures the balance delta at the recipient.

Português — Um router pode usar um venue que não consegue avaliar a partir do storage tratando o venue como dados, nunca como autoridade. Um wrapper imutável fala o ABI de swap da V3, um adapter entra através de um atraso de 48 horas e de uma análise de opcodes, e o Router continua a medir a variação de saldo no destinatário.

Español — Un router puede usar un venue que no puede valorar desde el storage tratándolo como datos, nunca como autoridad. Un wrapper inmutable habla el ABI de swap de V3, un adapter entra tras un retraso de 48 horas y un escaneo de opcodes, y el Router sigue midiendo la variación de saldo en el destinatario.

Français — Un router peut utiliser un venue qu'il ne sait pas évaluer depuis le storage en le traitant comme une donnée, jamais comme une autorité. Un wrapper immuable parle l'ABI de swap V3, un adapter entre après un délai de 48 heures et une analyse des opcodes, et le Router mesure toujours la variation de solde chez le destinataire.

Deutsch — Ein Router kann eine Venue, die er nicht aus dem Storage bepreisen kann, nutzen, indem er sie als Daten behandelt, nie als Autorität. Ein unveränderlicher Wrapper spricht das V3-Swap-ABI, ein Adapter wird nach einer Verzögerung von 48 Stunden und einem Opcode-Scan zugelassen, und der Router misst weiterhin die Saldoänderung beim Empfänger.

Русский — Роутер может использовать площадку, которую не может оценить по storage, если считает её данными, а не авторитетом. Неизменяемый wrapper говорит на swap-ABI V3, adapter допускается через задержку в 48 часов и сканирование опкодов, а Router по-прежнему измеряет изменение баланса у получателя.

Türkçe — Bir router, storage üzerinden fiyatlayamadığı bir venue'yu, onu yetki olarak değil veri olarak ele alarak kullanabilir. Değiştirilemez bir wrapper V3 swap ABI'sini konuşur, bir adapter 48 saatlik gecikme ve opcode taramasından geçerek girer ve Router alıcıdaki bakiye farkını yine kendisi ölçer.

العربية — يستطيع الـ router استخدام venue لا يمكنه تسعيره من الـ storage إذا عامله بوصفه بيانات لا سلطة. يتحدث wrapper غير قابل للتغيير بواجهة swap الخاصة بـ V3، ويدخل الـ adapter بعد تأخير 48 ساعة وفحص للـ opcodes، ويظل الـ Router يقيس فرق الرصيد لدى المستلم.

हिन्दी — राउटर ऐसा venue भी इस्तेमाल कर सकता है जिसकी कीमत वह storage से नहीं निकाल सकता, बशर्ते वह उसे डेटा माने, अधिकार नहीं। एक अपरिवर्तनीय wrapper V3 swap ABI बोलता है, adapter 48 घंटे की देरी और opcode स्कैन से गुज़रकर आता है, और Router फिर भी प्राप्तकर्ता पर बैलेंस का अंतर खुद मापता है।

日本語 — ルーターは、ストレージから価格を付けられない venue でも、それを権威ではなくデータとして扱うことで使えます。不変の wrapper が V3 の swap ABI を話し、adapter は 48 時間の遅延と opcode スキャンを経て登録され、Router は受取人での残高の差分を引き続き自分で測ります。

中文 — 路由器可以使用无法通过 storage 定价的 venue,方法是把它当作数据而不是权威。不可变的 wrapper 使用 V3 的 swap ABI,adapter 经过 48 小时延迟和 opcode 扫描后才被纳入,而 Router 仍然在接收方测量余额变化。

한국어 — 라우터는 스토리지에서 가격을 매길 수 없는 venue도 그것을 권위가 아닌 데이터로 취급하여 사용할 수 있습니다. 불변 wrapper가 V3 swap ABI를 사용하고, adapter는 48시간 지연과 opcode 스캔을 거쳐 들어오며, Router는 여전히 수령인의 잔액 변화량을 직접 측정합니다.

Bahasa Indonesia — Router dapat memakai venue yang tidak bisa dihargai dari storage dengan memperlakukan venue sebagai data, bukan otoritas. Wrapper immutable berbicara dengan ABI swap V3, adapter masuk lewat jeda 48 jam dan pemindaian opcode, dan Router tetap mengukur selisih saldo di penerima.

বাংলা — রাউটার এমন venue-ও ব্যবহার করতে পারে যার দাম storage থেকে নির্ণয় করা যায় না, যদি সে venue-কে কর্তৃপক্ষ নয়, ডেটা হিসেবে দেখে। অপরিবর্তনীয় wrapper V3 swap ABI বলে, adapter 48 ঘণ্টার বিলম্ব ও opcode স্ক্যানের পর ঢোকে, আর Router তবুও প্রাপকের কাছে ব্যালান্সের পার্থক্য নিজেই মাপে।

Filipino — Magagamit ng router ang venue na hindi nito mapepresyuhan mula sa storage sa pamamagitan ng pagtrato rito bilang data, hindi bilang awtoridad. Ang immutable na wrapper ay gumagamit ng V3 swap ABI, ang adapter ay pumapasok sa pamamagitan ng 48-oras na delay at opcode scan, at sinusukat pa rin ng Router ang pagbabago ng balanse sa tatanggap.

Short answer: by treating the venue as data and never as an authority. A thin immutable wrapper stands in front of the venue and speaks the V3 swap ABI. Nothing the wrapper or its adapter says about its own output becomes an input to a floor, because the Router measures the balance delta at the recipient exactly as it does for a V3 pool.

This is the Gate, one factory row in the Hub (section 4.5 of the whitepaper). It exists for venues the Core cannot read natively: Balancer V2 and V3, Curve StableSwap-NG, Twocrypto-NG and Tricrypto-NG, PancakeSwap Infinity CL and Bin, Liquidity Book, and Algebra Integral.

Wrapper: a V3 shape the Router already knows

For each venue the Gate creates a wrapper at a derived address. To the Router the wrapper is kind 9: it speaks the V3 `swap` and `uniswapV3SwapCallback` ABI and forwards what it measured arriving to its family's adapter. The Hub admits kind 9 only as a `MODE_CREATE2_V3` factory row, so a wrapper can exist in the registry only at the address the Gate's own creation code derives.

When a leg of an external kind executes, the Router checks that the wrapper it names is the one the Gate derives from the hop's own tokens and fee. Otherwise it refuses with `RouterE(19)`. The kind in calldata is a claim, and the derived address is the identity.

Adapter: two steps, 48 hours apart

An adapter enters in two steps separated by `ADAPTER_DELAY = 48 hours`. At the proposal the Gate scans the adapter's runtime code opcode by opcode, stepping over `PUSH` data. It refuses `DELEGATECALL`, `CALLCODE` and `SELFDESTRUCT`, because code that can run foreign code in its own context, or vanish and be redeployed, would make a pin meaningless. Empty code and an EIP-7702 delegation prefix are refused too. The scan is conservative: it may refuse honest code and never admits dishonest code.

The proposal records the adapter's code hash. The acceptance reverts if the code has moved since, and pins the hash. From then on `liveAdapter` answers zero when none is set or when the code at the address is no longer the pinned code, and every swap reads it, so a changed adapter stops every wrapper of its family at the next call.

  1. Propose the adapter. The Gate scans its runtime code and records the code hash.
  2. Wait the 48-hour delay.
  3. Accept. If the code has moved since the proposal, the acceptance reverts; otherwise the hash is pinned.
  4. On every swap, `liveAdapter` re-checks the pinned code. A mismatch stops the family's wrappers.

What the Router trusts, and what it measures

An adapter is immutable, leaves no allowance standing, and after each call may hold no more of either token than before. A venue that can only be priced by simulating it is quoted by `eth_call`. That quote is advice to the caller, and the Router's execution floors never read it.

The Gate's one pricing function, `gateQuote`, asks its questions in order. First identity: the Hub has admitted the Gate, the Gate still runs the code it was admitted with, the wrapper sits at the address the Gate derives, and the family's adapter is live. Then the wrapper's own `quote` is called by `staticcall` under a fixed gas ceiling. A failure is a zero quote and the venue drops out.

ParameterValueWhat it bounds
ADAPTER_DELAY48 hoursTime between proposing and accepting an adapter
GATE_MAX_WRAPPERS4Wrappers per pair, so the work a solve can be handed is bounded
GATE_QUOTE_GAS500,000Gas ceiling on the wrapper's quote call
Gate runtime10,710 bytesBytecode, 13,866 under the EIP-170 limit
Wrapper runtime4,408 bytesBytecode, 20,168 under the EIP-170 limit

Source: FACTOS section 2 and whitepaper 2.4, section 4.5 (release profile at commit 969bcc6).

Why the cap is four

The reason is a cost, not a taste. The best door reads every wrapper of the pair on every solve, one identity check each, and every wrapper enters the Solver's funnel next to the native venues. A wrapper's mass is not measured from a reserve, so it is never dropped as dust. The cap is what bounds the work.

Creating a wrapper stays a curator act, because the first creation fixes the venue pool of its token pair and venue key for ever. An open door would let anyone occupy every slot with a thin pool of a legitimate venue. Clearing a family is a brake and not a power over funds: its wrappers revert from the next call and the other kinds are untouched.

What this does not claim

It does not claim every venue of those families is wrapped, only that the ones that are enter by this path. It does not make a venue's quote true. It makes the quote irrelevant to settlement: the floors are enforced on the delta the recipient actually received.

Do not trust this page — reproduce it

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

grep -n 'ADAPTER_DELAY\|MAX_WRAPPERS_PER_PAIR' src/BlazePhoenixGate.sol   # declared at lines 76 and 78 at commit 969bcc6, in a checkout of the V2 repository. Then read gateWrapperLive and the RouterE(19) refusal in the Router's leg execution. Reading: section 4.5 of the 2.4 whitepaper.
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). A venue is data: how the Gate admits venues the Core cannot price natively. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/a-venue-is-data/
@misc{blazephoenix_a_venue_is_data,
  title  = {A venue is data: how the Gate admits venues the Core cannot price natively},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/a-venue-is-data/},
  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 Architecture · 6 / 20
EIP-170 as a measured gate: every guard is paid for in bytes, and the build counts them ›Ethereum caps deployed runtime code at 24,576 bytes. The V2 build fails at 24,000 and a test enforces the same line, so the margin of each contract is a published number and every added guard has to fit.6 min

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

Go to APP