Credits issued under your registry can be sold to emissions allowance programs through ORIGIN. Your methodology, MRV, verification and registry records stay within your framework. Retirements are recorded in your registry with named beneficiaries, and provenance stays traceable to your record.
Everything that establishes environmental integrity.
PVN references these sources. It does not generate them, alter them, independently assess them, or substitute for the organizations and processes responsible for them.
Methodology selectionYours to choose and defend. The applicable methodology and its requirements remain with the registry, program, or responsible project framework.
MRV dataReferenced, never rewritten. PVN uses defined references to the underlying evidence. It does not modify the source MRV record.
Verifier relationshipsYours to manage. Origin Ledgers does not select, replace, or independently attest to the verifier responsible for environmental verification.
Registry recordsYour registry remains the system of record. PVN can reference registry status and relevant evidence for digital lifecycle validation. It does not replace or modify the registry record.
How credits issued under your registry reach programs
From a developer’s listing to a named program.
01ListedA project developer lists credits issued under your registry.
02ValidatedPVN checks it against ORIGIN's published eligibility rules.
03AllocatedOrigin Ledgers buys it and holds it for a named program in its account in your registry.
04AssignedA program credit is placed with a specific participant position.
Joining takes four steps: approval against our criteria; integration, by API or documented process; an Origin Ledgers account opened in your registry; and a live test of status, transfer, retirement and confirmation. The approved registries are published.
What a separate validation layer adds to your credits' lifecycle.
PVN validates the Origin Ledgers lifecycle events that involve your credits — allocation, assignment, retirement confirmation — and reconciles expected against recorded state. It reads your registry records; it never writes to them.
01
Deterministic checksThe same cCRBX record, evaluated twice against the same versioned lifecycle rules and inputs, produces the same result. The purpose is repeatability: a reviewer can reproduce the validation outcome against the defined conditions.
02
ReconciliationExpected state is compared with recorded state for each event. Differences remain visible. Partial or inconsistent settlement is not silently treated as complete.
03
An evidence trailValidation run references, reconciliation results, state transitions, and related decisions are recorded as part of the lifecycle. The result is a reviewable history of what was checked, against which rules, and what the system recorded — rather than an audit trail reconstructed after the fact.
How data reaches PVN
By reference, not by copy.
PVN does not ingest or replace your registry. It validates defined lifecycle events that reference records in it. Three things are established for the validation relationship. After that, each event carries the references and data required for its own validation.
Established once
Program & asset referencesYour project and registry identifiers are mapped to the relevant cCRBX asset references. The mapping establishes how the digital event relates to the underlying registry record. PVN does not become a duplicate registry.
Established once
A validation profileThe rules against which events are checked — including eligible asset classes, quantity tolerances, required references, and permitted lifecycle transitions for the applicable program. The profile is versioned so a reviewer can identify which rules applied to a particular event.
Per event
The lifecycle event itselfAn allocation, assignment, settlement or retirement event carries its relevant references, expected quantities, and lifecycle information. PVN validates the event, reconciles expected against recorded state, and records the resulting validation outcome.
What we do not require: you do not need to hand over your MRV archive, verifier correspondence, or underlying project documentation simply for PVN to perform digital lifecycle validation. Where a review requires environmental or project-level evidence, that evidence remains with the registry, project developer, verifier, or other responsible source. PVN can reference the relevant record; it does not replace it.
Worked example · dummy data
What a failed event looks like.
RUN-00812 · cCRBX-2026-0417 · Program CVP-14Selected stages · Illustrative
Stage 01 of 07pending
Program & asset intake
cCRBX-2026-0417 enters the workflow under program CVP-14. Intake confirms that the asset reference is mapped and the program is admitted. It authorizes nothing.
What the example provesA partial result does not become a partial success. A hold does not become completion. Validation does not become authorization. The system preserves what happened, records why the event stopped, and leaves the event outside completed until the required conditions are actually satisfied.
Approved registries are the issuing standards for credits sold through ORIGIN. They are not parties to the sale and pay no fees. Origin Ledgers plans to give registries visibility of aggregate program demand; it is not live today.
Sale of creditsOrigin Ledgers to buyersNot a registry party
RetirementRecorded in your registryBeneficiary named
Aggregate demand visibilityPlanned
Reviewer questions
What this page is asked most
Environmental evidence — MRV records, registry records, methodology, and verifier attestations — remains a distinct source. PVN references that evidence where required for the digital lifecycle, but does not generate, alter, or independently judge it. A validation result records what was checked against the referenced information and applicable rules. It does not absorb or replace the underlying environmental determination.
Bring your registry's lifecycle rules. We'll show you the run.