Connect
Cover: Wired is not demonstrated: the difference between a venue family the code supports and one exercised against real chain state

Wired is not demonstrated: the difference between a venue family the code supports and one exercised against real chain state

What is the difference between a supported venue family and a demonstrated one?

Support decomposes into three independent stages — found, priced, executed — and a table that reports the union inflates. Five families work end to end, four have been demonstrated against real chain state, and the three rows that fail are described rather than hidden.

Known formally as The support decomposition in the BlazePhoenix whitepaper.

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

At a glance
LevelAdvanced
Formal nameThe support decomposition
Reading time10 min
Sections7
Updated2026-08-26

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

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

English — "Supported" is the conjunction of three independent predicates — discovery finds the venue, the solver prices it, the router executes against it — and a table reporting their union inflates without anyone lying. Applied to our own table: five of eight venue kinds work end to end (constant-product, concentrated liquidity, stableswap, Solidly dual, singleton), while cryptoswap is never emitted by discovery, the weighted-pool kind is an alias priced as constant product, and dynamic fee prices at fee = 0.

Português — "Suportado" é a conjunção de três predicados independentes — a descoberta encontra a venue, o solver dá-lhe preço, o router executa contra ela — e uma tabela que reporta a união deles infla sem ninguém mentir. Aplicado à nossa própria tabela: cinco de oito tipos de venue funcionam de ponta a ponta (produto constante, liquidez concentrada, stableswap, dual Solidly, singleton), enquanto o cryptoswap nunca é emitido pela descoberta, o tipo weighted-pool é um alias cotado como produto constante, e o dynamic fee cota com fee = 0.

Español — "Soportado" es la conjunción de tres predicados independientes — el descubrimiento encuentra la venue, el solver la cotiza, el router ejecuta contra ella — y una tabla que reporta su unión se infla sin que nadie mienta. Aplicado a nuestra propia tabla: cinco de ocho tipos de venue funcionan de punta a punta (producto constante, liquidez concentrada, stableswap, dual Solidly, singleton), mientras que cryptoswap nunca es emitido por el descubrimiento, el tipo weighted-pool es un alias cotizado como producto constante, y dynamic fee cotiza con fee = 0.

Français — « Supporté » est la conjonction de trois prédicats indépendants — la découverte trouve la venue, le solveur la price, le routeur exécute contre elle — et une table qui rapporte leur union gonfle sans que personne ne mente. Appliqué à notre propre table : cinq des huit sortes de venues fonctionnent de bout en bout (produit constant, liquidité concentrée, stableswap, dual Solidly, singleton), tandis que cryptoswap n'est jamais émis par la découverte, la sorte weighted-pool est un alias pricé comme du produit constant, et dynamic fee price avec fee = 0.

Deutsch — „Unterstützt" ist die Konjunktion dreier unabhängiger Prädikate — Discovery findet die Venue, der Solver bepreist sie, der Router führt gegen sie aus — und eine Tabelle, die deren Vereinigung berichtet, bläht sich auf, ohne dass jemand lügt. Auf unsere eigene Tabelle angewandt: Fünf von acht Venue-Arten funktionieren Ende zu Ende (Constant Product, Concentrated Liquidity, Stableswap, Solidly-Dual, Singleton), während Cryptoswap von der Discovery nie emittiert wird, die Weighted-Pool-Art ein als Constant Product bepreister Alias ist und Dynamic Fee mit fee = 0 bepreist.

Русский — «Поддерживается» — это конъюнкция трёх независимых предикатов: обнаружение находит площадку, солвер её оценивает, роутер против неё исполняет; таблица, сообщающая их объединение, раздувается без чьего-либо вранья. Применительно к нашей собственной таблице: пять из восьми видов площадок работают из конца в конец (постоянное произведение, концентрированная ликвидность, stableswap, дуал Solidly, синглтон), тогда как cryptoswap никогда не эмитится обнаружением, вид weighted-pool — алиас, оцениваемый как постоянное произведение, а dynamic fee оценивает при fee = 0.

Türkçe — "Destekleniyor", üç bağımsız yüklemin kesişimidir — keşif mekânı bulur, çözücü fiyatlar, yönlendirici ona karşı yürütür — ve bunların birleşimini bildiren bir tablo, kimse yalan söylemeden şişer. Kendi tablomuza uygulanınca: sekiz mekân türünden beşi uçtan uca çalışır (sabit-çarpım, yoğunlaştırılmış likidite, stableswap, Solidly ikilisi, singleton); cryptoswap keşif tarafından asla yayımlanmaz, weighted-pool türü sabit-çarpım gibi fiyatlanan bir takma addır ve dynamic fee, fee = 0 ile fiyatlar.

