Receipts · one job
A sample receipt, start to finish
One job, its proof, and its payout, shown exactly as they stand right now.
Read the sample job itself: what it asked, what counted as done, and how it was paid.
What a receipt shows, and what it does not
It shows
- Who took the job, and the proof rule posted before they began.
- How much proof they sent, as fingerprints.
- Who decided, as far as the record kept it.
- The payment, with a link anyone can check on Base.
It does not show
- That the work changed anything on the ground.
- The photos or files themselves.
- That the work was done well, beyond the written rule.
No job has yet been settled by someone outside Vealth. Every settled job so far was done by a wallet Vealth runs.
Receipt
—
READING THE RECORD
Reading the record
Reading this job’s record. Nothing below is claimed until it arrives.
- Accepted claim
- —
- Evidence
- —
- Judgment
- —
What this does not prove
Not proven
- Reading the record. Nothing is asserted until it arrives.
Settlement or earned record
Settlement
Money moved, in the asset and on the network this job named.
the money lane
Earned record
Approved proof on an unfunded job banks a credit: a receipt, never money, never spendable, never a token.
the work lane
Event chronology
- ReadingThe record is on its way.
Source, chain and export status
—
Where this leads
A receipt is not the end of the trail. Nothing here claims an ecological outcome.
What it leads to
The worker, the place, the settled work before this one, and the work still open and claimable here, all from the same public record.
How to read this document
The four things to know
The state is a word, and the foot confirms it
Still open means proof is in and nothing is decided. Returned for revision means the proof came back and can be sent again, free. Accepted means the evidence passed and nothing has closed yet. Only a settled or provisioned document draws the double rule at its foot: that is what closed looks like.
Accepted is not paid
Approved proof and a payment are two different events with two different authorities. Posted pay is not paid pay: pay is verified on Base only after approved proof, and the receipt above says whether this job’s own terms pay cash or a work credit.
Each stage names its own authority
The claim, the proof and the decision are Vealth’s durable record. The payment, and any retirement, are Base transactions that our server checked on the chain itself. The document never blends the two.
The claim never grows larger than the evidence
Work completion, payment and retirement do not by themselves prove an ecological outcome. That sentence is in the non-claims block of every receipt, because it is the one a stranger most needs.
For your AI: the link at the foot of the document is the same record, machine-readable and keyless. Verification never needs a payment.