Screening supports due diligence. It does not certify credits or verify carbon removals.
KNOW THE DIFFERENCE
START WITH A SCENARIO
A small forest. A clearer picture.
DEMO DATA
01 / PROJECT AREA
Put the claim on the map
Loading project map…
Submitted boundarySeeded example · synthetic evidence · 4 vertices
02 / SCREENING RESULT
A first look, with context
A claim is a starting point.
Choose a scenario or draw a small project boundary, then run a screening to inspect the evidence.
Reproducible rules
Sources and limitations
Downloadable audit trail
No wallet needed to screen
03 / FOLLOW THE SIGNALS
Evidence, with its edges visible.
Two source adapters
Fire activity
Awaiting screening
Hotspot detections can flag a potential disturbance requiring closer inspection.
Sources, dates and rule contributions appear here.
Weather context
Awaiting screening
Historical precipitation adds context, without inferring verified carbon tonnes.
Sources, dates and rule contributions appear here.
EVIDENCE EXPLANATION
Transparent reasoning. No invented assurance.
AI explains the supplied evidence within a validated schema. The versioned rule engine owns the score. A readable template is always available.
TAMPER-EVIDENT AUDIT
Anchor the evidence
Base Sepolia
Register claim and report hashes, score, year and submitted cells. Hashes prove integrity, not truth or availability.
Connect a wallet to anchor a report.
Contract trust boundary: cells and scores are supplied by the caller. The contract cannot verify polygon coverage or attest the screening. Coarse cells can conflict for nearby, non-overlapping polygons.
Registry activity 0
No confirmed transactions in this browser. Screening works without a wallet.
Activity is a browser-local index of confirmed writes, refreshed against the contract. Record retirement is not retirement of a recognized carbon credit.