Versions Compared

Old Version 2

changes.mady.by.user Dan Gisolfi

Saved on

compared with

New Version Current

changes.mady.by.user Stephen Curran

Saved on

Key

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

Summary

Excerpt
  • Revisiting/Finalizing points from last two meetings (state proofs, agreement keys, DIDDoc content)
  • Resolving ledger objects as DIDs?

Recording from the call:

...

 20210223 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

...

Collaboration Channels

...

This Week's Discussion:

  • From last week's discussion – confirmation of approach:
    • 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.
      • With support for the version_id and version_time resolution parameters.
    • Other options rejected
      • Do nothing
      • Single call with both state proofs and ledger does assembly
      • Write DIDDoc on ledger writes and have state proof for DIDDoc
      • Add WRITE_DIDDOC transaction 
  • Decision on assembly points of concern:
    • The "nymKeyAgreement" flag
    • 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 (e.g. schema, etc):

...