العربية — «مدعوم» هو اقتران ثلاثة محمولات مستقلة — الاكتشاف يجد المنصة، والمحلّل يسعّرها، والموجّه ينفّذ ضدها — والجدول الذي يبلغ عن اتحادها يتضخم دون أن يكذب أحد. مطبّقاً على جدولنا نحن: خمسة من ثمانية أنواع منصات تعمل من طرف إلى طرف (الجداء الثابت، السيولة المركّزة، stableswap، ثنائي Solidly، singleton)، بينما لا يصدر الاكتشاف cryptoswap أبداً، ونوع weighted-pool اسم مستعار يسعَّر كجداء ثابت، وdynamic fee يسعّر برسم = 0.

हिन्दी — "समर्थित" तीन स्वतंत्र विधेयों का संयोजन है — खोज venue को पाती है, सॉल्वर उसका दाम लगाता है, राउटर उसके विरुद्ध निष्पादित करता है — और उनका संघ बताने वाली तालिका बिना किसी के झूठ बोले फूल जाती है। हमारी अपनी तालिका पर लागू: आठ में से पाँच venue-प्रकार सिरे से सिरे तक चलते हैं (स्थिर-गुणनफल, संकेंद्रित तरलता, stableswap, Solidly द्वैत, singleton), जबकि cryptoswap खोज से कभी उत्सर्जित नहीं होता, weighted-pool प्रकार स्थिर-गुणनफल की तरह क़ीमत लगाया जाने वाला उपनाम है, और dynamic fee की क़ीमत fee = 0 पर लगती है।

日本語 — 「対応済み」は三つの独立した述語の連言です。ディスカバリーが会場を見つけ、ソルバーが価格付けし、ルーターがそれに対して実行する。三つの和集合を報告する表は、誰も嘘をつかずに膨らみます。当方の表に適用すると、八種の会場のうち五種が端から端まで動きます(定積、集中流動性、stableswap、Solidlyデュアル、シングルトン)。一方cryptoswapはディスカバリーから一度も発行されず、weighted-poolは定積として価格付けされる別名にすぎず、dynamic feeはfee = 0で価格付けします。

中文 — "已支持"是三个独立谓词的合取——发现层找到场所、求解器为其定价、路由器对其执行——报告其并集的表格无需任何人说谎就会膨胀。用在我们自己的表上:八种场所类型中有五种端到端可用(恒定乘积、集中流动性、stableswap、Solidly 双式、单例),而 cryptoswap 从未被发现层发出,weighted-pool 类型只是按恒定乘积定价的别名,dynamic fee 则按 fee = 0 定价。

한국어 — "지원됨"은 독립된 세 술어의 논리곱입니다 — 디스커버리가 장소를 찾고, 솔버가 가격을 매기고, 라우터가 실행합니다 — 셋의 합집합을 보고하는 표는 아무도 거짓말하지 않아도 부풀어 오릅니다. 우리 표에 적용하면 여덟 장소 종류 중 다섯이 끝에서 끝까지 작동합니다(상수곱, 집중 유동성, stableswap, Solidly 듀얼, 싱글턴). 반면 cryptoswap은 디스커버리가 결코 방출하지 않고, weighted-pool 종류는 상수곱으로 가격이 매겨지는 별칭이며, dynamic fee는 fee = 0으로 가격을 매깁니다.

Bahasa Indonesia — "Didukung" adalah konjungsi tiga predikat independen — penemuan menemukan venue, solver menghargainya, router mengeksekusi terhadapnya — dan tabel yang melaporkan gabungannya menggelembung tanpa ada yang berbohong. Diterapkan pada tabel kami sendiri: lima dari delapan jenis venue bekerja ujung ke ujung (produk-konstan, likuiditas terkonsentrasi, stableswap, dual Solidly, singleton), sementara cryptoswap tak pernah diemisikan penemuan, jenis weighted-pool adalah alias yang dihargai sebagai produk-konstan, dan dynamic fee menghargai dengan fee = 0.

