Summary

• Recap of IIW Discussion
• Collaboration Tools
• About the <network> element of the DID

Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct.

If the call is recorded, the recording will be here: <TO BE ADDED>

Welcome and Introductions

Announcements

• Status of relevant, unresolved issues in the DID Core Spec
  • A `type` attribute

Discussion

• Recap of discussion at IIW
• Collaboration Tools:
  • indy-did-method on RocketChat - https://chat.hyperledger.org/channel/indy-did-method
  • indy-did-method repo
    • ReSpec vs. SpecUp
• About the <network> element of the DID
  • First 5 characters of a hash – of what?
    • Genesis File
      • What Genesis File?  Domain (does not change - first n transactions on the ledger), Pool (does change - inevitable as it contains IP:port of nodes)
        • Proposal: Use the Pool Genesis File hash
        • Pool file is required to contact nodes of the network.
        • If Domain, what to do if there is a fork?
          • Proposal: Domain Genesis file contains the first n records after the fork, as the sequence number is the same
  • Should an "alias" be allowed as TrustBloc uses?
    • From Troy Ronda: A quick update on our did:trustbloc handling of multiple networks. With the ability to specify a canonical DID in the DID document, we are adding the ability to have both discoverable domains in the DID - e.g., did:trustbloc:domain:suffix and also to have a stable consortium genesis identifier - e.g., did:trustbloc:<consortium genesis hash>:suffix. The canonical DID would become the <consortium genesis hash> version such that the resolution of discoverable domain DIDs would point to this canonical DID in the resolution result.
    • TrustBloc alias example:

      • did:trustbloc:testnet.trustbloc.dev:s3did12345

      • https://testnet.trustbloc.dev/.well-known/did-trustbloc/org1.sandbox.trustbloc.dev.json
        • Configuration file – equivalent to the Indy Pool Genesis File
    • So Indy might use: 
      • <domain> alias is :example.com, https://example.com/.well_known/did-indy/ ??
        • Perhaps a folder with current ledger pool genesis file (to find the ledger) and ledger domain genesis file (to find/check the hash)
  • If the DID to be resolved is NOT using an alias, how is the Pool Genesis File found?
    • Known by all that need to know it?
    • Registry? GitHub?