Connect
Cover: A quote is a statement about the past: what an in-transaction solver fixes, and what it does not

A quote is a statement about the past: what an in-transaction solver fixes, and what it does not

Why can a fill differ from its quote, even with an in-transaction solver?

Three independent sources of drift separate a quote from a fill. Solving the route inside the executing transaction removes exactly one of them. The other two survive — and our own preview surface is the clearest case of a guarantee restated where it cannot be enforced.

Known formally as The quote-execution seam in the BlazePhoenix whitepaper.

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

At a glance
LevelAdvanced
Formal nameThe quote-execution seam
Reading time11 min
Sections7
Updated2026-08-13

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

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

English — The gap between a quote and a fill has three independent sources — temporal drift (reserves moved), search drift (the route search was only as good as its budget) and model drift (approximations applied in between) — and solving the route inside the executing transaction removes exactly one: temporal drift becomes structurally absent, search drift changes owner from the operator's budget to the contract's smaller one, and model drift survives untouched, including on BlazePhoenix's own preview surface.

Português — O fosso entre uma cotação e um fill tem três fontes independentes — deriva temporal (as reservas moveram-se), deriva de busca (a busca da rota vale o orçamento que teve) e deriva de modelo (aproximações aplicadas pelo meio) — e resolver a rota dentro da transação que executa remove exatamente uma: a deriva temporal fica estruturalmente ausente, a de busca troca de dono do orçamento do operador para o menor do contrato, e a de modelo sobrevive intocada, incluindo na própria superfície de preview da BlazePhoenix.

Español — La brecha entre una cotización y un fill tiene tres fuentes independientes — deriva temporal (las reservas se movieron), deriva de búsqueda (la búsqueda de la ruta valió lo que su presupuesto) y deriva de modelo (aproximaciones aplicadas en medio) — y resolver la ruta dentro de la transacción que ejecuta elimina exactamente una: la deriva temporal queda estructuralmente ausente, la de búsqueda cambia de dueño del presupuesto del operador al menor del contrato, y la de modelo sobrevive intacta, incluso en la propia superficie de preview de BlazePhoenix.

Français — L'écart entre un devis et un fill a trois sources indépendantes — dérive temporelle (les réserves ont bougé), dérive de recherche (la recherche de route valait son budget) et dérive de modèle (des approximations appliquées entre les deux) — et résoudre la route dans la transaction qui exécute en supprime exactement une : la dérive temporelle devient structurellement absente, la dérive de recherche change de propriétaire, du budget de l'opérateur au budget plus petit du contrat, et la dérive de modèle survit intacte, y compris sur la propre surface de preview de BlazePhoenix.

Deutsch — Die Lücke zwischen Quote und Fill hat drei unabhängige Quellen — zeitliche Drift (Reserven bewegten sich), Such-Drift (die Routensuche war nur so gut wie ihr Budget) und Modell-Drift (dazwischen angewandte Näherungen) — und die Route innerhalb der ausführenden Transaktion zu lösen beseitigt genau eine: Zeitliche Drift ist strukturell abwesend, Such-Drift wechselt den Besitzer vom Budget des Betreibers zum kleineren des Contracts, und Modell-Drift überlebt unberührt, auch auf BlazePhoenix' eigener Preview-Oberfläche.

Русский — Разрыв между котировкой и исполнением имеет три независимых источника: временной дрейф (резервы сдвинулись), поисковый дрейф (поиск маршрута хорош ровно настолько, насколько его бюджет) и модельный дрейф (применённые между ними приближения); решение маршрута внутри исполняющей транзакции убирает ровно один — временной дрейф структурно отсутствует, поисковый меняет владельца с бюджета оператора на меньший бюджет контракта, а модельный выживает нетронутым, в том числе на собственной превью-поверхности BlazePhoenix.

Türkçe — Kotasyon ile dolum arasındaki boşluğun üç bağımsız kaynağı vardır — zamansal kayma (rezervler oynadı), arama kayması (rota araması ancak bütçesi kadar iyiydi) ve model kayması (arada uygulanan yaklaşıklıklar) — ve rotayı yürüten işlemin içinde çözmek tam olarak birini kaldırır: zamansal kayma yapısal olarak yok olur, arama kayması sahibini operatörün bütçesinden sözleşmenin daha küçük bütçesine değiştirir ve model kayması, BlazePhoenix'in kendi önizleme yüzeyi dahil, el değmeden kalır.