বাংলা — "সমর্থিত" তিনটি স্বাধীন বিধেয়র সংযোগ — আবিষ্কার ভেনু খুঁজে পায়, সলভার দাম দেয়, রাউটার তার বিপরীতে নির্বাহ করে — আর তাদের সংযোগফল জানানো তালিকা কারও মিথ্যা ছাড়াই ফুলে ওঠে। আমাদের নিজেদের তালিকায় প্রয়োগে: আট ভেনু-জাতের পাঁচটি প্রান্ত-থেকে-প্রান্ত কাজ করে (স্থির-গুণফল, কেন্দ্রীভূত তারল্য, stableswap, Solidly দ্বৈত, singleton), অথচ cryptoswap আবিষ্কার থেকে কখনো নির্গত হয় না, weighted-pool জাতটি স্থির-গুণফল হিসেবে দাম দেওয়া এক ছদ্মনাম, আর dynamic fee দাম দেয় fee = 0 ধরে।

Filipino — Ang "suportado" ay pagsasama ng tatlong malayang predicate — natatagpuan ng discovery ang venue, pinepresyuhan ito ng solver, isinasagawa ito ng router — at ang talahanayang nag-uulat ng kanilang union ay lumalaki nang walang nagsisinungaling. Inilapat sa sarili naming talahanayan: lima sa walong uri ng venue ang gumagana nang dulo-sa-dulo (constant-product, concentrated liquidity, stableswap, Solidly dual, singleton), habang ang cryptoswap ay hindi kailanman inilalabas ng discovery, ang uri ng weighted-pool ay alias na pinepresyuhan bilang constant product, at ang dynamic fee ay nagpepresyo sa fee = 0.

Integration counts are the most reliably inflated number in this industry, and the inflation is usually not a lie. It is a category error. "Supported" is treated as a single predicate over a venue family when it is the conjunction of three independent ones, and a table that reports any of the three as if it were all of them will overcount without anybody deciding to overcount.

The three stages are: discovery has to be able to find the venue, the solver has to be able to price it, and the router has to be able to execute against it. A family that fails any one of the three is not supported. Listing it as such is the ordinary way this number gets inflated, and it is checkable — the failure modes are different at each stage and each leaves a different trace in the source.

The decomposition, and what each stage can fail at independently

Discovery failure means the scanner never emits an identifier for that family, so no route is ever assembled that uses it. The pricing and execution code can be present and correct and it will never run. This failure is invisible from the code alone: every function you read works.

Pricing failure means the solver produces a number for the family that does not match what the venue will actually do. This is the dangerous stage, because a wrong model produces a confident number rather than an error. Execution failure means the swap call itself does not work — the loudest and least harmful of the three, because it reverts.

Applied to our own venue table, five of eight kinds work end to end and are what the protocol genuinely trades against: constant-product, concentrated-liquidity, stableswap, the Solidly-style volatile/stable dual, and the singleton style. The other three fail at one stage each, and they are the honest part of the table.

kind                    found     priced                executed
constant product         yes       yes                   yes
concentrated liquidity   yes       yes                   yes
stableswap               yes       yes                   yes
Solidly dual             yes       yes                   yes
singleton                yes       yes                   yes
dynamic fee              yes       FLAWED (fee = 0)      yes
weighted-pool alias      yes       as constant product   as constant product
cryptoswap               NO        yes                   yes

The three failing rows, named

The cryptoswap kind is unreachable. The scanner that discovers this family labels everything it finds as the plain stable kind, so the cryptoswap identifier is never emitted by discovery. The pricing and execution code for it is present and correct; nothing ever produces a route that uses it. It is dead weight, not a feature — and a reviewer reading only the pricing library would conclude the opposite.

The weighted-pool kind is an alias, not an integration. There is no weighted-pool math anywhere in the source. A venue registered under that identifier is priced and executed as an ordinary constant-product pair, which is correct behaviour only if the venue actually is one. This is the row we would most like to have found differently, and mislabelling it as support would be worse than dead code: dead code does nothing, while a wrong model produces a number a user acts on.

The dynamic-fee kind prices with the wrong fee. Venues of that family are registered with their fee forced to a sentinel value of zero, and that zero flows into the concentrated-liquidity quote. The quote therefore prices the trade as though the venue charged nothing, while execution asks the venue and pays whatever its live fee turns out to be. The realised output is short by exactly that fee, systematically and in one direction. It is reachable, it executes, and its quote is optimistic — which is a genuine quote-versus-execution seam in a protocol whose central claim is the absence of one. It was found while sourcing the venue chapter and is reported here rather than after somebody else finds it.

