Summary

  • Discuss participating in Hacktoberfest 2021
  • Plan development of full Scope 1/2/3 emissions calculator, potential applications, and ecosystem
  • Review with Pritam Singh - 
    • Deployment of Vault
    • Update documentation

Our plans for upcoming development:

  • Extend the emissions calculator to cover full Scope 1/2/3 emissions
  • Build an openly available emissions factors data set on OrbitDB.  It will initially be seeded with the US EPA, EU EIA, and UK emissions factors, then expanded over time.
  • Develop an ecosystem around it of commercial service providers, open source developers, and companies
  • Initially we'll work on
    • Cloud computing emissions calculator based on the one from ThoughtWorks
    • Mobile app for calculating travel emissions

These changes are now on github as issues with the label scope-3-emissions

Please leave your feedback as comments.

zoom_0.mp4


Time:


Dial-In Information:  [ZOOM]

You can join either from your computer or from your phone:


Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.



  • No labels

12 Comments

  1. Si Chen

    Harsh SharmaWhere did you put the link to the Hacktoberfest?  I don't see it.

  2. Harsh Sharma

    Si ChenIn order to participate in Hacktoberfest, we just need to include "Hacktoberfest" as a label in our repository's about section. I've already done that. Please take a look at https://hacktoberfest.digitalocean.com/ for more details.

  3. Si Chen

    Bertrand WILLIAMSRIOUX Pritam Singh

    Could you please show me what tests currently exist for vault and web socket security?

    Also, I think third party clients should interact with either vault or web socket security through a scheme similar to obtaining tokens with google or Facebook.  For example see this article:

    • client should take the user to an app page which requests the user to sign in to either vault or web socket login
    • once the user signs in, they should authorize the transaction 
    • then it should redirect back to the third party application with the token
    • the third party application should now be able to use the token to perform operations

    this means that the authentication (/im/) operations should not be callable directly from the third party application.  Rather they should be part of a special authorization app.

    What do you think of this?

    1. Pritam Singh

      1. Si Chen

        Pritam Singh Bertrand WILLIAMSRIOUX

        I think the authentication should be part of our repository so that client apps have a standard way to work with our authentication models, just like Facebook and Google offer standard authentication and redirects.

        How about something like this:

        • Client app has a button to "Authorize"
        • This takes to a page from our app which asks for credentials (ie not the client app)
        • It redirects back to the client app with a token
        • Client app uses the token for subsequent requests

        Related to this, should this authentication feature be in the secure-identities directory Bertrand created?

        Should Vault also be in the secure-identities directory, since it could be one of several ways to sign Fabric transactions?

      2. Si Chen

        Pritam SinghHow are the blockchain gateway tests run?  Can they be added to be part of the Github CI pipeline?

  4. Pritam Singh

    yes, idea of putting vault identity authentication inside the secure-identities folder is nice. I can create a folder named `vault-identity` inside that folder, this folder will have the logic for management of vault identity.

    1. Si Chen

      Great.  Please do that.

      Also should I create a task to work on the authentication process?  Does what I described sound right?

      1. Pritam Singh

        Yes, it does,

        I had already implemented the logic for vault identity management, but it was inside the `typescript_app`. Now what I will do is move from their to the new sub folder.

        You can find the logic and swagger docs in fork under `identity` branch : https://github.com/Zzocker/blockchain-carbon-accounting/blob/identity/utility-emissions-channel/typescript_app/swagger.v2.json .

        also please create a issue for this, will merge by this weekend.

        1. Si Chen

          Ok please take a look at the issues I created and let me know what you think.

  5. Harsh Sharma

    Si ChenWe can also take a look at the FLINT project, which is an open source project by Moja Global (also under The Linux Foundation) that deals with GHG emissions and carbon accounting. In fact, it's already in use in a lot of countries. We could possibly discuss extending their platform with blockchain and decentralization, or maybe even have a meeting with their community members.

    1. Si Chen

      Yes, I know about FLINT--They'll be presenting in our SIG meeting on November 2!