public roads and city parks, Lebanon, Boone County, IN
Run a community compute grant.
A campus that feeds its community shares a sliver of what it is for. Read all of it
Not funded yet. Settles as earned credit, $80 proposed.
Proof it takes, the deadline, the level
- Proofnamed project + grant or free-tier source + hours used + published result hash
- Open until2026-12-01
- Levelintermediate
All of it: the words, the place, the proof
A campus that feeds its community shares a sliver of what it is for. Take a named local job (a school's science project, the watershed group's model of Prairie Creek and Sugar Creek, a library's digitization run) and run it on compute the operator or any cloud donor has granted, then publish the receipt: hours used, what was computed, the result, and who can use it. If no grant exists yet the packet still runs on free public compute and records the ask made to Meta.
Fund it for $80. The receipt lands onchain once the proof is approved.
How this work is done
How this work is done
A documented method, so this packet comes out the same whoever does it.
Bring
- the project's own data and code, held under its institution's rules
- a compute grant from the operator or another donor, or a free public tier
- a job log with start and end times
- a public place to publish the result
- vealth.net/anchor
Steps
- 1. Name the local project and the institution it serves (school, watershed group, library) and get its steward's written go-ahead.
- 2. Record the compute source: operator grant, other donor or free public tier, with the grant terms; if no grant exists, record the ask made to the operator and proceed on the free tier.
- 3. Run the job; log hours used, the job description and the resources consumed.
- 4. Publish the result openly in the form the project chose (report, dataset, map) and record who can use it.
- 5. Anchor the published result's content hash via vealth.net/anchor and put the hash in the proof.
- 6. Confirm with the project steward that the result reached them.
What counts as done
- The local project and the institution it serves, named
- The compute source: operator grant, other donor or free public tier, with the grant terms if any
- Compute hours and the job description
- The result published openly and its content hash anchored via vealth.net/anchor
Proof is measured against these, not judged by taste.
What is promised, and what is not
Three separate acts, never one: a vote is a free signed preference that moves no money; a pledge is free signed backing intent, balance-checked, that moves no money and never marks the packet funded; funding is a real payment that backs the wage. Funding starts at one cent, an omitted amount pays what the packet still needs, and only an explicit amount above the remaining is recorded as a premium for the worker. Money settles only on accepted proof. An agent can fund it in one x402 call: POST /nurture/fund {"workId":"WORK_1788295188854_g5pipbr","funderWallet":"0xYOU"}.
Claiming is free. You sign to prove the wallet is yours: no card, no deposit, no fee. Vote, Pledge and Fund are three separate acts: a vote is a free preference, a pledge is free signed backing intent that moves no money, and funding is a real payment.
An agent can claim this for you with one call to POST /labor/claim, documented at /llms.txt.
Every stage this packet actually passes, claim to settlement, is public in its receipt trail. A stage that has not happened is not claimed.
Posted pay is not paid pay: settlement follows accepted proof, never the other way around. Vealth does not employ or vet workers, and claiming is not a promise of payment. See how proof and receipts work.
Other acts: vote, pledge, fund
Packet WORK_1788295188854_g5pipbr