The second, sharper distinction: wired versus demonstrated

The table above says which families the code supports. It does not say which have been observed working against real chain state, and those are different claims — the first is a property of the source, the second is a property of the evidence. As of the 2026-08-24 fidelity matrix, fork execution covers every working family: constant-product, concentrated liquidity under both the Uniswap and Algebra state layouts, Solidly, and the V4 singleton — native ETH included — quote to settlement, preview against delivery, measured at 0–1 bps.

So: four families are wired, and four have been demonstrated — the two numbers finally agree, which is what publishing both was always meant to force. The distinction stays in print because the habit is the point: wired is a property of source, demonstrated is a property of evidence, and a protocol should always tell you which of the two it is claiming.

Why the non-fork test suite cannot close this gap

The obvious objection is that the whole test suite covers all of it, and the objection fails for a structural reason worth understanding, because it generalises well beyond our repository. The mock venues used throughout the non-fork suites compute their output by calling the very same library function the quoter calls — one of them says so in its own header, that quote and execution agree by construction.

Every quote-versus-execution assertion outside the fork tests therefore reduces to checking that a function equals itself. It cannot fail. It is not a weak test; it is a test that establishes nothing at all about the property this protocol most wants to claim, and it will stay green through any change that breaks that property in the same way on both sides. A green run proves that the policy invariants and the emission mathematics hold. It does not prove that the quote a user is shown is the one that executes.

The exception is worth naming because it is the strongest test in either repository: one fork suite prices against a real venue's own pricing function on real chain state, which is a genuine independent oracle rather than a mirror. That single suite is the entire evidentiary basis for the demonstrated column, which is why the column is four and not eight.

The evidence ladder, and what a green badge is worth

The general form of the argument is a ladder, and every rung is a strictly weaker claim than the one above it. Code exists for a family. The code type-checks and deploys. A unit test exercises it against a mock. A unit test exercises it against a mock that is not derived from the code under test. A fork test exercises it against the real contract at a live block. A fork test pinned to a specific block, so the result is reproducible rather than drifting with the chain.

Two of our sixteen fork suites are pinned to a specific block; the rest would drift with the chain, which means a future failure could be a chain change rather than a regression and a future pass could be luck. And on the verification side generally, what matters is which jobs can block a merge, which merely report, and which pass without having tested anything. In the router repository the build, the non-fork suite, the fork tests, a bytecode size guard set at 24,000 bytes — deliberately stricter than the 24,576-byte protocol limit — a static-analysis gate that fails on high-severity findings, and two symbolic proofs under Halmos all block. A third symbolic specification times out rather than completing, and a timeout is not a proof. A commercial verification job exits successfully when no licence key is present, so a green check there means the job was skipped. In the staking repository there is no prover and no static analyser at all.

How to apply this to any protocol, including this one

For each integration a protocol advertises, ask the three questions separately and demand a different artefact for each. For found: point me at the discovery code path that emits this family's identifier, and at a transaction where it did. For priced: point me at the pricing branch, and tell me whether it calls the venue's own function or reimplements it — reimplementation is where quotes and executions come to disagree, and asking removes an entire class of error at the cost of a second call. For executed: point me at a fork test, pinned to a block, that swaps through it.

Then ask the question that catches the tautology: is the thing the test compares against derived from the code under test? If the expected value and the actual value flow from the same function, the test is a mirror. That single question invalidated most of our own quote-versus-execution coverage, and writing the missing test — one that compares a preview against an actual execution — is the single highest-value piece of work outstanding on our codebase.

Do not trust this page — reproduce it

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

for any family you care about, find the fork test that swaps through it and check whether it is pinned to a block; then check whether the expected value it asserts against is computed by the same library the code under test calls — if it is, the test is a mirror and proves nothing
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). Wired is not demonstrated: the difference between a venue family the code supports and one exercised against real chain state. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/wired-is-not-demonstrated/
@misc{blazephoenix_wired_is_not_demonstrated,
  title  = {Wired is not demonstrated: the difference between a venue family the code supports and one exercised against real chain state},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/wired-is-not-demonstrated/},
  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 Evidence standards · 6 / 8
Metrological Design: the theory behind a contract that measures instead of believing ›Metrological Design is the BlazePhoenix engineering method: build the contract as an instrument. Code that believes is attack surface; code that measures is defence. The three rules — one morphism, measured coordinates, monotone inputs — and the real mechanisms that instantiate them.10 min

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

Go to APP