2023-01-17 Indy Contributors Call

Summary

Recording of Call: 20230117-Indy-Contributors-Call-Recording

Welcome and Introductions

Attendees

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

• @Char Howland (Indicio, PBC) <char@indicio.tech>

• @Philipp Schlarb (esatus AG) <p.schlarb@esatus.com>

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

• @Sam Curren (Indicio) <sam@indicio.tech>

• @Christian Bormann (Robert Bosch GmbH) <christiancarl.bormann@de.bosch.com>

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

• @Alexander Sherbakov (DSR Corporation), <alexander.sherbakov@dsr-corporation.com>

• @Artem Ivanov (DSR Corporation), <artem.ivanov@dsr-corporation.com>

Related Calls and Announcements

Release Status and Work Updates

• Indy Node

• Indy SDK

• Indy Monitoring - https://github.com/hyperledger/indy-node-monitor

• Indy Node Container - https://github.com/hyperledger/indy-node-container

• Indy/Aries Shared Libraries - Hyperledger (indy-vdr, indy-shared-rs, aries-askar)

• Ursa

• Indy DID Method – https://hyperledger.github.io/indy-did-method/

• AnonCreds Specification: https://anoncreds-wg.github.io/anoncreds-spec/

Meeting Topics 

• Sovrin Node build

  • sovrin:

    • indy-test-automation integrated

    • publishing works- just some minor version fixes

  • libsovtoken: publishing- version updates needed

  • token-plugin:  publishing works

  • Dev releases publishing to Sovrin JFrog

  • RC and release workflows tested on branch and working

  • After the meeting – testing additional pipelines

  • Official RCs today or tomorrow!! 

  • Cleanup work after that milestone – dependency trigger up the chain.

  • Links to JFrog artifacts:

    • https://sovrin.jfrog.io/ui/repos/tree/General/deb/pool/focal/dev/s/sovtoken/sovtoken_1.2.0~dev1673970905_amd64.deb

    • https://sovrin.jfrog.io/ui/repos/tree/General/deb/pool/focal/dev/s/sovtokenfees/sovtokenfees_1.2.0~dev1673970905_amd64.deb

    • https://sovrin.jfrog.io/ui/repos/tree/General/deb/pool/focal/dev/s/sovrin/sovrin_1.1.217~dev1673888029_amd64.deb

    • https://sovrin.jfrog.io/ui/repos/tree/General/deb/pool/focal/dev/l/libsovtoken/libsovtoken_1.0.5_amd64.deb

• Demos – DSR / BC Gov Code With Us @Alexander Sherbakov:

  • First PoC of the new Indy CLI 

  • Migration of VON to indy-vdr

• Transition of indy-node from RC to final

  • Issue created: https://github.com/hyperledger/indy-node/issues/1791

• Other Topics

Future Calls

• Indy Roadmap

• GDPR and the right to be forgotten – mitigations and approaches.

• The Indy "Corporate Firewall Problem" and the idea of a Proxy Server on Nodes? @Kim Ebert

  • Core issue: A mobile wallet user using a Corporate WiFi may find that they can't get to an Indy ledger because all but 80/443 ports and HTTP/S protocols are blocked

  • Discussion/Options paper: https://hackmd.io/@n5FW6jwuRfCgchBDNWR3VQ/H1kNlKpmo

  • Question: Is it viable to have each Indy Node also listen on port 80/443 for HTTP/S requests and arrange to have them processed?

    • Option: Receive on HTTP(S) and send on to local ZMQ instance as if coming from outside.

  • Answer: We think it is probably not viable, as mobile agents require HTTPS. As such, each Steward would have to get a IP-based SSL Certificate. Technically doable, but getting everyone through that is really not practical. The cost of the certificates and maintaining them would be ugly.

    • Option: Add a DIDComm agent to every node, and use DIDComm to send the messages

    • Similar to using HTTP(S), but use a DIDComm message. Since Mobile Agents would be using a mediator, the DIDComm message would flow through that, and the HTTPS issue would not matter.  This is almost easy, but... There is no encryption public key in the genesis file, so that needs to be retrieved from somewhere else...

Action items