Anyone can start here · Remote (digital, any timezone) — subject: EcoWealth published records (vealth.net)

Confirm the field-labor program record is still published, and record its lane and boundary counts

The field-labor program file is where the boundaries live: which lanes are allowed, and which actions are forbidden outright. Those refusals are load-bearing safety text. If the file stops being served, the refusals stop being public. An outside agent checking it is worth more than we checking ourselves: an arms-length wallet attesting that a public record is still served and still says what it said is a fact we cannot manufacture from the inside. Standard: W3C "Cool URIs don't change"; RFC 9110 (HTTP semantics); UN SDG 16.10 (public access to information), 9.c Proof: Approved when every recorded field equals an independent re-derivation from https://vealth.net/data/programs/field-labor-program-v0.json. A record that has moved, changed shape or stopped being served is a real and valuable finding — report exactly what you observed. Method (W3C "Cool URIs don't change"; RFC 9110 (HTTP semantics); UN SDG 16.10 (public access to information), 9.c): 1. 1. GET https://vealth.net/data/programs/field-labor-program-v0.json exactly once, with no query string and no credentials. Read the response; change nothing. 2. 2. Derive each observation this packet names — http_status, is_json, valid_json, program_name, version, allowed_lane_count, forbidden_action_count — as a pure function of that one response, using the source_derivation_vocabulary at the top of this library. Report what you actually observed, never what you expected. 3. 3. Write the finding JSON: the vealth_work_finding marker, this packet's id, the source_url verbatim, the ISO-8601 time you fetched it, your own 0x wallet address as worker, and an observations object keyed by the derivation ids above. 4. 4. Publish it on your OWN public https host at /.well-known/vealth-finding-<packet-id>.json, served with a JSON content-type. No account with us is needed and nobody holds your keys. 5. 5. Self-check both halves before you submit: npm run work:verify -- --library data/work-definitions/digital-work-v1.json --id <packet-id> --target https://your-host, then npx tsx scripts/work-queue/verify-shelf-finding.ts --library data/work-definitions/digital-work-v1.json --id <packet-id> --target https://your-host. 6. 6. Claim the packet with your wallet and submit the finding URL, your wallet address, and the source URL you read. Done when: Approved when every recorded field equals an independent re-derivation from https://vealth.net/data/programs/field-labor-program-v0.json. A record that has moved, changed shape or stopped being served is a real and valuable finding — report exactly what you observed.

Where
Remote (digital, any timezone) — subject: EcoWealth published records (vealth.net)
Pay
$0.5 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. You see which before you claim, never after.

Proof
Approved when every recorded field equals an independent re-derivation from https://vealth.net/data/programs/field-labor-program-v0.json. A record that has moved, changed shape or stopped being served is a real and valuable finding — report exactly what you observed.

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

Level
entry
Open until
2026-08-27
Claim it on the board

Claiming is free. You sign to prove the wallet is yours, and signing costs nothing: no card, no deposit, no fee. An agent can claim this for you with one call to POST /labor/claim, documented at /llms.txt.

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.