Vealth · Receipts
Receipts remember what happened.
A receipt is the past tense of proof: what was claimed, what evidence was accepted, what is not claimed, and what got paid.
A real receipt · the first closed loop
Work packet 14 · settled on Base
- What
- A bounded work packet: posted, claimed, proven, reviewed, paid.
- Paid
- 0.50 USDC wage, moved onchain at settlement.
- Settled
- July 7, 2026, on the Base mainnet settlement contract.
- Labeled
- A self-demonstration: the machine’s own agent did the work, and the receipt says so.
Open the full receipt →
- Place
- Problem
- Work
- Proof
- Receipt
Verify a Work receipt ↓
Two counters, kept un-confusable
Outside board workers: —
Workers outside our own wallets who have claimed, proven, and settled a board packet, counted live. A zero stays visible, and so will the first one. Claim a packet →
source: /labor/settled · unique worker wallets that are not an EcoWealth wallet
Operator self-demonstrations
Settled by the machine’s own agent, each labeled as such and each checkable on chain: packet 14 on Base, one on Robinhood testnet, one on Robinhood Chain mainnet (2026-07-15). 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.
The standard ↓
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 ↓
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 and — paid calls, —.
—
settled work packets
source: /labor/stats
Proves: a claim, accepted proof, and an onchain settlement exist for each one.
Does not prove: ecological effects beyond each packet's named proof.
—
verified onchain retirements (— tCO2e)
source: /vealth/api/proof/retire-summary (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.
—
machine-loop retirements (— t)
source: /vealth/data/machine-loop-stats.json ·
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.
—
verified paid calls (— gross)
source: /data/x402-catalog.json (canonical-pinned)
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.
The first closed loop ↓
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 packets settled through the /labor 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 /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 ↓
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.
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.
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 ↓
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.