Connecting NET to distributed Identity management services.

[brioux]

Eventually, I suggest adding to NET, and the blockchain-carbon-accounting project generally, distributed identity management services that can verify an organization's credentials (emissions auditor, offset issuer, producer ...) based on their registered public address. Hyperledger Aries can be leverged for such applications.

This can limit the role of NET servers in managing user information (and GDPR compliance). However, this requires using existing DLT based credential verification systems, of which not many exist. The team at Digital Mines in British Columbia has done good ground work on this, and are starting a pilot for natural gas producers.

In a recent call with Kyle Robinson, he differentiated their work as providing a vertical lens to asses the credentials (e.g., ESG) of an organization via DLT. This can intersect with the horizontal emissions/performance certificate tracking services we are implementing as transferrable tokens.

[sichen1234]

Yes, we should have a more formal identity management system. How does this compare to a KYC/AML system?

…

----- Si Chen Open Source Strategies, Inc. *Why open source and blockchain for carbon accounting? Video <https://www.youtube.com/watch?v=eNM7V8vQCg4> and Blog Post <https://www.opensourcestrategies.com/2022/06/01/why-open-source-carbon-accounting/>*

On Tue, Oct 25, 2022 at 3:35 PM Bertrand Rioux ***@***.***> wrote: Eventually, I suggest adding to NET, and the blockchain-carbon-accounting project generally, distributed identity management services that can verify an organization's credentials (emissions auditor, offset issuer, producer ...) based on their registered public address. Hyperledger Aries can be leverged for such applications. This can limit the role of NET servers in managing user information (and GDPR compliance). However, this requires using existing DLT based credential verification systems, of which not many exist. The team at Digital Mines in British Columbia has done good ground work on this, and are starting a pilot for natural gas producers. In a recent call with Kyle Robinson, he differentiated their work as providing a vertical lens to asses the credentials (e.g., ESG) of an organization via DLT. This can intersect with the horizontal emissions/performance certificate tracking services we are implementing as transferrable tokens. — Reply to this email directly, view it on GitHub <#640>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANAS4P3C7GX5X3BPGRLURLWFBODNANCNFSM6AAAAAARONFM3U> . You are receiving this because you are subscribed to this thread.Message ID: <hyperledger-labs/blockchain-carbon-accounting/repo-discussions/640@ github.com>

[sichen1234]

The current dApp allows the contract admin to update the name/organization/email information for a user.

This is not ideal long term. The contract admin is the admin of the smart contract, whereas the user information is stored in the database. A logical use case is for several dApps, each with their own dApp admin, interacting with the contracts. In those cases, it's the dApp admin who should maintain information about their users. For example, they would perform KYC/AML to onboard users to their dApp and then let those users interact with the blockchain contracts.

[brioux]

the modular framework of the NET app is well positioned to adapt to the different needs and requirements of different organizations. Providing centralized identity registry may serve some use cases - inline with how KYC-AML practices are organized by the majority.

I have encountered this a lot in the past 5 years of engaging with the crypto startup community, submitting identity documents to several platform - often hesitantly before a thorough research of the organization.

There is real innovation in KYC practices supported by web3.0. The government of Canada and major financial institutions are already using a DID platform https://verified.me/ ( i believe based on Hyperledger Indy) to verify credentials of individuals when accessing government services online (e.g, taxes) and private financial services. The idea is to avoid submitting proof of identity to multiple online service providers