Recourse reads the registry and watches the forest. If a credit is recalled, it can't be used, and whoever paid for it is refunded.
A registry hold, a satellite alarm or a published finding becomes a state every buyer, exchange and auditor can read, and a rule the contracts enforce.
Verra's own API response is proven with a zkTLS proof and checked inside the contract. The request is pinned byte for byte, so the status on-chain is the status Verra served.
A satellite detector compares Sentinel-2 dry seasons inside each project boundary. A notice reader extracts holds, withdrawals and over-issuance findings from public statements. Both sign their output; nothing acts until a reviewer confirms or the dispute window closes.
The credit gate refuses recalled or on-hold credits at the point of use. A retirement backs one claim only. A warranty escrow pays the buyer back from the holdback when a recall lands.
Verra lists 290 projects as on hold or withdrawn. Their credits are still held, still listed on exchanges, and still retired into corporate claims.
Source: Verra's public registry data (S&P Global platform), read 21 Oct 2026; snapshot sha256 0xd2e9a3ce68…. All exposure numbers
When a finding is confirmed, the recall is a single on-chain state. Exchanges, claim registers and escrows read the same state, so the consequence arrives everywhere at once.
Every number links to its source. Every model was scored against a pre-registered protocol. Every evidence bundle verifies in your browser.
Paste a Verra serial number. You get a verdict for general use, CORSIA, Türkiye's ETS and VCMI claims, read from the contracts.