العربية — للفجوة بين التسعيرة والتنفيذ ثلاثة مصادر مستقلة — انحراف زمني (تحركت الاحتياطيات)، وانحراف بحث (بحث المسار بجودة ميزانيته فقط)، وانحراف نموذج (تقريبات طُبّقت بينهما) — وحلّ المسار داخل المعاملة المنفِّذة يزيل واحداً بالضبط: الانحراف الزمني يغيب بنيوياً، وانحراف البحث يبدّل مالكه من ميزانية المشغّل إلى ميزانية العقد الأصغر، وانحراف النموذج يبقى دون مساس، حتى على سطح المعاينة الخاص بـBlazePhoenix نفسه.

हिन्दी — कोट और फ़िल के बीच की खाई के तीन स्वतंत्र स्रोत हैं — कालिक बहाव (रिज़र्व हिल गए), खोज-बहाव (रूट-खोज उतनी ही अच्छी जितना उसका बजट) और मॉडल-बहाव (बीच में लगे सन्निकटन) — और रूट को निष्पादित करने वाली ट्रांज़ैक्शन के भीतर हल करना ठीक एक को हटाता है: कालिक बहाव संरचनात्मक रूप से अनुपस्थित हो जाता है, खोज-बहाव का मालिक ऑपरेटर के बजट से बदलकर कॉन्ट्रैक्ट का छोटा बजट हो जाता है, और मॉडल-बहाव अछूता बचा रहता है — BlazePhoenix की अपनी प्रीव्यू-सतह समेत।

日本語 — 見積もりと約定のあいだの隔たりには三つの独立した源があります。時間的ドリフト(リザーブが動いた)、探索ドリフト(経路探索は予算の分だけしか良くない)、モデルドリフト(あいだに挟まる近似)。実行するトランザクションの内部で経路を解くことが取り除くのは、ちょうど一つだけです。時間的ドリフトは構造的に不在となり、探索ドリフトは持ち主を運営者の予算からコントラクトのより小さな予算へ替え、モデルドリフトは手つかずのまま生き残ります。BlazePhoenix自身のプレビュー面も例外ではありません。

中文 — 报价与成交之间的落差有三个独立来源——时间漂移(储备变了)、搜索漂移(路由搜索的好坏只等于其预算)与模型漂移(两者之间施加的近似)——而在执行交易内部求解路由恰好只消除其一:时间漂移在结构上不复存在,搜索漂移的主人从运营者的预算换成合约更小的预算,模型漂移则原封不动地幸存,包括在 BlazePhoenix 自己的预览面上。

한국어 — 견적과 체결 사이의 간극에는 세 가지 독립적 원천이 있습니다 — 시간 드리프트(준비금이 움직임), 탐색 드리프트(경로 탐색은 그 예산만큼만 훌륭함), 모델 드리프트(그 사이 적용된 근사들). 실행하는 트랜잭션 안에서 경로를 푸는 것은 정확히 하나만 제거합니다. 시간 드리프트는 구조적으로 부재하게 되고, 탐색 드리프트는 주인이 운영자의 예산에서 컨트랙트의 더 작은 예산으로 바뀌며, 모델 드리프트는 BlazePhoenix 자신의 프리뷰 표면을 포함해 손대지 않은 채 살아남습니다.

Bahasa Indonesia — Celah antara kuotasi dan eksekusi punya tiga sumber independen — simpangan temporal (cadangan bergerak), simpangan pencarian (pencarian rute hanya sebaik anggarannya), dan simpangan model (aproksimasi yang diterapkan di antaranya) — dan menyelesaikan rute di dalam transaksi yang mengeksekusi menghapus tepat satu: simpangan temporal jadi absen secara struktural, simpangan pencarian berganti pemilik dari anggaran operator ke anggaran kontrak yang lebih kecil, dan simpangan model bertahan tak tersentuh, termasuk di permukaan pratinjau BlazePhoenix sendiri.

বাংলা — কোট আর ফিলের মধ্যকার ফাঁকের তিনটি স্বাধীন উৎস — কালিক সরণ (রিজার্ভ নড়েছে), অনুসন্ধান-সরণ (রুট-অনুসন্ধান তার বাজেট যতটা, ততটাই ভালো) আর মডেল-সরণ (মাঝে প্রয়োগ করা আসন্নায়ন) — এবং নির্বাহকারী ট্রানজ্যাকশনের ভেতরে রুট সমাধান ঠিক একটিকে সরায়: কালিক সরণ কাঠামোগতভাবে অনুপস্থিত হয়, অনুসন্ধান-সরণের মালিক বদলে অপারেটরের বাজেট থেকে কন্ট্রাক্টের ছোট বাজেট হয়, আর মডেল-সরণ অক্ষত টিকে থাকে — BlazePhoenix-এর নিজের প্রিভিউ-পৃষ্ঠসহ।

