Summary
- Update from DID F2F last week – resolutions?
- Continued: 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.
Welcome and Introductions
Announcements
Collaboration Channels
Discussion
- Eliminated the hash and DNS-based alias because of the complexity in using the two names for the identifier in signing scenarios, and the use of DNS.
- Eliminated the hash only approach because of the lack of benefit of doing the hash vs. the downsides
- The verifiability in using the hash is lost by using just 5 characters, but using a sufficient number makes the identifier too long
- Micha generated a new Sovrin genesis file with a matching hash by varying only the alias name of one of the nodes in 30 minutes
- Since we assume there will be in the low thousands of networks at the outside, the decentralization inherent in using the hash is not crucial
- Eliminated the hash + arbitrary name because the hash is not providing additional value.
- Leaving "Arbitrary Name" as the selected solution.
- Next questions:
- Third level names for subsidiary ledgers – e.g. Sovrin Staging and Sovrin Builder net?
- How to find the nodes of the network once the ledger is known? Config files, registries, gossiped names, etc.