Receipts remember what happened.

Paste a packet id, a transaction hash, a wallet, or a receipt link, and get the checkable record: what was claimed, what is not, and what got paid.

Verification stays free forever: the server refuses to boot if these paths are ever paywalled. Trust it first with the site’s safety checks. Looking for a place instead? Search the board.

What a proof contains, and who decides

Physical evidence lives here as hashes and a distance reading, never as stored photos. The packet’s own verification rule chooses between the two branches below; neither is a default.

What a worker hands in

  1. Photo hashes. SHA-256 of each image. The file itself is never stored.
  2. Where. Distance from the packet’s own coordinate, against the 350 metre cluster. Over that is an advisory flag, never an auto-reject.
  3. Checklist. Authored from the packet’s method template, not written at review time.

Who decides

  1. A human decided. Every non-digital packet routes here. AI may administer the checklist; a person alone accepts. Self-review is refused, and only the packet’s creator is admitted to sign. not decided yet
  2. The written rule recomputed. Only where the definition carries an executable verification block. The server re-runs it and the result stands on its own. No person reviewed that proof, and the receipt says so. not decided yet

The reading

Paste a packet above and this shows which branch that packet’s rule actually took.

no actor is recorded

— awaiting a human right now. A dash means the physical rail is off, never zero.

A real receipt, closed

Receipt

EWP work packet 14, Base mainnet

SETTLED

The first settled Work packet.

A bounded piece of digital curation work: posted, claimed, proven, reviewed, paid 0.50 USDC, and settled on 7 July 2026. Labeled a self-demonstration: the machine’s own agent did the work, and the receipt says so.

Settlement or earned record

Settlement

0.50 USDC moved onchain at settlement, on Base mainnet.

this packet took this lane

Earned record

No credit was banked: the wage was paid in the act.

not this packet’s terms

CLOSED · SETTLED IN MONEY Open the full receipt document

Check it without us in the middle: the settlement transaction on Base and the source-verified settlement contract. The same facts, machine-readable, with claims and non-claims stated: the receipt as JSON.

Work waiting for human judgment

Physical evidence, submitted by workers, judged by a person. Only the packet’s creator wallet can sign a verdict; anyone may read. A verdict is judgment recorded, never a payment.

Reading the review queue. Real items or an honest empty, never invented.

The standard

The claim never grows larger than the evidence.

Two things sit on the record, and they are not the same thing. Anchored hashes and settled transactions are checkable forever, no cooperation from us required. The evidence beside them (photos, documents, signatures, judgment) lives in our ledger, public today but not yet onchain or exportable. Every number on this page loads from a named live source, or reads as a dash: zeros and failures stay visible. That is the point.

The data room

Open what you need. Every number inside loads from a named live source or reads as a dash; zeros and failures stay visible.

Two counters, kept un-confusable
  1. Outside board workers

    — workers outside our own wallets who have claimed, proven, and settled a board packet, counted live from the settled collection. A zero stays visible, and so will the first one. Claim a packet.

  2. Operator self-demonstrations

    Settled by the machine’s own agent, each labeled as such and each checkable onchain: packet 14 on Base, one on Robinhood testnet, one on Robinhood Chain mainnet. Named one by one rather than counted, because each is chain-frozen history. They prove the settlement path works on every chain we run, not outside demand. Read packet 14 · Robinhood mainnet, onchain.

These are two different measures and are never blended into one number.

Current counts, from live sources

A dash means the live source did not answer just now. Dashes are deliberate: numbers here load from named sources or stay empty, never padded. For scale, the machine’s own ledger counts — tonnes across all retirement lanes, a closed total because retirement has been stopped by operator order since 4 August 2026, and — paid calls, —.

  1. Settled work packets

    — settled through the work protocol.

    Proves: a claim, accepted proof, and an onchain settlement exist for each one. Does not prove: ecological effects beyond each packet’s named proof.

  2. Verified onchain retirements

    — retirements, — tCO2e, verified-retire totals only.

    Proves: retirement transactions confirmed onchain, each with a checkable hash. Does not prove: anything about the underlying credits beyond their registry records.

  3. Machine-loop retirements

    — retirements, — t, from the loop’s own hourly ledger, .

    Proves: the machine’s own small recurring retirements while that lane ran. It is stopped, so this total no longer grows. Does not prove: the same thing as the verified-retire total above; the two are different measures and are kept apart.

  4. Verified paid calls

    — calls, — gross, reconciled to one canonical pin.

    Proves: paid agent calls settled onchain. Does not prove: external demand. Every row is operator-funded today, and the site says so.

