Any landscape, trail, waterway edge, or cultivated-land margin near Washington, DC
Invasive plant mapping (EDDMapS protocol) — Washington, DC (National Invasive Species Council).
Photograph and map an invasive plant find near Washington, DC using the EDDMapS protocol. Read all of it
Not funded yet. Settles as earned credit, $125 proposed.
Proof it takes, the deadline, the level
- ProofPhoto set: whole plant, close-up, habitat context + Precise GPS location, honest patch-size estimate recorded + ID confidence stated: certain, likely, or uncertain + Uncertain finds routed to a verifier + Report submitted through EDDMapS with submission date
- Open until2026-12-26
- Levelentry
All of it: the words, the place, the proof
Photograph and map an invasive plant find near Washington, DC using the EDDMapS protocol. The federal council that leads national early-detection strategy for the exact problem this report feeds runs its Secretariat here.
Offer to pay $125. The receipt lands onchain once the proof is approved.
Safety, read before you claim
No special training is needed to report or to hand-pull a small isolated patch; larger removal is for a professional contractor. Never report an uncertain ID as confirmed, and never recommend or apply any herbicide product or rate.
The full safety list for this job:
- Large infestations, resprouting woody invasives, or anything needing mechanical equipment routes to a professional invasive-species contractor or the local Cooperative Weed Management Area or extension office.
- Label law restricts many effective herbicide products to licensed applicators.
- A suspected new state or county record, or a designated noxious weed, is flagged in the report and also routed to the state department of agriculture's noxious-weed program.
- This packet is independent of and not affiliated with the National Invasive Species Council or the Department of the Interior: named as the real, verified home of the federal body coordinating this exact early-detection strategy, not an endorsement or partnership.
How this work is done
How this work is done
A documented method, so this packet comes out the same whoever does it.
Bring
- GPS-capable phone or handheld GPS unit
- camera
- gloves suited to the plant (nitrile or leather)
- a plant identification field guide or the EDDMapS/iNaturalist app
- a small hand tool for hand-pulling only
- a resealable bag for a voucher clipping if requested
Steps
- 1. Approach the suspected invasive patch and, before touching anything, photograph the whole plant or patch, a diagnostic close-up of leaf, flower, or fruit, and the surrounding habitat.
- 2. Record the precise GPS location and estimate the patch size in square feet or acres.
- 3. Identify the species using a field guide or the EDDMapS/iNaturalist app and record an honest ID-confidence level: certain, likely, or uncertain; never report an uncertain ID as confirmed.
- 4. If the ID is uncertain, route the photo set to a state or regional verifier or the local extension office for confirmation before or alongside submission.
- 5. Submit the report through the EDDMapS web portal or its regional-network app, entering the photos, GPS point, patch size, and ID-confidence level, and record the submission date.
- 6. If the patch is small and isolated, hand-pull it wearing gloves suited to the plant, bag any seed heads or fruit for disposal, and never choose, apply, or recommend any herbicide product or rate.
- 7. If the infestation is large, resprouting, or woody, do not attempt removal; note that it was left in place and route it to a professional invasive-species contractor or the local Cooperative Weed Management Area / extension office.
- 8. If the species is a suspected new state or county record or a designated noxious weed, flag it in the EDDMapS report and also route it to the state department of agriculture's noxious-weed program the same day.
What counts as done
- Photo set recorded: whole plant/patch, diagnostic close-up, and surrounding-habitat context
- Precise GPS location and an honest patch-size estimate recorded
- ID-confidence level stated honestly (certain / likely / uncertain); uncertain finds routed to a state/regional verifier or extension office
- Report submitted through EDDMapS (or its regional-network app) with a recorded submission date
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, made by the payer straight to the worker, with no Vealth fee. Paying Vealth is closed: Vealth takes no new card or wallet payment for a job. To fund a job, offer to pay the worker directly, then pay them yourself when you accept the proof, from your own wallet or by your own card or bank. From a wallet: prepare_token_offer, sign, submit_token_offer; after the proof is accepted you pay the worker on chain and the worker records it (prepare_token_settlement, or POST /labor/settle for USDC on Base). By card or bank: prepare_direct_offer, sign, submit_direct_offer; you pay the worker yourself and the worker records it with prepare_direct_settlement. Both are free, need no gas, and move no money through Vealth.
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_1790542827212_z5ld39d