verify[402]
snapshot · block — Run free check

What is proven, what is not.

A truth service has to apply its own standard to itself. This page lists every claim the project makes and the public evidence behind it — including the claims that are still false.

Proven on-chain: one full settlement

A buyer paid, the seller received, and the verdict travelled inside the settlement receipt. It was the operator's own funds on the testnet — the honest scope of the proof.

The activity page lists this call and the three later testnet calls read live from the chain, with explorer links.

Receipt

0x11121007…a9324a
Base Sepolia · payTo 0xAeEF086DD4e436c69d6d0F684b4c9F43392df9cb

Audited. It lost.

An independent agent built a harness against the source and publicly reproduced two defects in the paid-recovery contract: recovery was recorded before settlement success, and a companion alias could borrow a second budget. Both were verified against the source and fixed the same day; the companion alias was later removed entirely because a public content hash must never be a replay credential. The regression tests remain in the suite.

The audit trace: public harness, public failure

The gist runs against commit cd59b105 and shows the naive contract returning 200 where it should have stopped at the paywall.

The fix: fail-closed, then re-tested

Commit 4bf3c9c: settlement stages inert, promotion only on the official onAfterSettle hook matched on the actual response bytes; one projection everywhere; per-operation replay cap. Suite 34/34.

Proposed, not adopted: an x402 extension

The recovery contract was written up as an optional extension to the x402 spec: declared evidence projection plus settled-response retry recovery, with the fail-closed rule as the normative core. It is a proposal, not a standard.

Issue #3847 · Draft spec PR #3848 — pending maintainer review. If it is rejected, this page will say so.

Not proven: no external buyer, no funding.

Nobody outside the operator has paid for a call yet. There are no grants, no revenue, and no sponsors. The free tier and the RPC calls come out of the operator's own pocket. When the first external payment lands, this page changes the same day — with the transaction.

Donation ledger

No donations or hosting sponsors yet. Every contribution will be acknowledged here with a transaction link, if the donor wants it named. Donation options · Sponsor one month of hosting — $7.

Traction ledger — dated, monthly

The three numbers a buyer would check before believing any traction claim, kept as a dated record rather than a dashboard. A paid call counts only when the payer is not the operator; a repeat buyer is an external payer with two or more settled calls; a disputed verdict is one a buyer formally contested with evidence. Counts come from settlement records reviewed by hand, so a zero month stays visible instead of being quietly dropped.

MonthExternal paid callsRepeat buyersDisputed verdictsRecords checked
2026-10 (from 19 Oct)0002026-11-10
2026-11 (to 10 Nov)0002026-11-10

First published 10 November 2026, after the 1 November date first promised in public. The free instance keeps no durable settlement store, so this table is maintained from the operator's records, not read from a database. When the first external payment lands, its transaction is added here the same day.

Reproduce it: don't trust this page.

Everything here is public: the source, the tests, the chain. The suite runs offline against recorded fixtures, and the settlement is on a public explorer.

A verify402 receipt showing a BLOCK verdict, with the intent, spender, allowance and pinned block.
A preflight receipt. A settlement carries the same intent, request, block and expiry fields.