Page tree
Skip to end of metadata
Go to start of metadata

Today we showed a basic UI connecting opentaps with the blockchain carbon accounting ledger through a REST api.  From a site in opentaps, we could use the utility bill data to record emissions on the ledger.  We could then see the emissions associated with the site.  Right now the UI is very basic, but we're working on implementing additional functionality for it to calculate real emissions and see a list of emissions records. We will also be implementing a registerAndEnrollUser function similar to the one in the Fabric asset transfer sample so that each user would have their own key to access the ledger.  This is based on option 1 from Robin Klemens's comments for the August 31 call.  I made a diagram showing how our current architecture is planned:

Conor Svensson then showed us the Epirus platform that his company has been developing.  It will create an open API for deploying tokens on an Ethereum chain.  He is preparing a big release in the next few days.  Using this platform, we will be able to integrate both permissioned fabric ledgers and public Ethereum channels.  

Martin Wainstein talked with us about how Renewable Energy Certificates (REC's) are created.  They are based on utility data and Independent System Operator (ISO) data and are created in a registry of the ISO, such as WREGIS.  They could be used for either flat or marginal (time of use) displacement of emissions.  For the latter there is a Watt Time database.

Long-term, we plan to put the pieces together like this:

  1. A group of people could get their utility, travel, and other data on permissioned data channels
  2. An auditor could get access to those channels and calculate the total emissions
  3. REC tokens could be integrated into the auditor's calculations to offset utility emissions
  4. Total emissions would be minted as tokens 
  5. The group would then contribute towards offsetting their emissions
  6. Based on their emissions and tokens, a DAO could set up a voting mechanism for them to vote on emissions offseting projects

We talked about integrating with Hyperledger Aries, which could be used to set up an automated or digital auditor that could verify claims in real time against data from IOT devices, utility meters, etc.  This could also be used to turn REC's into mitigation outcomes.

Since the next OpenClimate collabathon is in about a month, we should plan on some prompts to get more contributions and participation in this project.  Key questions are where we will be in early November, our overall vision of what to build, and what would need to be built next.


  • No labels


  1. I updated the REST API with `registerAdmin` and `registerAndEnrollUser` functionalities. Let me know if you have any questions and feel free to open issues in GitHub in case you run into errors. Have fun (smile)

    1. Thanks!  I was able to enroll the admin, enroll the user, and then record an emission.  The get emissions records, however, didn't work.  I posted it here:

      1. Thanks for reporting this. I closed the issue since the error occurred because the input data was of wrong format. See my comment at GitHub.

        1. Yes, it works.  Thank you!