On a few Ethereum pairs — stablecoins and correlated assets — our quote can sit below the market. The reason is a deliberate trust boundary, not arithmetic: that depth trades on venue families we excised by choice into our Ethereum registry. How to tell if it affects your trade.
BlazePhoenix Engineering · updated 2026-10-05 · data through 2026-10-11 · 7 min · written from the deployed bytecode
| Level | Intermediate |
|---|---|
| Reading time | 7 min |
| Sections | 5 |
| Sources cited | 1 |
| Updated | 2026-10-05 |
By Mitra (@Sigmacrit) — anonymous developer of the BlazePhoenix protocol. The code is the résumé.
English — On a small set of Ethereum pairs — stablecoins and correlated assets — our quote can be worse than the market. The cause is coverage: that depth lives on Curve and Balancer, not yet wired into our Ethereum registry.
Português — Num pequeno conjunto de pares Ethereum — stablecoins e ativos correlacionados — a nossa cotação pode ser pior que o mercado. A causa é cobertura: essa profundidade está na Curve e na Balancer, ainda não ligadas ao nosso registo em Ethereum.
Español — En un pequeño conjunto de pares de Ethereum — stablecoins y activos correlacionados — nuestra cotización puede ser peor que el mercado. La causa es la cobertura: esa profundidad está en Curve y Balancer, aún no conectadas a nuestro registro en Ethereum.
Français — Sur quelques paires Ethereum — stablecoins et actifs corrélés — notre cotation peut être moins bonne que le marché. La cause est la couverture : cette profondeur est sur Curve et Balancer, pas encore reliées à notre registre Ethereum.
Deutsch — Bei wenigen Ethereum-Paaren — Stablecoins und korrelierte Assets — kann unsere Quote schlechter sein als der Markt. Die Ursache ist Abdeckung: Diese Tiefe liegt auf Curve und Balancer, die in unserem Ethereum-Register noch nicht eingetragen sind.
Русский — На небольшом наборе пар Ethereum — стейблкоины и коррелированные активы — наша котировка может быть хуже рынка. Причина в покрытии: эта глубина на Curve и Balancer, ещё не подключённых к нашему реестру в Ethereum.
Türkçe — Az sayıda Ethereum paritesinde — stablecoin ve birbirine bağlı varlıklar — fiyatımız piyasadan kötü olabilir. Sebep kapsam: o derinlik Curve ve Balancer'da ve bunlar Ethereum kaydımıza henüz bağlı değil.
العربية — في مجموعة صغيرة من أزواج إيثريوم — العملات المستقرة والأصول المترابطة — قد يكون سعرنا أسوأ من السوق. السبب هو التغطية: تلك السيولة على Curve وBalancer، وهما غير مسجّلتين بعد في سجلّنا على إيثريوم.
हिन्दी — कुछ Ethereum जोड़ियों में — स्टेबलकॉइन और सहसंबद्ध संपत्तियाँ — हमारा कोट बाजार से खराब हो सकता है। कारण कवरेज है: वह गहराई Curve और Balancer पर है, जो अभी हमारी Ethereum रजिस्ट्री से जुड़ी नहीं हैं।
日本語 — 一部のEthereumペア（ステーブルコインや相関資産）では、当社の見積もりが市場より劣ることがあります。原因はカバレッジです。その厚みはCurveとBalancerにあり、Ethereumのレジストリにまだ接続していません。
中文 — 在少数以太坊交易对上（稳定币与相关性资产），我们的报价可能劣于市场。原因是覆盖范围：这些深度位于 Curve 与 Balancer，目前尚未接入我们在以太坊的注册表。
한국어 — 일부 이더리움 페어(스테이블코인과 상관 자산)에서는 우리 견적이 시장보다 나쁠 수 있습니다. 원인은 커버리지입니다. 그 유동성은 Curve와 Balancer에 있으며 아직 이더리움 레지스트리에 연결되지 않았습니다.
Bahasa Indonesia — Pada sejumlah kecil pasangan Ethereum — stablecoin dan aset berkorelasi — kuotasi kami bisa lebih buruk dari pasar. Penyebabnya cakupan: kedalaman itu ada di Curve dan Balancer, yang belum terhubung ke registri Ethereum kami.
বাংলা — কিছু ইথেরিয়াম জোড়ায় — স্টেবলকয়েন ও সম্পর্কিত সম্পদ — আমাদের কোট বাজারের চেয়ে খারাপ হতে পারে। কারণ কভারেজ: সেই গভীরতা Curve ও Balancer-এ, যা এখনও আমাদের ইথেরিয়াম রেজিস্ট্রিতে যুক্ত নয়।
Filipino — Sa iilang pares sa Ethereum — stablecoin at magkaugnay na asset — maaaring mas mababa ang quote namin kaysa merkado. Ang dahilan ay saklaw: nasa Curve at Balancer ang lalim na iyon, hindi pa nakakabit sa aming registry sa Ethereum.
If you quote certain Ethereum pairs here and compare against a price aggregator, you may find our number is worse. We would rather explain that than let you discover it mid-trade, so here is the actual reason.
It is not a pricing error, and it is not the fee. It is coverage: a route can only be as good as the venues it is allowed to consider, and on Ethereum the deepest liquidity for some pairs sits on venues our registry does not currently include.
The pattern is consistent: stablecoin-to-stablecoin pairs, and pairs between assets that track each other closely — a liquid staking token against the asset it represents, or two wrappers of the same underlying. Those pairs migrated years ago to venues whose curves are purpose-built for correlated assets, because a constant-product pool is a poor instrument for trading two things that are meant to have the same price.
On Ethereum the deepest correlated-asset flow trades on the Curve and Balancer families — venues this engine deliberately does not route. If most of a pair's depth is there and we are routing across the venues we do cover, our best available route can trail the market's best — and the honest thing is to show you our real number rather than a market average we cannot actually fill at.
The mathematics was never the gap — those curves were fully integrated and working. They were removed anyway, in a trust-boundary hardening round, because of what supporting them required: the Router's only token approval, a depth figure attested by callers instead of measured from pools, and an exception in the registry's pair-authenticity proof — three attack surfaces, each the last of its class in the codebase. When coverage and verifiability conflict here, verifiability wins; coverage bought with an unmeasured trust assumption is not coverage.
What is missing is registry coverage on Ethereum: those venues are not currently wired into the Hub on that chain, so the Solver never sees their pools as candidates. That is a configuration and verification job — each factory has to be registered and its pool derivation proven — not a rewrite. It is on the roadmap, and we are not going to put a date on it here that we might miss.
Two checks, both quick. First, the route: our quote shows how many legs it used and across which venues. If your pair is a stable-to-stable or a correlated pair and the route looks thin, that is the case described here.
Second, compare directly. Quote the pair here and on any venue you like, at the same size in the same minute, and look at tokens received. If the difference is material, take the better route — we mean that. A tool that tells you when someone else is better on a specific pair is a tool you can believe when it says it is better on the rest.
For the majority of pairs — volatile tokens, the long tail, anything trading mainly on constant-product and concentrated-liquidity venues — this does not apply, and our on-chain-computed quote is exactly what the Router will realise.
Compare like for like, same minute, same size (USDC → USDT on Ethereum):
curl 'https://blazephoenix.xyz/api/quote/prepare?chain=eth&in=USDC&out=0xdAC17F958D2ee523a2206206994597C13D831ec7&amountIn=1000000000'
# run the returned eth_call on your Ethereum node, then POST it to /api/quote/decode
Then quote the same pair wherever you normally trade, and compare
the raw output amounts — not percentages.Because the alternative is that you find out by losing a few basis points and concluding we are either careless or dishonest. Neither is true, and neither is worth the silence.
A protocol that names its own coverage gaps in public is making a claim you can test: that when we say a number is the best we can find, that statement means something. The gap is real, it is bounded to a describable set of pairs, and it will close.
Every claim above is checkable against the chain. Start here:
Quote a stable-to-stable Ethereum pair here and on any other venue within the same minute, then compare the raw output amounts — the gap this article describes is the one you will see, and only on those pairsLicensed CC BY 4.0 — quote, translate and reuse freely, including commercially, with attribution and a link. Copy a ready-made citation:
BlazePhoenix (2026). Why some Ethereum pairs quote differently here than the price you see elsewhere. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/ethereum-pair-price-differences@misc{blazephoenix_ethereum_pair_price_differences,
title = {Why some Ethereum pairs quote differently here than the price you see elsewhere},
author = {BlazePhoenix},
year = {2026},
url = {https://blazephoenix.xyz/learn/ethereum-pair-price-differences},
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). Standards cited: EIP-20
Questions, a partnership or a bug to report? Contact us or email contact@blazephoenix.xyz