Open Carbon Protocol Handbook
  • Welcome to the Open Carbon Protocol
  • The OCP Process Overview
  • Back to the OCP
  • GOVERNANCE
    • OCP Governance Structure
      • OCP Board
    • Conflict of Interest
    • Annual Audit Process
    • Stakeholder Engagement & Complaints
    • Business Model & Financial Transparency
    • OCP Sustainability: Environmental and Social Strategy
    • KYB & Anti-Money Laundering Policy
    • Anti-Bribery and Corruption Policy
  • METHODOLOGIES
    • Methodology Development, Feedback & Approval
      • Underlying Credit Value & Uncertainty
      • Methodology Demo Videos
      • OCP Methodology Requirements
    • The Expert Community
  • PROJECTS
    • Project Proposal Flow
      • Project Proposal and Validation Demo Videos
    • Third-Party Validation and Verification
      • dMRV: Digital Monitoring Reporting and Verification
    • Safeguards, Co-Benefits & SDGs
    • Mitigating Project Risk: Insurance and Buffer Pool
  • REGISTRY
    • The OCP Registry Infrastructure
      • Opening and Closing an Account
    • Credit Issuance Flow
      • Retirement Information
    • No Double Counting
    • Registry Information
Powered by GitBook
On this page
  1. REGISTRY

Registry Information

PreviousNo Double Counting

Last updated 1 month ago

  • Our registry has a human-centric information design, allowing buyers & other stakeholders to see the most important information first.

  • All files related to the project proposal flow + data are clearly named and organized in an easy-to-read format and made publicly available. This lets project developers highlight impact & helps buyers conduct due diligence.

  • This includes:

    • Specific information related to how emissions were calculated such that the process can be replicated

    • Environmental and Social Impact Report

    • Methodology used: including how the project meets baselines and additionality requirements [See ]

    • Label to indicate if the project uses a methodology that is CCP or CORSIA-approved.

    • Deviations from the methodology

    • Validation reports

    • Verification processes / dMRV information

    • Stakeholder engagement efforts, including all public comments received and resolutions

  • The project status is also displayed. A project can either be:

    • Active = validated project, before Project Expected End Date

    • Completed = validated project, after Project Expected End Date

    • On Hold = manual status update by admin; no more credits can be issued

    • Canceled = manual status update by admin; no more credits can be issued

  • Project data is stored on-chain with a token identifier in the format of:

    (project id + monitoring period + token id) [ epoch timestamp as monitoring period]

Project Proposal and Validation Demo Videos