Connect
Cover: Anatomy of an execution receipt: what each field proves, and what it does not

Anatomy of an execution receipt: what each field proves, and what it does not

What does a settled swap publish on-chain, and what does each field prove?

Every settlement emits Swap, ExecutionProof and Fee. A worked example reads each field: the final hop's quote, the delivered amount measured at the recipient, the floor that had to be beaten, and the fee.

Known formally as Settlement events: Swap, ExecutionProof and Fee 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 — Every settlement publishes a receipt anyone can re-derive: the Router emits Swap, ExecutionProof and Fee, with the delivered amount measured at the recipient and the reference quote taken from the same frame as the execution. The receipt proves the recipient received that amount above both the protocol floor and the minimum the user set, not that the route was optimal.

Português — Cada liquidação publica um recibo que qualquer pessoa pode voltar a derivar: o Router emite Swap, ExecutionProof e Fee, com o montante entregue medido no destinatário e a cotação de referência retirada do mesmo frame da execução. O recibo prova que o destinatário recebeu esse montante acima do piso do protocolo e do mínimo definido pelo utilizador, não que a rota foi ótima.

Español — Cada liquidación publica un recibo que cualquiera puede volver a derivar: el Router emite Swap, ExecutionProof y Fee, con el importe entregado medido en el destinatario y la cotización de referencia tomada del mismo frame que la ejecución. El recibo prueba que el destinatario recibió ese importe por encima del piso del protocolo y del mínimo fijado por el usuario, no que la ruta fuera óptima.

Français — Chaque règlement publie un reçu que chacun peut re-dériver : le Router émet Swap, ExecutionProof et Fee, avec le montant livré mesuré chez le destinataire et la cotation de référence prise dans le même frame que l'exécution. Le reçu prouve que le destinataire a reçu ce montant au-dessus du plancher du protocole et du minimum fixé par l'utilisateur, pas que la route était optimale.

Deutsch — Jede Abwicklung veröffentlicht einen Beleg, den jeder nachrechnen kann: Der Router gibt Swap, ExecutionProof und Fee aus, wobei der gelieferte Betrag beim Empfänger gemessen und der Referenzkurs aus demselben Frame wie die Ausführung genommen wird. Der Beleg beweist, dass der Empfänger diesen Betrag über der Protokoll-Untergrenze und dem vom Nutzer gesetzten Minimum erhielt, nicht dass die Route optimal war.

Русский — Каждое исполнение публикует квитанцию, которую любой может вывести заново: Router эмитирует Swap, ExecutionProof и Fee, причём доставленная сумма измеряется у получателя, а эталонная котировка берётся из того же фрейма, что и исполнение. Квитанция доказывает, что получатель получил эту сумму выше нижней границы протокола и заданного пользователем минимума, но не что маршрут был оптимальным.

Türkçe — Her uzlaşma, herkesin yeniden türetebileceği bir makbuz yayımlar: Router Swap, ExecutionProof ve Fee olaylarını yayar; teslim edilen tutar alıcıda ölçülür, referans kotasyon ise yürütmeyle aynı frame'den alınır. Makbuz, alıcının bu tutarı hem protokol tabanının hem de kullanıcının belirlediği asgarinin üzerinde aldığını kanıtlar; rotanın en iyi olduğunu kanıtlamaz.

العربية — تنشر كل تسوية إيصالًا يستطيع أي شخص إعادة اشتقاقه: يُصدر الـ Router الأحداث Swap وExecutionProof وFee، ويُقاس المبلغ المسلَّم لدى المستلم ويؤخذ عرض السعر المرجعي من الإطار نفسه الذي جرى فيه التنفيذ. يثبت الإيصال أن المستلم تلقى ذلك المبلغ فوق الحد الأدنى للبروتوكول وفوق الحد الأدنى الذي حدده المستخدم، لا أن المسار كان الأمثل.