Filipino — Ang agwat sa pagitan ng quote at fill ay may tatlong malayang pinagmulan — temporal na paggalaw (gumalaw ang mga reserba), paggalaw ng paghahanap (ang paghahanap ng ruta ay kasinghusay lamang ng badyet nito) at paggalaw ng modelo (mga approximation na inilapat sa pagitan) — at ang paglutas ng ruta sa loob ng nagsasagawang transaksyon ay nag-aalis ng eksaktong isa: nagiging estruktural na wala ang temporal na paggalaw, nagpapalit ng may-ari ang paggalaw ng paghahanap mula sa badyet ng operator tungo sa mas maliit na badyet ng kontrata, at nananatiling buo ang paggalaw ng modelo, kabilang sa sariling preview surface ng BlazePhoenix.

A quote is a promise about a trade that has not happened yet. Every aggregator makes one, and in almost every case the promise is produced by different machinery than the trade: a service computes the route off-chain, and the contract on-chain executes the route it was handed. The contract does not choose; it checks. Whether the route it received was the best one available is not something it can know, and therefore not something a user can verify.

That is a sound engineering arrangement and it is why aggregators are fast and cheap. It has one consequence rarely stated plainly: the strongest claim such a system can make is that its operator is honest. The constraints it enforces on-chain — a minimum output, a deadline — bound how badly the trade can go, but say nothing about whether a better route existed and was not offered.

Three sources of drift, which are usually collapsed into one

The gap between a quote and a fill is not usually fraud. It is drift, and it has three ordinary and independent sources that a reader should keep apart, because a mechanism that closes one may leave the others untouched.

Temporal drift: the quote is computed at one moment against reserves that move continuously, so by the time the transaction lands, the pool it priced is a different pool. Search drift: the route was chosen by a search over a snapshot, and the search is only as exhaustive as the operator's budget for running it — a fact invisible in the output, since a worse route and a better route are both just numbers. Model drift: any correction applied between the two — a slippage buffer, a fee taken on the way, an approximation used because the exact computation was too expensive — is applied by code the user did not read, to a number the user cannot reproduce.

None of that requires bad intent. All of it is invisible. And the three have different remedies, which is the point of separating them.

source of drift    what it is                              what an in-frame solver does
temporal           reserves moved between quote and fill    ELIMINATES (same frame)
search             the search was as good as the budget     ELIMINATES the operator's budget;
                                                            replaces it with the contract's
model              approximation between quote and fill     UNTOUCHED

What the on-chain-solving entry point actually removes

The protocol offers an entry point that takes six scalars — the two tokens, the amount, a minimum, a recipient, a deadline — and works out the route itself, calling the solver in the same frame before any tokens move. The thing that chooses is the thing that trades. Temporal drift between the routing decision and the execution is not reduced; it is structurally absent, because there is no interval. And the route can be re-derived by anyone from the same public state, because it was derived from that state.

Search drift changes character rather than disappearing. The operator's search budget stops mattering and the contract's budget starts mattering instead, and the contract's is smaller. A single-pass allocation over a small fixed set of topologies is not what an unconstrained off-chain search would find. That is the trade stated in the direction that does not flatter us: the distinctive entry point costs the most gas and delivers the least polished routing, and what it buys is a route no operator produced.

It is also worth attributing the protocol's other properties to the right half, because the temptation runs the other way. The output floors, the enforcement against measured balance deltas, the survival of fee-on-transfer tokens and the authentication of venue callbacks all belong to the ordinary settlement side, and a conventional aggregator could adopt every one of them.

Model drift is the one that survives, and we have a live instance

Execution always asks the venue: the swap is performed by the venue's own code and the result is established by measuring balances. Quoting is where a choice exists. For stable-curve, Solidly-style and cryptoswap venues the quote is obtained by calling the venue's own pricing function. For constant-product, concentrated-liquidity and singleton venues the quote is computed by the protocol from the venue's reserves using the standard formula for that family.

Modelling is how a quote and an execution come to disagree. A model is correct until the venue differs from it in some corner — an unusual fee tier, a hook, a rounding convention — and the disagreement reaches the user as receiving less than they were shown. Asking removes that class of error; computing accepts it in exchange for not having to call the venue twice.

