Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Let's take a look at a very specific use case: a permissioned Hyperledger Fabric channel where a utility shares an auditor calcualtes the emissions of a customer's electricity bill with its customersbased on its utility bill.  The same pattern could be repeated for other data services (travel, commute, shipping, etc.)

...

  • Utility – utility which generates electricity and provides CO2 emissions data energy use data
  • Auditor – trusted third-party which calculates CO2 emissions from utility energy use and published data sources 
  • Customers – customers of the utility who used electricity and need to get their CO2 emissions data
  • Channel Operator – a third party which operates the channel, including maintaining the Orderer and Anchor Peer and allowing new organizations into the channel.  In real life this Channel Operator would probably operate on behalf of the utilities and the customers who use it, under the supervision of a governance entity. 
  • Peer Node Operator – third parties whose only role is to operate a Peer Node.  In real life these may be independent "validators" who earn a small fee for maintaining the data on the channel.  

...

  • 1 Orderer run by Channel Operator
  • 1 Anchor Peer run by Channel Operator 
  • 3 Peers run by 1 Peer Node Operator, 1 UtilityAuditor, and 1 Channel Operator
  • MSP for Utility Auditor and each Customer.  The utility 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.

...

A micro-service run by the utility or a service provider for the utility auditor will:

  • Get the utility bill for each customer
  • Convert the kWH of electricity used to CO2 emissions based on the Emissions & Generation Resource Integrated Database (eGRID) database.  This database should be stored in an immutable, publicly available database such as OrbitDB
  • Present its security key to the channel
  • Write the CO2 emissions for each customer to the channel as private data for each customer

...