Corrections

CORRECTION #2 — 2026-07-19 What happened: Our daily archive published days as "final" while a significant share of on-chain settlements had not yet been captured. The nightly settlement scan runs against a time budget; blocks beyond the cutoff were not reached before days were stamped — and our coverage measurement only counted the blocks the scan did reach, so the gap was invisible to us. A full re-sweep of every published day has now recovered 921,973 settlements across 2026-07-07 → 2026-07-12. Several days were missing between 20% and 53% of their settlement records: 07-07 (+240,723), 07-09 (+173,292), 07-10 (+245,803), 07-11 (+137,312), 07-12 (+123,983), 07-08 (+860). Separately, on 2026-07-15 our database provider's resource limits caused a day-long outage; all of that day's captures were subsequently recovered from the chain. A sentence we retract: Correction #1 stated "Settlement receipts (the daily archive) — zero loss, all days captured." That was written in good faith about that incident's scope; as a general claim it was wrong, and we retract it. This correction replaces it with measured numbers. What was NOT affected: Verdicts, lifetime per-agent figures, and the headline totals — computed by full-history enumeration and independently reconciled against the chain to the cent. Most recovered records belong to already-quarantined bot-loop wash; recovering them completes the forensic record without inflating any verified-revenue figure. The error was confined to per-day settled figures in the daily archive. The fix, already live: "Final" is no longer a calendar claim. A coverage watermark now records exactly which blocks have been contiguously scanned, and a day is only stamped final once the watermark has provably passed its end. Days we haven't fully seen now wait, visibly, instead of publishing. Every publication since 2026-07-17 has run under this proof. The completions: Per our data definitions, history is never silently rewritten — it may be completed, flagged and disclosed. The affected days are being recomputed with the recovered settlements, each flagged late_write. The before → after figures append to the table below as each day completes (all within ~24 hours of this notice):

What remains open, honestly: (1) A small tail of settlements from facilitators that have since gone inactive cannot be recovered by our standard re-sweep — including, notably, the three settlements ($7) whose discovery opened this incident — see the Final Update below, where the chain's precise figures correct this description. A historical-trust re-sweep to recover them is scheduled and its results will be disclosed here. (2) Our daily archive measures the standard x402 rail (transferWithAuthorization). A second settlement path — account-abstraction (ERC-4337) routed payments — exists and is under investigation; lifetime figures already include it, daily figures will state their basis until it is measurable per-day. The record: Original values remain permanently visible here. Every recovered settlement is individually verifiable on Basescan.

CORRECTION #2 — FINAL UPDATE, 2026-07-23: the open items, resolved The inactive-facilitator tail — recovered. As disclosed above, some settlements from facilitators that later went inactive could not be recovered by our standard re-sweep. We have now completed a historical-trust re-sweep: each affected day was re-scanned using the facilitator set as it stood on that day, reconstructed from chain evidence. Result: 877 additional settlements recovered across 2026-07-07 → 2026-07-13. The affected days were recomputed once more (flagged late_write); the updated figures are in the table below (total +$6,983.64).

The settlements that started this — home, and our own number corrected. This incident began when our founder noticed missing settlements on one agent. Above, we described them as "three settlements ($7)." The chain's precise answer, now that they are recovered: two settlements were missing — $1.00 and $2.00, totaling $3.00 — alongside one $1.00 settlement we had always captured; the agent's day held three settlements totaling $4.00. We are correcting our own earlier sentence to match the chain. Precision applies to our legends too. Still open, as stated: the account-abstraction (ERC-4337) settlement path remains under investigation; daily figures state their basis until it is measurable per-day. This closes the incident opened 2026-07-08. Every figure above is verifiable on Basescan.

CORRECTION #1 — 2026-07-14 What happened: From 2026-07-12 to 2026-07-14, this site UNDERSTATED the verified x402 economy on Base. The in-scope count showed 59 verified services (~$39.2M volume) when the true figure was ~94-96 (~$45M+). 37 genuinely real agents were wrongly excluded. Why: Our scope check — the test deciding whether an agent belongs to the x402 economy we measure — sampled each agent's OLDEST transactions. Agents that adopted x402 after their wallet's creation could fail this test falsely. A safety cache masked the flaw until 2026-07-12, when the cache's database query exceeded a URL length limit as the tracked-agent count grew, FAILED, AND THE FAILURE WAS SILENTLY IGNORED — so every agent was re-tested by the flawed method at once. The excluded agents' recent on-chain activity was verified directly: their payments are genuine x402. The rails never changed; our ruler misread them. What was NOT affected: Settlement receipts (the daily archive) — zero loss, all days captured. Real/bot verdicts — correct throughout; all daily anchors passed. Money figures per agent — computed from receipts, correct. The error was confined to one label (in-scope/out-of-scope) for two daily snapshots. The fix (deployed 2026-07-13, verified 2026-07-14): the scope check now samples recent AND oldest transactions; the cache query was rebuilt to be size-proof; and any such failure now halts safely and loudly instead of silently mass-flipping agents. The record: per our data definitions, the 07-12 and 07-13 snapshots stand as written — history is never rewritten. This note is the correction.