This is an implementation of the audited emissions data channels from the Operating System for Climate Action.
Let's take a look at a very specific use case: a permissioned Hyperledger Fabric channel where an auditor calculates the emissions of a customer's electricity based on its utility bill. The same pattern could be repeated for other data services (travel, commute, shipping, etc.)
Imagine a network with multiple utilities, emissions auditors, and customers:
Customer would like to get audited GHG CO2 emissions for the energy it purchased from Utility.
Emissions from energy purchased by a company need to be calculated according to Greenhouse Gas Protocol Scope 2. In GHG Protocol Scope 2 Guidance (see pages 11 and 26), the emissions for purchased energy should be calculated from utility bills and emission factors, which should be based on local source if available, then grid and finally national level data if more precise data is not available.
In the United States, the Emissions & Generation Resource Integrated Database (eGRID) is a source of audited emissions factors for different utilities and grids.
The first step is to set up the channel, with the following organizations:
Later additional parties could be added to support the channel.
Each time CO2 emissions data is stored on the channel, it will have the following data:
A micro-service run by the auditor will:
A micro-service run by the customer will:
The emissions data are not tokens and not meant for transactions. The emissions data can be used to create a token which is suitable for transaction as part of the Emissions Tokens Network Project. For example, the emissions data from a full month or several months could be used to create a token. The token may require that the emissions data used covers enough of the time period, and that there are no overlaps of emissions data.
To prevent double counting, we will not allow emissions records for the same utility customer in overlapping date ranges on the channel.
1) Start by subscribing to the Climate SIG mailing list for updates and meeting notifications.
2) Join our bi-monthly Peer Programming Zoom call for developers on Mondays at 9 AM US Pacific time (UTC-07:00 America/Los Angeles.) Please check the calendar for the next call.
3) Check out the good first issues from our blockchain-carbon-accounting in Hyperledger-labs and feel free to contribute a fix for one that looks interesting to you.
4) See our How to Contribute page for other ways how you could get involved.