← Board

On-site with a milkweed patch / Minneapolis-St. Paul, MN (monarch breeding range)

Monarch larva and milkweed patch monitoring (MLMP protocol) — Twin Cities, MN.

Count monarch eggs and larvae on a fixed Twin Cities milkweed patch weekly by instar class. Read all of it

Not funded yet. Settles as earned credit, $120 proposed.

Claim this job

Proof it takes, the deadline, the level
  • ProofYearly site description, milkweed density recorded + Egg, larva counts classified by instar 1 to 5 + Same patch monitored weekly through breeding season + No organism collected, relocated, or reared
  • Open until2027-01-22
  • Levelentry
All of it: the words, the place, the proof

Count monarch eggs and larvae on a fixed Twin Cities milkweed patch weekly by instar class. The Monarch Larva Monitoring Project itself started here, so a Twin Cities site feeds the same continent-wide dataset the project's own researchers analyze locally.

Fund it for $120. Proof lands onchain when it's done.

Where
On-site with a milkweed patch / Minneapolis-St. Paul, MN (monarch breeding range). Open the map
Pay
$120 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
Yearly site description, milkweed density recorded + Egg, larva counts classified by instar 1 to 5 + Same patch monitored weekly through breeding season + No organism collected, relocated, or reared

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

Level
entry: anyone can start here
Open until
2027-01-22
Posted by
0x034F…6c89

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

How this work is done

How this work is done

A documented method, so this packet comes out the same whoever does it.

Bring

  • A fixed, identifiable milkweed patch or set of milkweed plants at the monitoring site
  • The MLMP site-description and milkweed-density datasheets (mlmp.org)
  • The MLMP egg/larva identification guide (instars 1-5) for field reference
  • A hand lens for spotting first-instar eggs and tiny larvae on leaf undersides

Steps

  1. 1. Complete the yearly MLMP site description once per season (location, milkweed species present, habitat context).
  2. 2. Record milkweed density: survey all milkweed at the site (small patches) or a defined random sample of stems (larger patches), per the datasheet.
  3. 3. On the same fixed patch/plants, check leaves — especially undersides — and stems for monarch eggs and larvae; use the hand lens for eggs and first instars.
  4. 4. Classify every larva found by instar (1st through 5th) using the MLMP identification guide's size and feature keys, never by guessed age.
  5. 5. Record counts by life stage (egg, instar 1-5) with the date, and note any predation, parasitism, or disease signs observed WITHOUT collecting or rearing the animal.
  6. 6. Leave all eggs and larvae exactly where found once counted; do not relocate, collect, or rear them as part of this packet.
  7. 7. Repeat the same patch/plants on a weekly cadence through the local monarch breeding season and log the running series.
  8. 8. Record the season's data in the MLMP dataset format so it is comparable across sites and years.

What counts as done

  • Yearly MLMP site description and milkweed-density survey completed and recorded
  • Egg and larval counts recorded by instar class (1st-5th) using the MLMP identification keys, not estimated
  • The same fixed patch/plants monitored on a weekly cadence through the local breeding season, with a dated running log
  • Confirmation recorded that no egg, larva, or adult monarch was collected, relocated, or reared

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_1790292626284_igrk0o3","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
Vote for it, free Pledge backing, free Fund this work, $120

Packet WORK_1790292626284_igrk0o3