Anyone can start here · public sidewalks around CCSD campuses and civic buildings, Las Vegas, Clark County, NV (city-center coordinate; the worker records the exact campus)
Build the production-dashboard baseline for Clark County School District solar carports, Las Vegas, NV.
Fund it for $80. Proof lands onchain when it's done.
$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.
Open, but not claimable yet. restricted: permit-required — Regulated or permit-required work cannot be claimed on this rail yet. It stays readable; voting and pledging are free, and funding is separate from claiming.
What the work involvesClark County School District solar carports is run by Clark County School District under Nevada school and community solar, on NV Energy. Before anyone argues about whether it is doing well, write down what the public record already says: nameplate DC rating, module count, commissioning date, tilt and orientation where published, and the address of the production data itself. district sustainability reporting and per-campus dashboards; record the URL used or mark it not published. Every field carries its source or is marked unknown, and nothing is estimated in the owner's favor or against it.
How this work is done
A documented method, so this packet comes out the same whoever does it.
Bring
- laptop or tablet with a spreadsheet
- the array's public production dashboard address, or the owner's meter export
- a named public irradiance source such as NREL NSRDB or the nearest public weather station
- the array's published nameplate DC rating and commissioning date
- camera and a GPS phone for the single public-ground photo
Steps
- 1. Record the array's identity: host, address, nameplate DC rating in kW, module count if published, commissioning date, tilt and orientation if published, and the production dashboard address. If no dashboard and no owner meter data exist, stop and publish that as the finding.
- 2. Download the period's measured energy in kilowatt hours at the finest interval the source offers, and record the interval, the time zone and the download date.
- 3. Pull irradiance for the same period and the same location from a named public source, and state whether it is plane-of-array or global horizontal. Never substitute a design assumption for a measurement.
- 4. Compute expected energy from the nameplate rating and the irradiance, then the performance ratio as measured over expected, leaving every input visible in the sheet.
- 5. Name the losses the public record supports: shading, soiling, inverter downtime hours, curtailment. Publish anything you cannot name as unexplained rather than assigning it to a cause.
- 6. Publish the sheet in full with its sources, take one photo of the array from public ground, and anchor the published file's content hash.
What counts as done
- The array's nameplate DC rating, module count and commissioning date, each with the source it came from or marked unknown
- The production dashboard URL and the finest reporting interval it offers, or the dashboard recorded as not published
- One photo of the array from public ground with a GPS waypoint and the date
- The baseline published in full 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_1788297273833_sbs2ubj","funderWallet":"0xYOU"}.
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.