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

> Canonical: https://blazephoenix.xyz/learn/anatomy-of-an-execution-receipt/
> License: CC BY-NC-ND 4.0 (attribution + link) · © 2026 BlazePhoenix
> Updated: 2026-11-16

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.

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.

## 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.

## 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.

**Verify it yourself:** 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.

Related: https://blazephoenix.xyz/learn/result-verification-primitive/ · https://blazephoenix.xyz/learn/verifying-beats-solving/ · https://blazephoenix.xyz/learn/the-authentic-callback/
