Join our Peer Programming Call-In
We have a bi-weekly Peer Programming Zoom call for developers on Mondays at 9 AM US Pacific time (UTC-07:00 America/Los Angeles.)
We're currently implementing the Utility Emissions Channel use case together.
If you're interested, please check the calendar for the next call.
Introduction
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.)
...
- Present its seurity key to the channel
- Get its CO2 emissions from the channel's private data
Emissions Data are Not Tokens
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. 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.
An offline analogy would be engineering reports signed by a building engineer. You can keep bringing plans to your engineer, and he can review each one and sign off on it. But ultimately, only one set of plans will be used to build a building.