Carbon credits, verified from orbit.
Many forest credits are over-issued, double-counted, or keep trading after the forest is gone. CanopyChain ties every credit to a satellite report hash, retires credits permanently, and flags reversals in public.
Verification report · Polygon Amoy
Rondônia Forest Reserve, Brazil
NDVI · Sentinel-22025
NDVI · Sentinel-22026
- Forest cover
- 1,131.8 ha → 1,132.1 ha
- Mean NDVI
- 0.84 → 0.87
- Credits issued
- 10,696 tCO2e
- Sentinel-2 resolution
- 10 m
- Credits per project & vintage
- ERC-1155
- Buffer pool for reversals
- 10%
- Public, on-chain audit trail
- 100%
Why it matters
6M+ ha
of tropical primary forest lost in 2024, a record year (Global Forest Watch, WRI / University of Maryland).
Carbon finance can pay communities to keep forests standing, but only if every credit stands for a real tonne of CO2 that stayed in the trees. When credits are over-issued, double-counted or keep trading after the forest burns, buyers claim reductions that never happened.
CanopyChain's impact is integrity: every credit is tied to a satellite measurement, a signed approval and a public, permanent record.
How it works
From satellite pixels to retired credits, in six verifiable steps.
- 01
Register a forest
Draw the boundary on a satellite map and sign it with your wallet. An approver checks the land title before it goes on-chain.
- 02
Verify by satellite
Sentinel-2 imagery measures forest cover (NDVI) against a baseline year and estimates avoided emissions in tCO2e.
- 03
Mint credits
The report hash is attested on-chain and ERC-1155 credits are minted: 90% to the owner, 10% to a buffer pool.
- 04
Retire for good
Retiring burns credits and stores a permanent on-chain certificate, so a credit can never be counted twice.
- 05
Keep watching
Re-checks detect deforestation. A reversal is flagged on-chain and buffer credits are cancelled.
- 06
Audit everything
The public registry lists every project, issuance, retirement and reversal straight from the contract.
Safeguards
Trust enforced by code, not promised in a PDF.
Every rule below is enforced by the smart contract or by the verification backend, and the security assessment in the repository explains each one, including what is still trusted.
Signed ownership
The owner's wallet signs every registration, and the signature expires after ten minutes. Nobody can register a forest in someone else's name.
One forest, one project
A boundary that overlaps an existing project is refused, so the same trees can't back two sets of credits.
Independent approval
The contract admin signs off on land title and fixes the methodology inputs. Nothing reaches the chain before that, and nobody can inflate the numbers later.
Only the oracle mints
Credits are minted solely by the oracle role, once per project and vintage. The contract rejects a second verification of the same year.
Tamper-evident reports
Each satellite report's keccak256 hash is written on-chain. Anyone can recompute it in the browser and prove the report wasn't edited.
Reversals hit the buffer
10% of every issuance is held back. When re-checks find forest loss, the buffer is burned and the project is flagged in public.