Published records

Every batch record we have published, and what each one actually is.

Why the status is not in the record

A record's hash is anchored on Solana. Adding a field that said “this was a devnet test” would change that hash and break the verification the record exists for. Moving it is out too — a certificate's URI is fixed when it is minted, and certificates already point at these addresses. So the status is published here, beside the records, and the files themselves are left untouched.

Only records marked mainnet represent trees Sapling Network claims to have funded.

Each planting also carries a grade, computed from the record rather than chosen: witnessed documented allocated. The counter adds the first two. Allocated trees are a share of somebody else’s planting — we cannot point at which ones are ours, so they are shown apart and never added in. Section 13.2.

Survival is published here too, for the same reason. Each planted batch is checked for three years (Section 9.5); every check counts the trees found alive, damaged, dead and not found, and a tree not found counts as lost. A community check is counted only once a lead or Senior who did not plant the batch signs it off. Sites are shown at about a kilometre; the positions of single trees are not published. All sites · monitoring.json

This page reads index.json, which is generated from the records at build time rather than kept by hand. To check a record against its anchor, use the verifier.