Summary

Short meeting – 30 minutes this week (ACA-Pug meeting starts at 08:00 Pacific / 17:00 CET)
Update from the implementation team - status of work/wrapping up
Overview/demo of DID:Indy work
Open PRs and Issues

Recording from the call:

	Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct.

	Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct.

Update from the implementation team
- Implementation Plan: https://hackmd.io/@dbluhm/did-indy-impl
- PR ready for review! https://github.com/hyperledger/indy-node/pull/1740
- PR to Indy HIPE: https://github.com/hyperledger/indy-hipe/pull/163
  - Very similar to implementation plan
- Only things left: minor doc updates, any feedback on PRs
indy-node changes overview and demo
- Slides found here
Indy VDR Status - done...
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
Next Week:
- Governance of the Hyperledger `did-indy-networks` repo, and deployment
- Changes needed to CredX, indy-sdk/anoncreds and ACA-Py (and other frameworks) to use DID:Indy identifiers.