Attendees (18)
@Maria Teresa Nieto
@Bobbi Muscara
@kamlesh Nagware
@Debbi Bucci
@Jorge Ordovas
@Kamlesh@Snapper
@Mike McCoy
Meeting on the zoom channel is https://zoom.us/my/hyperledger.community
Antitrust Policy and introductions
Main Event : Presentation on TrustID by Maria Teresa Nieto Galan. Blockchain Specialist at Telefónica.
Abstract: TrustID was created to decentralize the Hyperledger Fabric identity for the product implemented in Telefonica, TrustOS. TrustID is now an independent project. TrustID eases the management of identities for the case of TrustOS. Users shouldn’t need to hold a different set of credentials for each network or decentralized application they interact with. The same credentials used to access your own Bitcoins and manage your tokens in Ethereum should let you update the state of a Fabric asset or launch a secondary market in TrustOS. This is the rationale behind TrustID. The main goal of TrustID as a new project released in the Hyperledger Labs, under open source license, is to develop a new identity management standard in different blockchain platforms, regardless of the underlying technology.
- Ideas for Future talks (please add suggestions with contact)
- EBSI and eIDAS, and integration into the open platform. More on this topic.
Discussions on Identity as seen by the state vs across regions and internationally and how that helps stitch together the blockchain infrastructures, in terms of trust, KYC etc.. Refer to FATF.
- Further on TOIP
- NIST 800-63: https://pages.nist.gov/800-63-3/sp800-63-3.html Call For Comment https://csrc.nist.gov/publications/detail/sp/800-63/4/draft
- ID2020: Why is it important? Financial and societal inclusion through Digital Identity and SDGs.
Recordings
Chat:
Jim Mason : are these docs current for the current release ?? https://trustos.readthedocs.io/en/latest/id.html
Jorge Ordovas : This docs are related to Telefonica’s TrustOS API, but not related to TrustID (the documentation is in the GitHub repository Maria Teresa is presenting, on Hyperledger Labs)
Jorge Ordovas : https://github.com/hyperledger-labs/TrustID
Rouven Heck : The interOp Charter: https://docs.google.com/document/d/1a01GQVtZB7tDVcm9avS8zuYPHQzEEDtTOEh4Bqu-8Bs/edit
Rouven Heck : https://identity.foundation/interop/
Rouven Heck : https://github.com/decentralized-identity/interoperability
Rouven Heck : this working group meets weekly ^^
Rouven Heck : recently kicked off, so all pretty new
Jim Mason : Thanks @rouven — looks good. Aries already has done some work with OIDC for authentication to legacy systems as well
Rouven Heck : There was recently a workshop with OIDC to discuss/represent DID Auth SIOP, there is close collaboration happening: https://identity.foundation/working-groups/authentication.html
Rouven Heck : DIF has people from the Aries community part of it. Might be the same effort
Rouven Heck : similar with DIDComm - close collaboration across ecosystems
Minutes
Summary:
What do we need?
- Decentralized Authentication
- To give users the possibility to custody their keys
- Keys interoperable with other platforms or methods
- To give different access to chaincodes in the same Hyperledger Fabric channel
- To use DID standard
Demo:
Code walk-thru (see video).
- Identity and Chaincode internals. Init, invoke, verification, and create identity services.
- Create an identity and publish in Fabric chaincode
- Interact with chaincode using DID and JOSE (json for encryption)
Questions:
Q. How does the project integrate with the core Telefonica business?
A. Briefly, many clients want to create business consortiums and provide the ability for self-identity
Q. Similar to Hyperledger Aires?
A. Thank you, cooperation collaboration is possible.
Q. Interoperability of different DID/DIF ecosystems ...
A. Discussion
Q. What are the main challenges for integrating/interoperating different types of signatures?
A. Each blockchain platform has a different algorithm to create keys: The main idea, everything is verified in chaincode or smart contracts, we only need to verify.
Q. Sharded keys / multiple keys?
A. We didn't have time for this requirement (so far).