Green Proofs · Meta Proofs

Registry interoperability
and synchronization.

Meta Proofs is a cross-registry verification service. It streamlines the export and import of EACs across different registries, no matter the registry operator. It also checks that a project isn't listed across multiple registries and that a claim hasn't already been issued, transferred, or retired by a peer registry, using privacy-preserving matching against hashed identifiers, not raw data exchange. The result: integrated, continuous, lower-cost assurance about the integrity of market instruments for consumers.

How it works → Talk to the team
The interoperability between registries

The registry ecosystem faces export-import integration challenges and double-issuance risks.

Registries don't currently synchronize with each other on a continuous basis. Instead, they rely on manual processes, validations, and corrections. This creates administrative costs for reconciling discrepancies and harmonizing trade across registry systems. The same megawatt-hour of verified clean energy can also be unintentionally issued and claimed in a national and voluntary EAC registry, or across two, reducing trust in the system and creating costs associated with the currently manual processes required to address incidents. Meta Proofs serve as a verification layer that connects the dots between registries and provides continuous assurance.

Gap 01 · Uniqueness
"Has this project been registered
or this attribute claimed elsewhere?"
While registries excel at managing and reconciling their own records, they face a critical visibility gap: proving that a physical event has not also been recorded elsewhere, particularly when claims span different jurisdictions, asset classes, or commodities.
What breaks
  • Cross-registry double-registration and double-issuance
  • Export / import related claims
  • Mixed asset-class accounting
Gap 02 · Methodology
"Was the same rule
actually applied?"
Two registries may claim to follow the same methodology yet produce different outcomes due to variations in versions, parameters, or interpretation of the underlying rules. As a result, buyers have limited ability to verify alignment downstream.
What breaks
  • Untracked methodology drift
  • Parameter mismatches
  • Silent rulebook version skew
Gap 03 · Privacy
"Can registries cross-check
without merging?"
Registries hold sensitive commercial, regulatory, and market data that cannot be openly shared. Cross-registry verification must deliver trust and assurance while keeping the underlying records private.
What breaks
  • Counterparty confidentiality
  • Jurisdictional data residency
  • Selective disclosure to buyers
A proof of proofs

One verification,
composed from many registries.

A Meta Proof composes evidence from each source registry, a hashed identifier of the underlying record, the rulebook version that issued it, the operator's signature, runs them through a privacy-preserving match, and emits one verifiable result. No raw data leaves the source registry. Operators and data stay sovereign; the proof is what travels.

Registry · A
National GO registry
Issues renewable-electricity certificates under jurisdictional rulebook.
Registry · B
Voluntary carbon program
Issues offsets under an independent methodology & vintage schema.
Registry · C
Corporate disclosure ledger
Records Scope 2 / 3 claims tied to specific consumption events.
Meta Proof engine
Compose · Cross-check · Anchor
VCC Compute nodes verify uniqueness, methodology alignment, and operator signatures in parallel. Result is anchored on-chain.
Output · 01
Cross-registry uniqueness proof
"This attribute has not been claimed in any of A, B, C as of block N."
Output · 02
Methodology-alignment receipt
All source records were issued under compatible rulebook versions.
Output · 03
Re-verifiable evidence pack
Regulators or buyers re-run the proof against the same commitments.
Where Verified Compute Cloud is in development

Already in flight across CBAM, CSRD, SAF compliance and other supply chains.

Verified Compute Cloud is piloted across registries, market operators and assurance providers that run these markets. Each pilot is shaped around a specific regulatory framework and the pilots draw on the same foundations: uniqueness, methodology alignment and evidence anchoring.

Corporate disclosure · Pilot
Real-time ESG verification
Digital control environments and continuous data validation that reduce the cost of preparing and auditing sustainability data for CSRD reporting, working across the data systems an enterprise already uses.
What it enables
  • Machine-verifiable evidence packs that preserve data lineage, calculation logic, and execution trails
  • Continuous data validation that reduces preparation cost and re-work for assurers
  • MRV aligned with ISO 14065 and ISO 17029 to support faster sign-off
Trade · Pilot
Green import verification for carbon border schemes (CBAM)
Continuously verified evidence packs that document an importer's lower-carbon inputs, packaged consistently for carbon border scheme verifiers and delivered on demand.
What it enables
  • Machine-verifiable evidence packs for lower-carbon imports
  • Audit trails prepared for carbon border scheme verifiers, on demand
  • A lower-cost route to avoiding carbon border fees
Aviation · Pilot
Verified SAF compliance for aviation
Machine-verifiable evidence bundles that document an operator's sustainable aviation fuel use and compliance position, packaged consistently for accredited aviation verifiers and surfaced through a Verified Data Explorer.
What it enables
  • Machine-verifiable evidence bundles that preserve proof of sustainability, mass-balance chain of custody, and the calculation logic linking SAF to specific flights
  • Cross-operator duplicate detection and automated reference-data resolution (emission factors, feedstock pathways) that reduce verifier back-and-forth over document quality
  • Verification aligned with ReFuelEU Aviation (EU) 2023/2405, with correctness confirmed by accredited, independent verifiers to support faster sign-off ahead of the annual deadline

More to be announced soon.

Outcomes

What Meta Proofs unlock at market scale.

Cross-registry verification turns a fragmented patchwork of registries into a harmonized system that maintains registry operator control and independence.

Benefit 01
Cross-registry
uniqueness.
A claim's underlying event is checked against every participating registry before issuance, eliminating the most common form of double counting at its source.
Benefit 02
Methodology
alignment.
Rulebook versions are signed and version-pinned. Counterparties can verify that two records under "the same methodology" actually used identical logic, such as the protocol that registries use for identity management among registered projects.
Benefit 03
Privacy-preserving
cross-checks.
Workers verify commitments, not raw records. Counterparty identities, pricing, and confidential parameters never leave the source registry.
Benefit 04
Mutual recognition,
by construction.
Regulators and buyers can accept claims from one registry on the strength of a Meta Proof, without bilateral, registry-by-registry trust agreements.
Cross-registry integrity

Close the seams
between markets.

If you operate a registry, run a regulatory program, or design verification for a market that touches more than one ledger, we want to hear what you're verifying, and where the seams are leaking.

Talk to the team → Explore solutions
Note Meta Proofs are open source and built for shared governance. Methodologies, worker logic, and the verification rulebooks are all public.