Page History

...

• Recap of discussion at IIW
• Collaboration Tools:
  • Current hackmd document 
  • 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 – did:indy:<network>:<id>

  • What is the goal of the structure of the network?
    • Hash (543F4) – unrecognizable, verifiable with the ledger, short, non-discoverable/requires a registry
    • Domain Name (example.com) – recognizable, discoverable, not tied to the ledger, dependent on DNS
    • Arbitrary Name (SovrinStaging) - recognizable, non-discoverable/requires a registry, not tied to the ledger
    • Combination of hash and domain name (this is what TrustBloc does) 

    • Combination of arbitrary name and hash <arbname>:<hash>  e.g. did:indy:sovrin:<hash>:<id>

  Approach	Discoverability	Decentralized Control	(Limited) Verifiability	Human Friendly	Conciseness	Dependencies
  Hash of Domain Genesis File	No	Yes	Yes	No	Yes	Registry or Config
  Domain Name	Yes	Yes	No	Yes	No	DNS
  Arbitrary Name	No	Yes	No	Yes	No	Registry or Config
  Hash and Domain Name Alias, as in TrustBloc	Yes and No	Yes	Yes	Yes and No	Yes and No	DNS and Config
  Arbitrary Name + Hash	No	Yes	Yes	Yes	No	Registry or Config

  
  

  • • What is the easiest way for agents to use this?
      • DNS is a hard sell per Dan Gisolfi
      • A registry implies centralization - e.g. GitHub, DIF, ToIP
      • Today it will be just a manual list of name - config files
      • Does readability matter?   Who sees a DID?
        • Should be no one.  "If anyone sees a DID, we've failed at our job" - quote from RWoT

...