हिन्दी — हर सेटलमेंट एक रसीद प्रकाशित करता है जिसे कोई भी दोबारा निकाल सकता है: Router Swap, ExecutionProof और Fee emit करता है, जिनमें डिलीवर की गई राशि प्राप्तकर्ता पर मापी जाती है और संदर्भ कोट उसी फ़्रेम से लिया जाता है जिसमें निष्पादन हुआ। रसीद यह साबित करती है कि प्राप्तकर्ता को वह राशि प्रोटोकॉल फ़्लोर और उपयोगकर्ता द्वारा तय न्यूनतम, दोनों से ऊपर मिली, यह नहीं कि रूट सर्वोत्तम था।

日本語 — すべての決済は、誰でも再導出できるレシートを公開します。Router は Swap、ExecutionProof、Fee を emit し、引き渡し額は受取人で測定され、基準の見積もりは実行と同じフレームから取られます。レシートが証明するのは、受取人がその額をプロトコルのフロアとユーザーが設定した最小額の両方を上回って受け取ったことであり、ルートが最適だったことではありません。

中文 — 每次结算都会发布一张任何人都能重新推导的凭据:Router 会触发 Swap、ExecutionProof 和 Fee 事件,实际到账金额在接收方测量,参考报价取自与执行相同的帧。凭据证明的是接收方收到的该金额高于协议下限和用户设定的最低值,而不是证明路由是最优的。

한국어 — 모든 결제는 누구나 다시 유도할 수 있는 영수증을 공개합니다. Router는 Swap, ExecutionProof, Fee를 emit하며, 전달 금액은 수령인에서 측정되고 기준 견적은 실행과 같은 프레임에서 가져옵니다. 영수증이 증명하는 것은 수령인이 그 금액을 프로토콜 하한과 사용자가 정한 최소치 모두 위로 받았다는 점이지, 경로가 최적이었다는 점이 아닙니다.

Bahasa Indonesia — Setiap penyelesaian menerbitkan tanda terima yang dapat diturunkan ulang oleh siapa pun: Router memancarkan Swap, ExecutionProof, dan Fee, dengan jumlah yang diserahkan diukur di penerima dan kuotasi acuan diambil dari frame yang sama dengan eksekusi. Tanda terima membuktikan penerima menerima jumlah itu di atas batas bawah protokol dan minimum yang ditetapkan pengguna, bukan bahwa rutenya optimal.

বাংলা — প্রতিটি সেটলমেন্ট এমন একটি রসিদ প্রকাশ করে যা যে কেউ আবার নির্ণয় করতে পারে: Router Swap, ExecutionProof ও Fee emit করে, যেখানে বিতরণ করা পরিমাণ প্রাপকের কাছে মাপা হয় এবং রেফারেন্স কোট নেওয়া হয় নির্বাহের একই ফ্রেম থেকে। রসিদ প্রমাণ করে প্রাপক ওই পরিমাণ প্রোটোকল ফ্লোর ও ব্যবহারকারীর নির্ধারিত সর্বনিম্ন, দুটোর ওপরেই পেয়েছেন; রুট সর্বোত্তম ছিল তা নয়।

Filipino — Bawat settlement ay naglalathala ng resibong maaaring hanguing muli ng sinuman: naglalabas ang Router ng Swap, ExecutionProof at Fee, kung saan ang naihatid na halaga ay sinusukat sa tatanggap at ang reference quote ay kinukuha mula sa parehong frame ng execution. Pinatutunayan ng resibo na natanggap ng tatanggap ang halagang iyon na higit sa protocol floor at sa minimum na itinakda ng user, hindi na pinakamahusay ang ruta.

Short answer: every settlement publishes a receipt that anyone can re-derive. The Router emits `Swap`, `ExecutionProof` and a `Fee` event. The fields are measured, not declared: the delivered amount is read from the recipient's own balance, and the reference quote comes from the same frame as the execution.

Section 11.6 of the 2.4 whitepaper says how to read one without over-claiming. This article walks the fields, then a worked example, then lists what the receipt does not prove.

How a settlement closes

Settlement closes the frame the way it opened, by measurement. The Router takes its output-token delta against the entry baseline as the gross output, runs the floor check, charges the fee where the regime puts it, transfers the net to the recipient and measures the recipient's balance delta. It enforces `userMinOut` on that delivered amount, so a fee-on-transfer output token cannot slip the user below their bound (`RouterE(5)`).

