Run a community compute grant.

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.

Where

public roads and city parks, Lebanon, Boone County, IN · Open the map

Pay

$80 proposed

This packet is not funded yet, so this figure is a proposed price and not money waiting in escrow. If a buyer funds it, approved proof settles that price onchain. If nobody funds it, approved proof earns provable credit toward the work instead of cash — recorded, and readable any time at vealth.net/labor/credit/(your wallet). You see which before you claim, never after.

Proof

named project + grant or free-tier source + hours used + published result hash

This is exactly what gets it approved. Nothing settles without it.

Level

intermediate

Open until

2026-12-01

Posted by

0x034F…6c89

The creator wallet. Its signature is what approves proof and settles the wage.

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. 1. Name the local project and the institution it serves (school, watershed group, library) and get its steward's written go-ahead.
2. 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. 3. Run the job; log hours used, the job description and the resources consumed.
4. 4. Publish the result openly in the form the project chose (report, dataset, map) and record who can use it.
5. 5. Anchor the published result's content hash via vealth.net/anchor and put the hash in the proof.
6. 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.