...
- Recap of discussion at IIW
- Collaboration Tools:
- indy-did-method on RocketChat - https://chat.hyperledger.org/channel/indy-did-method
- indy-did-method repo
- About the <network> element of the DID
- First 5 characters of a hash – of what?
- Genesis File – but what if it changes?Stored on the ledgerFile
- What Genesis File? Domain (does not change - first n transactions on the ledger), Pool (does change - inevitable as it contains IP:port of nodes)
- Pool file is required to contact nodes of the network.
- If Domain, what to do if there is a fork?
- Domain Genesis file contains the first n records after the fork, as the sequence number is the same
- What Genesis File? Domain (does not change - first n transactions on the ledger), Pool (does change - inevitable as it contains IP:port of nodes)
- Genesis File – but what if it changes?Stored on the ledgerFile
- 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: https://testnet.trustbloc.dev/.well-known/did-trustbloc/org1.sandbox.trustbloc.dev.json
- So Indy might use:
- <domain> alias is :example.com, https://example.com/.well_known/did-indy/ ??
- Perhaps a folder with a domain pool file (can produce hash), ledger pool file
- <domain> alias is :example.com, https://example.com/.well_known/did-indy/ ??
- 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?
- First 5 characters of a hash – of what?