Summary

Recording from the call: 

Welcome and Introductions

Announcements

Attendees

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

• Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>

• @Lynn Gray Bendixsen (Indicio PBC) <lynn@indicio.tech>

• @Wade Barnes (Neoteric Technologies Inc.) <wade@neoterictech.ca>

• @Char Howland (Indicio PBC) <char@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

  • This week:

    • ATTRIB txn resolve state by seqNo or timestamp

    • Finish off HIPE, doc updates

    • Polishing up

• Indy VDR updates

  • Indy VDR Proxy server with multi-ledger and DID Resolution support: PR https://github.com/hyperledger/indy-vdr/pull/86

    • Static network configuration by did indy networks repo or local folder structure

  • Indy VDR Python Wrapper with general DID Resolver. PR: https://github.com/hyperledger/indy-vdr/pull/87

    • Example of static and dynamic network configuration. Dynamic tries to fetch genesis txn from did indy networks repo when new DID namespace is encountered. 

    • Resolver used in wrappers can't fetch ATTRIB txn if no diddocContent is present. Wrapper code has to take care of that.

  • DID:Indy Universal Resolver Driver based on new Indy VDR: https://github.com/IDunion/indy-did-resolver/tree/did-indy-vdr

  • DID generation in indy vdr tests via indy-utils (part of indy-shared-rs). PR to enable generation of did:indy self-certified DIDs: https://github.com/hyperledger/indy-shared-rs/pull/13

• 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.

Future Discussions: