Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary

Excerpt
  • Can we do the GET_DIDDOC transaction?
  • ATTRIB DIDDoc raw data format
  • How to represent Indy Ledger Objects as DIDs?

Recording from the call: 20210216 Indy DID Method Specification Call Recording

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

...

  • Sergey Khoroshavin on Indy state proofs and the ramifications of a GET_DIDDoc transaction.
  • Options for getting a DIDDoc, which are a trade-off of integrity and effort to implement
    1. Do (almost) nothing.  Client must get NYM, ATTRIB and assemble the DIDDoc.
      1. Lack of certainty that the client gets a consistent version.
    2. Have a single call that gets the NYM and ATTRIB and state proofs for both with same multi-signed merkle root, and leave the assembly to the client.
    3. Same as previous but have the ledger return the assembled document.
      1. To verify the state proofs, must still include the NYM and ATTRIB
    4. Have NYM and ATTRIB transactions write the DIDDoc to state and return that
      1. V1 txns work the same
      2. V2 txns work this new way
    5. Update NYM transaction to allow for an ATTRIB provided at the same time.
      1. Looks like 4, but they are processed in a single call to the ledger
    6. Create a new transaction WRITE_DIDDOC and put the object to the ledger
      1. What's the impact on the NYM object?
    7. For all:
      • How might a query that requests a "version_id=" and "version_time=" work?
      • version_time is doable, version_id is less clear, as we have two ids
      • Risk is losing time database
  • Any thoughts on the "nymKeyAgreement" discussion?
  • Is it important to remove the "content" item and just inline the rest of the ATTRIB?
  • What error checking should be done on the ATTRIB.  See proposal in the hackmd document (valid JSON, no NYM fields, valid DIDDoc)
  • Other Indy Ledger Objects as DIDs (schema):
    • Process
    • Existing transactions
    • Putting the Ledger Objects on other ledgers using extensions

...

  • This meeting: Discussion on nymKeyAgreement
  • Drummonds proposal: https://docs.google.com/document/d/1f99z4Bf8F-DA8EbkNjInVQv2ncJGPwF_Dp7I7Mfyhqs/edit
  • What format for other objects on the ledger as DIDDocs.
  • What format for existing objects on the ledger as DIDDocs?
  • DNR and DND discussions
  • Structure for Indy specific objects returned as DIDs
    • What is the DID?
    • What is the DIDDoc format?
    • Existing objects – backwards compatibility
      • DID vs. DID URL – how could that be done?

...