Clear one boundary or trail segment of a community forest and build its check dams, Madre de Dios.

A community forest in Madre de Dios is held by walking its edges, and the boundary and trail lines are what make that walking possible. When a line closes in it stops being walked. Invasive regrowth swallows the tread, a fallen trunk pushes traffic around it and cuts a second path, and every heavy rain turns a bare stretch into a channel that deepens until the line has to be re-cut somewhere else. Each of those is cheap to answer in one afternoon and expensive to answer a year later. This packet pays for that afternoon on one named segment, and the segment is finished when the worker leaves it: the regrowth and the blockages are gone, water is turned off the tread at every eroding point by a hand-built check dam, and the line is marked again so the next person can walk it. What the community gets is one segment they can walk today that they could not walk this morning, counted in metres of line cleared, in check dams standing, and in blockages removed, each with a before and after photograph taken at the same waypoint. The pay is for three hours of hard physical work with hand tools in hot, wet forest at a place that costs time to reach, carrying a proof discipline an ordinary work party does not carry: a GPS fix at every check dam and a hash on every photograph before it leaves the phone. Entry-skill work under this same standard prices between 95 and 260 USD across this library with a median of 160, and this sits at that median. The outcome is inspectable on foot the same day, so the price is paid against something that exists rather than against a report about it. The figure is a proposed price on an unfunded packet: it settles as recorded credit until someone funds it, and no REGEN or credit rate is implied here. This packet claims no carbon: a cleared line and a check dam hold soil, and nothing here measures what that is worth.

Where

Community forest near Puerto Maldonado, Madre de Dios, Peru · Open the map

Pay

$160 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

three counts taken on the line (metres cleared, blockages removed, check dams built and standing) + a before and after photograph pair at the same waypoint for every marked point, each photograph SHA-256 hashed before upload + GPS fix at the start, at the end and at every check dam, all inside the packet's place cluster + hours on the line + the community steward's acknowledgement and a human acceptance walk

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

Level

entry

Open until

2026-10-23

Posted by

0x034F…6c89

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

How this work is done

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

Steps

1. Get the segment from the community steward before you start: its name, its start point, its end point, the width they want the line held to, and who accepts the work. Agree the line on their map, not yours. If nobody can name the segment, do not work it.
2. Walk the whole segment once from the start point to the exit before you cut anything, carrying only marking tape and the phone. Mark three kinds of thing as you go: every blockage across the line, every stretch where the tread is closing in, and every eroding point, meaning a bare rill, a scour on the downhill side, or a place where water is running along the line instead of off it. Take a GPS fix and one wide before photograph at every mark.
3. Record the start: GPS fix, time, weather, who is working, and the marked count for each of the three kinds. Those three numbers are what the hours are measured against at the end, so write them before the work begins.
4. Work back from the far end toward your exit, so you never carry tools through finished ground and always have a clear way out. Cut invasive regrowth and encroaching brush back to the width the steward named and no wider. Cut fallen trunks and limbs only where they block the line, and roll or lever the cut pieces clear of the tread rather than lifting them.
5. Build a check dam at every eroding point you marked, and at least three on the segment. Use what is already on the ground: brush bundled tight and staked, or stacked rock where rock is there. Set it across the fall line, keyed into both sides of the cut so water cannot run around the end, with the middle lower than the ends so the water spills over the centre. Space them so the top of one is level with the base of the next one below it.
6. If the segment genuinely has fewer than three eroding points, build one at every point there is and record the true count with its photographs. An honest count of two is proof; an invented third is not, and a human accepting these hours will walk the line.
7. Turn the water off the line at each check dam: open a short outlet on the downhill side so the water held there leaves the tread instead of standing on it. Do not widen the line to make room for it.
8. Re-mark the segment using the community's own marking convention and not a new one: refresh or replace the markers at the start, at the end, and at every point where the line turns or another path joins it.
9. Photograph every marked point again from the same waypoint and the same standing position as its before photograph, so the pair reads as one place. Take the SHA-256 hash of every photograph before it leaves the phone and list each hash against its waypoint.
10. Record the end and hand it over: GPS fix, time, the three final counts (metres cleared, blockages removed, check dams built and standing), and the total hours on the line, honestly, with breaks taken out. Acceptance is a person walking it, not a document: the segment is passable end to end on foot, every check dam is standing and keyed into both sides with its spill in the middle, the counts match the photograph pairs, every before and after pair is at the same waypoint, and every waypoint sits inside the packet's own place cluster. Hand the counts, the photographs and the hash list to the com

What counts as done

• Three counts recorded on the line rather than estimated afterwards: metres of line cleared, blockages removed, and check dams built and standing
• A before and after photograph pair for every marked point, taken from the same waypoint and the same standing position, with the SHA-256 hash of each photograph recorded before upload
• GPS fix at the segment start, at the segment end, and at every check dam built, every one of them inside the packet's own place cluster
• At least three check dams built, or one at every eroding point when the segment has fewer than three, with the true count stated either way
• Total hours actually spent on the line, breaks taken out
• The community steward's acknowledgement that the segment was handed back, plus a human acceptance that the segment is passable end to end and every check dam is standing

Proof is measured against these, not judged by taste.