At the grow site / Ithaca, NY (home and small-farm oyster/shiitake cultivation)
Home/small-farm mushroom cultivation contamination audit (oyster/shiitake) — Ithaca, NY.
Inspect a grow site near Ithaca for contamination such as green mold, cobweb mold, or bacterial blotch. Read all of it
Not funded yet. Settles as earned credit, $130 proposed.
Proof it takes, the deadline, the level
- ProofDated grow area audit identifies contamination by type + Photograph taken before disturbance + Contaminated substrate isolated, then discarded, never salvaged + Sterile technique reviewed against source protocol
- Open until2026-12-26
- Levelentry
All of it: the words, the place, the proof
Inspect a grow site near Ithaca for contamination such as green mold, cobweb mold, or bacterial blotch. Cornell's own Specialty Mushrooms project, the source of this standard's oyster/shiitake guidance, runs from here.
Offer to pay $130. The receipt lands onchain once the proof is approved.
Safety, read before you claim
Contaminated substrate is always discarded, never salvaged or eaten, and this is cultivation husbandry, not food safety certification or a medicinal claim. Grower respiratory symptoms route to a clinician, and any wild volunteer mushroom near the grow area routes to a mycological society.
The full safety list for this job:
- This audit makes no edibility determination beyond the cultivated species already grown intentionally.
- This packet is independent of and not affiliated with Cornell University or the Cornell Small Farms Program: named as the real, verified source of this standard's own oyster/shiitake cultivation guidance, 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
- The grow area (fruiting chamber, monotub, or shiitake log yard) with good lighting
- Camera for photographing any suspect growth before disturbing it
- Nitrile gloves and an N95 dust mask for inspection near suspect substrate
- A sealed disposal bag for discarded contaminated substrate
- A grow log with prior audit dates and environmental settings
Steps
- 1. Inspect the substrate and fruiting surfaces without unnecessary disturbance; record temperature, humidity, and fresh-air-exchange (FAE) conditions at the time of audit.
- 2. Look for green mold: green-sporulating patches on grain spawn or substrate, most common where FAE is poor or substrate was under-sterilized (Trichoderma spp., the documented dominant green-mold pathogen on cultivated mushroom substrate).
- 3. Look for cobweb mold: a fast-spreading, fine gray-white mycelial mat that can overgrow pins and casing within days (Cladobotryum spp.).
- 4. Look for bacterial blotch: brown-to-tan slimy or sunken lesions on cap surfaces, typically worsened by excess surface moisture (Pseudomonas tolaasii).
- 5. Photograph any suspect growth before touching it, for the grow log.
- 6. Isolate affected substrate or blocks immediately, moving them out of the shared grow space to prevent airborne spore or mycelial spread to clean substrate.
- 7. DISCARD the contaminated substrate. Never salvage it, cut out the affected area and continue fruiting, or harvest any mushroom from a contaminated block for food.
- 8. Review sterile/sanitary technique against the source protocol — substrate pasteurization/sterilization parameters, spawn-handling cleanliness, FAE and humidity control, and surface sanitation between batches — and record the specific gap identified, if any.
- 9. Log the audit date, findings, disposal action, and technique-review outcome against the prior audit.
What counts as done
- Grow area, substrate, and environmental conditions (temperature, humidity, FAE) inspected and recorded
- Any contamination identified by type (green mold / cobweb mold / bacterial blotch) with a pre-disturbance photograph
- Contaminated substrate isolated and DISCARDED -- never salvaged, trimmed-and-continued, or harvested for food
- Sterile/sanitary technique reviewed against the source protocol with any identified gap recorded
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_1790539274004_wfo7b52