Platform · Layer 02

The auditor does not work for the audited.

Verifiers are assigned by rotation from an accredited pool and paid by the registry. Developers never choose, never pay, and never see the assignment in advance.

0
Developer-selected verifiers
100%
Registry-funded
Rotation
Assignment method
Public
Every attestation

Why this is structural, not a promise

In most of the voluntary market, the project developer selects their verifier and pays the fee. Everyone involved may act in good faith, and the incentive still points one way: a verifier who raises hard findings is a verifier who is not rehired.

Financial audit solved this decades ago by separating who selects the auditor from who is audited. We applied the same separation. Verifiers are drawn from an accredited pool by rotation, their fee comes from a pooled levy on issuance, and no developer can request or refuse a particular firm.

It costs us more to run and it slows issuance down. It is also the only version of independence that survives being asked how it works.

What a verifier checks

Five checks before a batch is signed

01
Instrument integrity
Calibration in date, no gaps in the log, no unexplained interruptions
02
Cross-stream agreement
Field readings reconciled against satellite and lab results
03
Methodology application
Correct version applied, with every input traceable
04
Site inspection
Physical visit for first issuance and on a rolling sample thereafter
05
Safeguards
Land rights, consent, and benefit-sharing evidence still current
Next layer

A signed batch becomes a public record

Verification ends with an attestation. The registry is where that attestation becomes permanent and checkable by anyone.