...
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.)
Players
Imagine a network with multiple utilities, emissions auditors, and customers:
- Utility – utility which generates electricity and provides energy use data. The Utility is not part of the blockchain or channel. It provides data with the same authentication process, such as Green Button, as it already does.
- Auditors – trusted third-parties who calculate CO2 emissions from utility energy use and published data sources (see below.) The auditor is like an engineering company and uses specialized software to calculate emissions from data such as utility bills. A group of independent auditors set up the blockchain and maintain it collectively.
- Customers – customers of the utility who used electricity and need to get their CO2 emissions data. Customers also do not have to have to have blockchain or channel infrastructure. It interacts through the Auditors.
- Orderer Operator - third party entity which operates the orderer. Since the same organization should not be both peer or orderer, a neutral orderer is needed.
...