Summary

• Update from the implementation team
• Status of work – wrapping up
• Use of did:indy identifiers/URLs in objects shared across participants
• Open PRs and Issues

Recording from the call: TO BE ADDED

Welcome and Introductions

Announcements

Attendees

• Daniel Bluhm (Indicio PBC) <daniel@indicio.tech>

Collaboration Channels

•  indy-did-method on Discord - https://discordapp.com/channels/905194001349627914/941708981825576960
  • Invitation: https://discord.gg/hyperledger
• indy-did-method repo using SpecUp
• Published specification: https://hyperledger.github.io/indy-did-method

Online Discussion (from Discord this week)

This Week's Discussion:

• Update from the implementation team
  • Implementation Plan: https://hackmd.io/@dbluhm/did-indy-impl
  • feature/self-cert merged into main feature branch
    • Investigation into TXN_PAYLOAD_VERSION: https://github.com/hyperledger/indy-did-method/issues/63
  • Draft PR opened: https://github.com/hyperledger/indy-node/pull/1740
    • Tests passing 
  • Working on HIPE and Doc updates
  • Upcoming
    • ATTRIB txn resolve state by seqNo or timestamp
• PR review and finalization.
• Question: Will we be able to put `did:indy` references into objects shared amongst participants and they "just work"
  • For example, in a proof request, can I put into the restricts `"cred_def_id" : "did:indy:123...345:...."` and it will work with Indy VDR?
  • Presumably not – what has to change to enable that?
• GitHub PRs for review
  • Self-certification validation selection update 
  • (Draft) Resolvable JSON-LD DID Doc Examples  - Moved to Sam Curren for further review and research.
• GitHub Issues for review
  • Indy object naming conventions permit whitespace and other characters that impact formatting as a URL
• Discussions:

Future Discussions: