Skip to content

Commit ee10c03

Browse files
authored
Merge pull request hashgraph#2402 from l-rajeev/patch-1
Update README.md
2 parents c4a6897 + 85754e6 commit ee10c03

File tree

1 file changed

+96
-38
lines changed

1 file changed

+96
-38
lines changed

Methodology Library/KrypC/README.md

+96-38
Original file line numberDiff line numberDiff line change
@@ -1,47 +1,58 @@
1-
# KrypC CarbonCore Policy – Global Carbon Council
1+
# KrypC Carbon Core Policy – Global Carbon Council
22

3-
### KRYPC CARBONCORE GUARDIAN POLICIES
3+
### KrypC Guardian Policy Template Methodologies
44

5-
The purpose of this document is to policy for renewable power generation project using Global Carbon Council Methodology. KrypC CarbonCore platform will use the GCCM0001 methodology to create the policy for tokenization of the carbon credit via Hedera Hashgraph technology.
6-
The policy facilitates the project owners of eligible greenhouse gas (GHG) reduction projects to calculate emission reduction of their projects, monitor the emission reductions and develop the project submission in accordance with the methodologies.
5+
KrypC has developed a custom policy for Renewable Energy Generation projects using Global Carbon Council (GCC) Methodology. The policy facilitates the project owners of eligible Green House Gas (GHG) reduction projects to calculate, monitor the emission reductions of their projects and to develop the project submission in accordance with the methodologies.
76

8-
The policy refers to the methodology for renewable power generation projects, which either supply power to the connected grid or to recipient captive user for captive consumption (here onwards referred as “the project activity”) facilitates the projects that displace the electricity which would be provided to the grid by more emission-intensive mix of power sources, than that established under project activity. The power generated from the Renewable sources can be either directly sold to the grid or used for captive consumption or can be stored in a Battery storage solution (BESS) attached to renewable energy generation plant and then delivered to the grid or used for captive consumption.
7+
In this document will take you through the process of Guardian Policy Integration for any product team.
98

10-
### SPECIFICATIONS
9+
KrypC Carbon Core platform is using the GCCM0001 methodology for Renewable Energy Generation Projects Supplying Electricity to Grid or Captive Consumers to create the policy for tokenization of the carbon credit via Hedera Hash graph technology.
1110

12-
This Policy can be used for renewable power generation projects, which either supply power to the connected grid or to recipient captive user for captive consumption (here onwards referred as “the project activity”) facilitates the projects that displace the electricity which would be provided to the grid by more emission-intensive mix of power sources, than that established under project activity.
11+
The power generated from the Renewable sources can be either directly sold to the grid or used for captive consumption or can be stored in a Battery storage solution (BESS) attached to renewable energy generation plant and then delivered to the grid or used for captive consumption.
1312

14-
The source of the methodology for the policy is taken from Global Carbon Council (GCC) methodology number GCCM0001 - Methodology for Renewable Energy Generation Projects Supplying Electricity to Grid or Captive Consumers. We will use updated versions of the documentation as and when they are released through the GCC.
13+
### The different actors within KrypC policies
1514

16-
### POLICIES
15+
Below Four different types of users involved in Carbon Core platform.
1716

18-
The policy is based on following baseline and monitoring methodologies of CDM/GCC.
17+
• Admin - Onboard system users and project owner
1918

20-
ACM0002: Grid connected electricity generation from renewable sources; and
19+
CC Consultant - Manages Project Documentation outside of the Guardian and transcribes into the Guardian.
2120

22-
AMS-I-D: Grid connected renewable electricity generation.
21+
Auditor - Reviews monitoring reports and approve/reject.
2322

24-
AMS I F: Renewable energy generation for Captive use and mini grid
23+
Project Owner – A person who is considered as the owner of the offsets and has complete access to it.
2524

26-
The policy also refers to the latest approved versions of the following tools and guidelines of CDM/GCC:
2725

28-
a) “Tool to calculate the emission factor for an electricity system”
26+
### Emission Calculation using Guardian Middleware API
2927

30-
b) “Tool to calculate baseline, project and/or leakage emissions from electricity consumption and monitoring of electricity generation”.
28+
The policy is based on following baseline and monitoring methodologies of CDM/GCC;
29+
30+
• ACM0002: Grid connected electricity generation from renewable sources; and
31+
32+
• AMS-I-D: Grid connected renewable electricity generation.
33+
34+
• AMS I F: Renewable energy generation for Captive use and Mini grid
35+
36+
The policy also refers to the latest approved versions of the following tools and guidelines of CDM/GCC;
37+
38+
• Tool to calculate the emission factor for an electricity system.
39+
40+
• Tool to calculate baseline, project and/or leakage emissions from electricity consumption and monitoring of electricity generation.
41+
42+
• Tool for Demonstration and Assessment of Additionality.
3143

32-
c) “Tool for Demonstration and Assessment of Additionality”
3344

3445
**Baseline emissions**
3546

36-
Baseline emissions include only CO2 emissions from electricity generation in power plants that are displaced due to the project activity. The policy refers to the methodology that assumes that all project electricity generation above baseline levels would have been generated by existing grid connected power plants and the addition of new grid-connected power plants. The baseline emissions are to be calculated as follows:
47+
This includes only CO2 emissions from electricity generation in power plants that are displaced due to the project activity. The policy refers to the methodology that assumes that all project electricity generation above baseline levels would have been generated by existing grid connected power plants and the addition of new grid-connected power plants. The baseline emissions are to be calculated as follows:
3748

3849
**BEy = EG BL,y × EFCO2,y**
3950

4051
**EFCO2,y = EF grid,CM,y**
4152

4253
**Project Emissions**
4354

44-
Under this policy we assume that most renewable energy project activities, project emissions are equal to zero
55+
Under this policy we assume that most renewable energy project activities, project emissions are equal to zero.
4556

4657
**PEy = 0**
4758

@@ -53,14 +64,16 @@ As per methodology used in this policy, no leakage emissions are anticipated
5364

5465
**Estimation of emission reductions**
5566

56-
As per policy referred from section 12 of GCCM001 V3.0, the formula to calculate the emission reductions is
67+
As per policy referred from section 12 of GCCM001 V3.0, the formula to calculate the emission reductions is followed.
5768

5869
**ERY=BEY-PEY-LEY**
5970

60-
### FORMAT OF REFERRED FOR THE CREATION OF THE POLICY SHOWN BELOW
71+
### Schema
6172

6273
**Project Details**
6374

75+
The following are subsets of common attributes specific to a project.
76+
6477
| Schema Type | Questions | Allow Multiple Answers | Answers | Source of Data |
6578
|---|---|---|---|---: |
6679
| Strings | Project Scope | No | GHG-SS 1 (Energy (renewable/non-renewable sources) | Project Consultant
@@ -79,10 +92,12 @@ As per policy referred from section 12 of GCCM001 V3.0, the formula to calculate
7992
| Date Range | Project Crediting Period | Yes | Date | Project Consultant
8093
| Date Range | Monitoring Period | Yes | Date | Project Consultant
8194
| Strings | GHG source | Yes | Fossil Fuel/Natural Gas | Project Consultant
82-
| Strings | Monitoring Pla | Yes | Based on the methodology "GCCM001" | Project Consultant
95+
| Strings | Monitoring Plan | Yes | Based on the methodology "GCCM001" | Project Consultant
8396

8497
**Baseline Scenario Emission**
8598

99+
The following are subset of common attributes specifically to submit the predictive data estimated to reduce the emissions.
100+
86101
| Schema Type | Questions | Allow Multiple Answers | Answers | Source of Data |
87102
|---|---|---|---|---: |
88103
| Value | Operating Margin | No | 0.5859 | (Referenced Source)
@@ -93,6 +108,8 @@ As per policy referred from section 12 of GCCM001 V3.0, the formula to calculate
93108

94109
**Project Scenario Emission**
95110

111+
The following are common attributes specific to a project’s electricity generation.
112+
96113
| Schema Type | Questions | Allow Multiple Answers | Answers | Source of Data |
97114
|---|---|---|---|---: |
98115
| Value | Project Capacity | Yes | 15.94 | Project Owner
@@ -102,36 +119,77 @@ As per policy referred from section 12 of GCCM001 V3.0, the formula to calculate
102119

103120
**Calculation of Emission Reduction**
104121

122+
A subset of the Common Attributes specifically to submit the monitoring report. Based on meter data emission values are calculated.
123+
105124
| Schema Type | Questions | Allow Multiple Answers | Answers | Source of Data |
106125
|---|---|---|---|---: |
107126
| Value | Panel Efficiency Module | No | 21.1 | Manufacturer
108127
| Value | Panel Degradation second year onwards | No | 0.55% | Manufacturer
109-
| Auto Calculated | Net GHG Reduction (2022 -23) | Yes | 13682.13547 | System Generated
128+
| Auto Calculated | Net GHG Reduction (2022 -23) | Yes | 13682.14 | System Generated
129+
130+
**Guardian Policy Workflow Process**
131+
132+
![policy_workflow](https://github.com/hashgraph/guardian/assets/134472833/758c8fcc-c6c8-4995-baca-892a9c0d8a6d)
133+
134+
Admin gets the Organization/Project owners information based on offline communication according to due diligence which is part of onboarding process. Then admin adds them to the system.
135+
136+
**Adding Project details & Predictive data**
137+
138+
Consultant creates a project based on offline communication with Project Owners/Organizations and adds ex ante data. A wallet was created for project owners at the time of the first project creation.
139+
140+
![grid1](https://github.com/hashgraph/guardian/assets/134472833/8e2c0fa8-8ac5-4b38-8cf8-f88af3f634cd)
141+
142+
**Onboarding Meters, Submission & Verification of MRV data**
143+
144+
Consultants need to add devices, set the configuration and share it to Project Owners. They install it in devices which then send the MRV data to the system.
145+
146+
![grid2](https://github.com/hashgraph/guardian/assets/134472833/46161b0f-34bb-4d74-b987-5606afd2c778)
147+
148+
**Verification of Emission Reduction, Issuance of certificate & Minting Carbon Credits**
149+
150+
Consultant will prepare monitoring report and Emission values are calculated using the data captured from meter. Then he submits the monitoring report to the Auditor for approval.
151+
Auditors issue the certificate on approval. Then the Consultant uploads the issued certificate, then tokens minted and transferred to project owner’s wallet.
152+
153+
![grid3](https://github.com/hashgraph/guardian/assets/134472833/34b7f802-0742-4d56-a1b0-a31171ce78b6)
154+
155+
156+
### Policy Versioning
157+
158+
KrypC's policies will continue to evolve based on our ongoing requirements, we will do our best to update them within this repository, however, please reference our primary guardian policies repository for all up-to-date versions.
159+
160+
### KrypC’s Carbon Core Process
161+
162+
KrypC Carbon Core platform provides solutions for all parties simplifying the entire process making Carbon trading market safe, reliable, efficient, convenient, open and inclusive. It acts as ledger for creating the trust chain for the verified carbon units and verified emission reductions created. The platform also helps in verifying and minting carbon offset tokens and will lend its credibility towards 'high-quality' credits, attracting higher prices and allowing more funding to projects.
163+
KrypC Carbon Core Platform tokenizes the carbon credits via Hedera Hash graph technology. This will be following steps;
164+
165+
• Create specific architecture and libraries for the Project listing process and documentation for various registries.
166+
167+
• Create MRVs, Architecture, and Libraries for carbon project listing processes and documentation on Hedera.
168+
169+
• Tokenize and mint tons of carbon offsets (tC02e).
170+
171+
• Complete the build with KrypC’s carbon solution platform as a ledger for creating the trust chain for the VCUs/VERs created by any stakeholder/partner.
172+
173+
• Recognizes different VERs/VCUs of by virtue of running a ‘pricing matrix’ of different ‘series of tokenized VERs/VCUs with the aim of having strong liquidity.
110174

111-
### UNDERSTAND KRYPC'S CARBONCORE FROM A HIGH-LEVEL
175+
• Link to KrypC's Carbon solution for a full end-to-end platform for tokenized VCUs/VERs.
112176

113-
KrypC CarbonCore platform provide solution for all parties simplifying the entire process making Carbon trading market safe, reliable, efficient, convenient, open and inclusive. It acts as ledger for creating the trust chain for the verified carbon units and verified emission reductions created. The platform also help in verifying and minting carbon offset tokens will lend its credibility towards 'high-quality' credits, attracting higher price and allows more funding to projects.
114177

115-
KrypC CarbonCore Platform tokenized the carbon credits via Hedera Hashgraph technology. This will follow a few detailed steps:
178+
**High level process flow of KrypC’s Carbon Core Platform**
116179

117-
• Create specific architecture and libraries for the Project listing process and documentation for various registries
180+
<img width="512" alt="high" src="https://github.com/hashgraph/guardian/assets/134472833/fce9ddfb-3287-438b-902d-d4f5d2572eff">
118181

119-
• Create MRVs, architecture, and libraries for carbon project listing processes and documentation on Hedera
182+
### Carbon Core Project Flow Example
120183

121-
• Tokenize and mint tons of carbon offsets (tC02e)
184+
Following are the steps to onboard organizations, create projects and minting of carbon credits.
122185

123-
• Complete the build with KrypC’s carbon solution platform as a ledger for creating the trust chain for the VCUs/VERs created by any stakeholder/partner
186+
<img width="467" alt="flow" src="https://github.com/hashgraph/guardian/assets/134472833/dc955cc2-f301-4b66-8fd7-c8376e964217">
124187

125-
• Recognizes different VERs/VCUs of by virtue of running a ‘pricing matrix’ of different ‘series of tokenized VERs/VCUs with the aim of having strong liquidity available
188+
### Technical Architecture
126189

127-
• Link to KrypC's Carbon solution for a full end-to-end platform for tokenized VCUs/VERs
190+
Project creation and other activities happened through Carbon Core UI which then hits the related API services. Client and Admin/Consultant communication is though Jira. Once the policy is created guardian API will be called. Documents stored in IPFS. All the actions are saved in the database.
128191

129-
**The overall following flow will be followed by KrypC CarbonCore:**
192+
![arch](https://github.com/hashgraph/guardian/assets/134472833/e89c8f8a-b7ca-4cd1-8791-6ab84e3293d0)
130193

131-
<img width="800" alt="image" src="https://user-images.githubusercontent.com/79293833/218481408-3421ed7b-3f2b-404f-bdfd-d0aba3ab7aab.png">
132-
133-
### OVERVIEW OF THE KRYPC CARBONCORE ONBOARDING FLOW
134194

135-
Below are the steps for onboarding to minting of carbon credits.
136195

137-
<img width="800" alt="image" src="https://user-images.githubusercontent.com/79293833/218481487-400aef7f-78f3-490c-a2e1-75533b454c33.png">

0 commit comments

Comments
 (0)