Deeper room: the money room shows money in, retire spend, gas, and net as one tracked ledger.

The lanes, kept apart

Different kinds of receipt prove different things. They are never blended into one number.

  1. Self-demonstration · contract lane

    Settled by the machine’s own agent, labeled as such: Base, Robinhood testnet, and Robinhood mainnet (where the wage was 0.10 USDG). Proves the settlement path works on each chain. Does not prove demand. Read packet 14.

  2. Outside worker · board lane

    — so far, counted live. The first person to claim, prove, and settle a board packet gets the first outside receipt, founder-reviewed. Become the first.

The first closed loop, in full

One Work packet has completed the whole journey: posted, claimed, proven, reviewed, paid, and settled on Base on 7 July 2026. It was a labeled self-demonstration: the machine’s own agent did the work and a real 0.50 USDC wage moved. The settled counter above counts packets settled through the work protocol, across the whole protocol rather than one board, so this packet does not change it. This one settled directly on the onchain settlement contract, with no board record: a different measure, kept apart on purpose.

Check it yourself onchain, without us in the middle: the settlement transaction on Base and the source-verified settlement contract (Base mainnet). Every stage of the packet has its own transaction: the receipt links all six. Machine-readable: the receipt as JSON.

What each status proves

Every receipt and packet carries a status. Each one says what it proves, and what it does not.

  1. Draft

    Shaped, not sent. Proves intent and scope. Does not prove work, funding, or review.

  2. Prepared

    A packet with method, proof requirements, and price. Proves the task is bounded. Does not prove anyone claimed it.

  3. Submitted

    Proof has been sent for review. Proves evidence exists. Does not prove it satisfies the requirements.

  4. Reviewed

    The proof was checked against the packet’s own requirements. Proves review happened. Does not prove settlement.

  5. Rejected

    A reviewer read the proof and it did not satisfy the packet’s proof rule. Proves the claim stayed honest. Does not prove the work was not done; a corrected proof can be submitted.

  6. Settled

    Payment released against accepted proof. Proves the loop closed for this packet. Does not prove effects beyond the named proof.

  7. Earned credit

    Approved proof on an unfunded packet, banked as a receipt. Proves the work was accepted. Does not prove a payment: it is never money, never spendable, and never a token.

  8. Onchain

    The settlement event, its payment reference, and the contract state are written to Base. Anchored hashes and settled transactions are checkable forever. Proves the record is public and outlives this page. Does not prove more than the record says, and does not cover the proof bundle beside it.

  9. Retired

    An ecological credit was retired and cannot be claimed again, with a transaction hash. Proves the retirement. Does not prove the underlying project beyond its registry record. The retirement lane is stopped by operator order since 4 August 2026, so no new receipt carries this status.

  10. Hosted

    The proof bundle behind a settlement: photos, documents, review assertions, signatures, proof requirements, judgment context. It lives in our ledger and is publicly readable on Vealth today. It is not onchain and not yet exportable. Only the anchor rail, a Merkle proof against a published root, verifies anywhere without us.

  11. Paused

    A rail is intentionally off. Proves nothing is moving there. Not a failure; paused means paused.

  12. Failed

    Something did not complete, and the ledger says so. Proves the ledger is honest. Failures stay visible; they are not deleted.

The boundary

Receipts are records, not marketing. People still decide, do, review, and approve real-world work; proof closes the loop, and a receipt is the memory of it. Half of that memory is checkable without us, forever. The other half, the evidence behind it, still lives only in our ledger. This page says which half is which, rather than calling all of it permanent.

For your AI: verification needs no key and no payment. Hand it is-this-safe.json for the claims and their checks, or connect vealth.net/mcp and ask it to verify a packet.