Our live instance is the dynamic-fee family. Those venues are registered with their fee forced to a sentinel value of zero, and that zero flows into the concentrated-liquidity quote, so the quote prices the trade as though the venue charged nothing while execution pays whatever the live fee turns out to be. The realised output is short by exactly that fee. Solving in-frame does not help: both the quote and the execution happen in the same transaction and they still disagree, because the disagreement is in the model rather than in the interval.

Measure, never declare — the discipline that bounds model drift

What limits the damage is that amounts are established by measuring balances before and after, not by trusting what a function returned or what a caller asserted. The output of a swap is a balance delta on the router, not the number the pool claimed to send. This is also what lets tokens that take a fee on transfer be handled without a separate accounting path: there is no declared amount to be wrong.

The same principle governs the floor. After execution, the router re-derives its floor from the impact it actually measured and the way the amounts it was handed actually split across legs, anchored to a quote taken in the same frame — a value no caller can forge, because no caller supplies it. A floor supplied in calldata can only make that number stricter. That is the difference between a contract that executes a route and one that enforces a policy while executing it.

The qualifications belong in the same paragraph as the guarantee, because a floor is exactly the kind of promise where the exceptions are the content. The reference is the final hop's quote at execution time, not the quote the user was shown — between the two sits everything the market did in the interval. The check runs before the protocol fee is applied, so the floor bounds the pre-fee amount rather than the delivered one. And the guard is inert when that reference is zero. The compact statement — that the floor never falls below 80% of the user's quote — is false in three separate ways, and a reader who took the compact version would be misled about a safety parameter.

The preview surface: a guarantee restated where nothing can enforce it

There is a read-only surface that returns a preview of a trade: expected output, fee, a floor, a minimum, a gas estimate. Wallets and integrators read it, and every number in it is something someone will act on. We audited it against what the router actually enforces, and the result is the most uncomfortable material in the corpus, because a preview that reads like a guarantee in a protocol whose central claim is the absence of a quote-versus-execution seam is exactly the failure we set out to avoid.

Of everything the preview returns, exactly one number binds: the minimum the caller supplies, and it binds only because the caller passes it again at execution and the router checks it against the recipient's actual balance change. The output, fee and route fields are indicative — honest computations of what the protocol expects, subject to everything that can change between the read and the transaction. The remainder read like guarantees and are not: the floor the preview reports is taken from the caller's own route data rather than derived by the protocol; the field named as the effective minimum omits the protocol floor entirely and is therefore not the bound the router applies; the gas estimate is consumed by nothing anywhere in the system; two route-classification fields are returned as fixed zeros in every case; and a field named as a safety buffer has no counterpart in the router at all.

Two divergences cost money rather than merely confusing. The preview function whose name promises an exact figure falls back to scaling the expected output linearly when it cannot compute the exact one, and returns no flag saying it did — a caller cannot distinguish an exact answer from an approximation. And the preview's output figure is gross, before the protocol fee of 28 bps, while the integration notes tell integrators to derive their minimum from it. An integrator who follows that advice literally sets a minimum the trade cannot meet, or a minimum loose enough to absorb the fee twice.

What an integrator should do today

These are disclosed rather than fixed, and the register of open findings names each one. The correct practice in the meantime is simple and is right regardless of our defects: derive your minimum from your own price expectation, not from any field in a preview — ours or anyone's — and treat every other number in a preview as an estimate.

The reason that advice is more than caution is the failure mode a hostile or compromised interface has available. The caller supplies the route, the recipient and the minimum, and that minimum is the quantity every other bound falls back to. A hostile interface does not need to break any of our bounds; it only needs to propose a minimum that is non-zero but terrible, which passes every check the contract performs, because the contract cannot know what the user would have chosen. Our refusal to accept a zero minimum — where the reference implementation the industry copies accepts zero and proceeds — is necessary and nowhere near sufficient. What exists against it is an execution proof emitted on every swap, carrying the quote, the realised amount and the floor that was applied, which makes the attack detectable after the fact by anyone including the victim. That is worth having and it is not prevention.

Do not trust this page — reproduce it

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

call the preview off-chain, then execute the same trade and compare the emitted swap event — quote, realised amount and applied floor are all on-chain — against what the preview returned; that comparison is the one test our own suite does not contain
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 quote is a statement about the past: what an in-transaction solver fixes, and what it does not. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/quotes-are-statements-about-the-past/
@misc{blazephoenix_quotes_are_statements_about_the_past,
  title  = {A quote is a statement about the past: what an in-transaction solver fixes, and what it does not},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/quotes-are-statements-about-the-past/},
  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 Execution semantics · 7 / 7
This was the last one in Execution semantics — back to the library ›

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

Go to APP