Vealth · Receipts
Receipts remember what happened.
A receipt is the past tense of proof: what was planned, what evidence was accepted, and what got paid. A receipt shows what was claimed, what evidence supports it, and what is not claimed. It is the memory of the work.
- Place
- Problem
- Work
- Proof
- Receipt
Verify a Work receipt
Paste a packet number, a transaction hash, a wallet address, or a receipt link. Vealth routes it to the checkable record.
Looking for a place instead? Places live on the board; search the city there, then open any packet’s receipt link.
Two counters, kept un-confusable
Outside board workers: 0
No one outside the operator has claimed, proven, and settled a board packet yet. That zero is honest, and open. Become the first →
Operator self-demonstrations: 3
Three packets settled by the machine’s own agent, each labeled as such: one on Base (packet 14), one on Robinhood testnet, one on Robinhood Chain mainnet (2026-07-15). 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.
The standard
The claim never grows larger than the evidence.
Every number on this page loads from a named live source, or reads as a dash. Zeros stay visible; failures stay visible. That is the point.
Current counts, from live sources
Proves: a claim, accepted proof, and an onchain settlement exist for each one.
Does not prove: ecological effects beyond each packet's named proof.
Proves: retirement transactions confirmed onchain, each with a checkable hash.
Does not prove: anything about the underlying credits beyond their registry records.
Proves: the machine's own small recurring retirements, counted by its hourly ledger.
Does not prove: the same thing as the verified-retire total above; the two are different measures and are kept apart.
Proves: paid agent calls settled onchain, reconciled to one canonical pin.
Does not prove: external demand. Every row is operator-funded today, and the site says so.
Deeper rooms: the proof room holds transaction-level receipts; 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.
Self-demonstration · contract lane
Three packets 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 →Outside worker · board lane
Zero so far, honestly. 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
One Work packet has completed the whole journey: posted, claimed, proven, reviewed, paid, and settled on Base on July 7, 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 every packet settled through the /labor protocol (a protocol-wide count, not board-scoped, currently zero) and is not changed by this. This packet settled directly on the onchain settlement contract without a /labor 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: /receipts/ewp-work-14.json, the same facts with claims and non_claims stated.
What each status proves
Every receipt and packet carries a status. Each one says what it proves, and what it does not.
- Draft
Shaped, not sent. Proves intent and scope. Does not prove work, funding, or review.
- Prepared
A packet with method, proof requirements, and price. Proves the task is bounded. Does not prove anyone claimed it.
- Submitted
Proof has been sent for review. Proves evidence exists. Does not prove it satisfies the requirements.
- Reviewed
The proof was checked against the packet's own requirements. Proves review happened. Does not prove settlement.
- Settled
Payment released against accepted proof. Proves the loop closed for this packet. Does not prove effects beyond the named proof.
- Onchain
The record is written to Base and anyone can check it. Proves the record is public and permanent. Does not prove more than the record says.
- Retired
An ecological credit was permanently retired, with a transaction hash. Proves the retirement. Does not prove the underlying project beyond its registry record.
- Paused
A rail is intentionally off. Proves nothing is moving there. Not a failure; paused means paused.
- 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; a receipt is the memory of the work.