It then reads the fee ledger once: a settlement that paid the protocol nothing is refused (`RouterE(15)`), and on an anchored route a second payment is refused (`RouterE(16)`). Only on the success path does it write to the Hub, once per executed leg. Nothing is written when the floor rejects.

The three events, field by field

`Swap(payer, tokenIn, tokenOut, amountIn, delivered, declaredLegs)` carries the gross amount the user handed over. `ExecutionProof(user, tokenOut, quoted, realized, floorUsed, blockNumber)` is the reference quote produced in the same frame as the execution, published as an on-chain series that anyone can re-derive by an `eth_call` to `findBestRoutePlan` at that block. `Fee(token, amount, toT1, toT2)` names the token and the split.

FieldWhat it isWhat it does not claim
userThe payer, never `msg.sender`That the payer and the recipient are the same address
quotedThe final hop's quoteIt proves the last hop, not the whole route
realizedWhat was delivered, measured at the recipientThat no better route existed
floorUsedThe protocol floor that had to be beaten, net of any transfer tax on the final transferA floor on the price you could have had
blockNumberThe block of the reference quoteAnything about other blocks

Source: Whitepaper 2.4, section 11.6; FACTOS section 7.

A worked example

The whitepaper's example 6 settles a two-hop route and emits `ExecutionProof(0xUSER, B, 1,000.000, 998.400, 933.600, N)` and one `Fee(WETH, 0.014, 0.0042, 0.0098)`. The table reads the numbers.

  1. quoted: 1,000.000 B, the final hop's in-frame quote at the WETH that actually arrived.
  2. realized: 998.400 B delivered to the recipient and measured there, which is 9,984 bps of the quote.
  3. floorUsed: 933.600 B, the floor of 9,336 bps applied to the quote. The fill sat 64.8 B above it.
  4. Distance to userMinOut: the trader set 990 B, so the fill cleared it by 8.4 B, which is 0.84 % of the quote.
  5. Fee: 0.014 WETH in one event, which is 28 bps of the 5.000 WETH that hop 0 produced, paid at hop 1's input. Nothing was taken from B.
QuantityValueCheck
realized / quoted998.400 / 1,000.0009,984 bps
realized - floorUsed998.400 - 933.60064.8 B
realized - userMinOut998.400 - 9908.4 B
Fee28 bps of 5.000 WETH0.014 WETH

Source: Whitepaper 2.4, section 11.6, worked example 6.

Reading delivered against quoted

Delivered minus quoted is the market's answer, not the protocol's. In the example the fee left earlier, in WETH, and no output-side cut exists on that route. A `Fee` event denominated in the output token appears only on a direct route into a bridge coin.

What the receipt does not prove

It does not prove the route was optimal, and it does not prove the whole route: `quoted` is the last hop's quote. What it does prove is narrower and checkable: the recipient received `realized`, and that amount cleared both `floorUsed` and the user's own minimum, or the transaction would have reverted.

Do not trust this page — reproduce it

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

In a checkout of the V2 repository at commit 969bcc6, run grep -n 'event ExecutionProof\|emit ExecutionProof' src/BlazePhoenixRouter.sol, then grep -n 'SettledSwapEmitsExactlyOneFee\|DeliveredNeverBelowTheProtocolFloor\|FeeIsChargedOnExactlyOneSide\|DeliveredNeverBelowUserMinOut' test/BlazePhoenixRouter.invariant.t.sol. For a real receipt, read ExecutionProof from the transaction logs and make an eth_call to findBestRoutePlan at the block it names. Arithmetic: 998.400 - 933.600 = 64.8 and 5.000 x 0.0028 = 0.014. Reading: section 11.6 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). Anatomy of an execution receipt: what each field proves, and what it does not. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/anatomy-of-an-execution-receipt/
@misc{blazephoenix_anatomy_of_an_execution_receipt,
  title  = {Anatomy of an execution receipt: what each field proves, and what it does not},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/anatomy-of-an-execution-receipt/},
  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 Foundations · 4 / 33
The V4 emission curve: a linear base plus a halving bonus ›Each staking deployment schedules 90,000,000 BZPX over eight years: 60,000,000 at a constant rate plus a bonus that halves every two years. Here is the closed form, the year-by-year table and the arithmetic that makes it close with zero remainder.7 min

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

Go to APP