...
- 1 Orderer run by Channel Operator
- 1 Anchor Peer run by Channel Operator
- 3 Peers run by 1 Peer Node Operator, 1 Auditor, and 1 Channel Operator
- MSP for Auditor and each Customer. The auditor is given permission to write data to the channel. The customers are given permission to read data from the channel. Their MSP's are able to register certificates for their users.
The Workflow
Customer contacts Auditor to request that its CO2 emissions from its Utility bill be calculated.
Auditor sends an authorization request for data access from the Utility to the Customer. This could be an emailed link or a paper document.
Customer grants the authorization request, by clicking on agree or sending back the paper document.
Utility grants Auditor access to Customer's bill data.
Auditor downloads Customer bill data from Utility, applies the emissions factors from a published database like the Emissions & Generation Resource Integrated Database (eGRID).
Auditor publishes the Customer's CO2 emissions on the channel.
Later, the CO2 emissions can be accessed by
- Customer
- Customer's customers (down the supply chain)
- Regulators
- Investors
Data Stored on Channel
Each time CO2 emissions data is stored on the channel, it will have the following data:
...