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.

Two things sit on the record, and they are not the same thing. Anchored hashes and settled transactions are checkable forever. The proof bundle behind a settlement lives in our ledger and is publicly readable on Vealth today; it is not onchain and not yet exportable. That means the settlement event, its payment reference and the contract state need nobody’s cooperation to read, while the photos, documents, review assertions, signatures, proof requirements and judgment context around them are ours to keep serving. Verification itself is free forever, by law: the proof paths cannot be put behind a paywall, and the server refuses to boot if they are.

  1. Place
  2. Problem
  3. Work
  4. Proof
  5. Receipt
Verify a 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.

Before you trust the verifier, run the site’s safety checks or give your agent /is-this-safe.json.

Looking for a place instead? Places live on the board; search the city there, then open any packet’s receipt link.

A real receipt

A real receipt

Chain-frozen history: these facts do not change, so they are written here rather than loaded.

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 →

Check it without us in the middle: the settlement transaction on Base and the source-verified settlement contract. Machine-readable: /receipts/ewp-work-14.json, the same facts with claims and non_claims stated.

What needs judgment

Work waiting for human judgment

Physical evidence, submitted by workers, judged by a person: the packet’s creator signs the verdict. Anyone may inspect. Photo evidence lives here as SHA-256 hashes with GPS, never as stored photos, and a verdict is judgment recorded, never a payment.

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

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.

The data room

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

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.

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, .

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 while that lane ran, counted by its hourly ledger. 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.

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 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.

The first closed loop, in full

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

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 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.

  • 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.

  • 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.

  • 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. Anchored hashes and settled transactions are checkable forever. The proof bundle behind a settlement lives in our ledger and is publicly readable on Vealth today; it is not onchain and not yet exportable. This page says which half is which rather than calling all of it permanent.