7G CarbonPlatform — a single digital core for carbon accounting

• GHGMRV

  Industry and energy

  Emissions by site and source, GHG Protocol reporting, a baseline for modernisation projects.

• CBAMGHG

  Exporters to the EU

  Specific emissions per tonne of product for CBAM declarants — from the same data as corporate accounting.

• PCAF

  Banks and investors

  Financed emissions of the lending and investment portfolio under the PCAF standard, with a data quality score.

• MRVMarket

  Climate project developers

  Project passport, monitoring, three-node review and a package ready for verification and unit issuance.

• Market

  Carbon unit buyers

  A transparent history of every unit: project, vintage, serial number, transfers and retirement.

• MarketMRV

  Government bodies

  The national registry receives verified packages, and the claims registry prevents double counting between countries.

• GHGCorporate accountingCompany emissions across Scope 1, 2 and 3: boundary, sites, sources, reporting.carbonplatform.asia — opens in a new tabLearn more in the knowledge base — GHG
• PCAFFinanced emissionsEmissions of the lending and investment portfolio, data quality score 1–5.carbonfin.asia — opens in a new tabLearn more in the knowledge base — PCAF
• MRVProject MRVReduction projects: baseline, monitoring, calculation and preparation for verification.carbonmodel.asia — opens in a new tabLearn more in the knowledge base — MRV
• CBAMCarbon Border AdjustmentEmbedded emissions in goods exported to the EU: installation, calculation, supply.carboncbam.asia — opens in a new tabLearn more in the knowledge base — CBAM
• MarketCarbon marketProject, result, carbon unit and claim — in one chain.carbonmarket.uz — opens in a new tabLearn more in the knowledge base — Market

• REG-PProjects registryProjects, final MRV records and their hashes — in the consortium's private registry
• REG-CClimate claims registryClaims and retirements · access point registry.carbonmarket.asia · [name to be confirmed]
• NAT.National unit registryIssuing units is a state power. Each country has its own server and domain zone

1. 01

   Primary data

   The company enters fuel and energy use and attaches invoices and certificates.

   Company
2. 02

   MRV calculation

   A versioned module and factors; the input data is stored with the result.

   TER
3. 03

   Operator review

   Data schema, documents, control ratios, report hash.

   HPBS
4. 04

   Independent review

   Engineering parameters, sources and reproducibility of the calculation.

   EIS
5. 05

   3 of 3 confirmation

   Network confirmations from three validators, publication and a copy on every node.

   TER + HPBS + EIS
6. 06

   External verification

   An accredited verifier confirms the volume of reductions.

   Verifier
7. 07

   National registry

   Issuance and serial numbers of units — the country registry's decision.

   State

1. 01

   Registration by INN

   The organisation is found in the registry by its INN; the email is confirmed with a code.

   ≈ 5 minutes

2. 02

   Choosing a contour

   On the home page — GHG, PCAF, MRV, CBAM or Market. The rest can be added later.

   1 minute

3. 03

   Sites and staff

   Sites, their contours and employees with access to their own sites.

   10–15 minutes

4. 04

   First data

   Fuel and energy use for a quarter — emissions are calculated right away.

   ≈ 5 minutes

• TER

  Total Energy Recovery LLC

  Uzbekistan · Project MRV

  • Develops the Project MRV module and calculations
  • MRV report and technical review of input data
  • Its own validator node
• HPBS

  HPBS LLC

  Uzbekistan · platform operator

  • Interface, user and project registration
  • Operator review, report hash, initiating and publishing records
  • API, Blockchain Gateway and its own node
• EIS

  Ecoengineering-stroy LLC

  Belarus · independent review

  • Independent engineering review of parameters and evidence
  • Reproducibility check and independent hash confirmation
  • Its own node; recusal in case of a conflict of interest

• 3 of 3final and critical records: issuance, transfer, retirement, correction. The threshold never drops to 2 of 3 — if a node is down, finalisation waits
• > 2/3 · 75%after expansion: regular final records need more than two thirds of validators, critical ones at least 75% including two founders
• Recusala validator with a conflict of interest does not vote; a temporary independent validator is appointed for the record

External verification of a project stays with an independent accredited verifier — none of the three parties replaces it. A node confirmation is not a digital signature: legally binding documents are signed separately. The v2.3 rule set (10 documents) is being signed — until then the network runs as a pilot.

• Documents stay off-chain

  Reports and calculations are kept in protected storage; the registry holds the SHA-256 hash, status, time and signatures.

• Nothing is deleted

  A wrong record is corrected by a new record with a reason; the original stays in the history.

• Separate keys and nodes

  The parties' nodes run on independent infrastructure; private keys are never shared.

• Two-factor sign-in

  Least-privilege access, an activity log and regular access reviews.

• GHG ProtocolCorporate · Scope 3 · Project
• ISO 14064-1organisational inventories
• ISO 14064-2reduction projects
• IPCC 2006factors and methods
• PCAF 2025financed emissions
• IFRS S1 / S2climate risk disclosure
• CBAMEU Regulation 2023/956
• Verra VCS v5voluntary crediting
• Article 6Paris Agreement

Regulatory mapKnowledge base