> For the complete documentation index, see [llms.txt](https://open-carbon-protocol.gitbook.io/ocp-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://open-carbon-protocol.gitbook.io/ocp-handbook/registry/registry-schema-and-infrastructure.md). # Registry Schema and Infrastructure The OCP Registry combines best-in-class technical infrastructure with human-centric information design. ## Registry Infrastructure * We are working to integrate with the [Climate Action Data Trust](https://climateactiondata.org/) (CADT), reducing double counting risk and ensuring credit data is tracked long-term. * Our registry is blockchain-based, with credits issued and data stored on a Celo blockchain, so credit data is unchangeable and easy to audit. No cryptocurrency component. * **This is not the same as tokenization**. Our issued credits are 'non-fungible' (each is unique, with an identifying code linking it back to issuance, project, and methodology). #### Registry Security Our carbon credit registry leverages blockchain technology's immutable ledger and cryptographic protocols to ensure unprecedented security and transparency in tracking carbon credits. Every transaction is cryptographically signed, permanently recorded, and verified by a distributed network of nodes, making unauthorized alterations or fraudulent entries virtually impossible. #### Data Management and Security The OCP stores project documentation and data securely on Amazon Web Services (AWS), which has multiple layer security and has built-in back-up and recovery. [You can read more about AWS’s data protection and security here](https://aws.amazon.com/compliance/data-protection/). Data related to credits (issuance data, quantity, ownership, status etc.) is also stored on the Celo blockchain. The OCP team also runs monthly offline back-ups of methodology and project data. As part of the validation and reporting/issuance processes, the project developer and other project partners will report project data to the OCP. All data related to quantification will be made publicly available on the OCP registry. All other project documentation and data will be made available on the OCP registry, with exemptions granted for confidential information, as flagged by the relevant parties. Project Developers should develop separate data management systems depending on their requirements. ## Registry Information Schema 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 [Project Proposal and Validation Demo Videos](/ocp-handbook/projects/demo-videos-project-proposal-validation-verification.md)] * 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]* {% hint style="info" %} [Our Beta API Documentation can be found here](https://www.notion.so/oneshot-earth/OCP-API-Documentation-2020e7075b5e80d1ba3cee45b45fddae?source=copy_link). Please contact to discuss integrations. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://open-carbon-protocol.gitbook.io/ocp-handbook/registry/registry-schema-and-infrastructure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.