2023-08-15 Indy Contributors Call

Summary

• Open Discussion

Zoom: https://zoom.us/j/93198495358?pwd=TS80VklHVElJS3lEcjUzQjV0VHVtUT09

Recording: 08152023 Recording

Welcome and Introductions

Attendees

• Char Howland (Indicio PBC) <char@indicio.tech>
• Wade Barnes (Neoteric Technologies Inc. / BC Gov) <wade@neoterictech.ca>
• Bruno Hivert (https://idlab.org)
• Lynn Gray Bendixsen  (Indicio PBC) <lynn@indicio.tech>

Related Calls and Announcements

• Second Hyperledger Indy Ecosystem Summit
  • 7 Sept, 6-8am Pacific/3-5pm Central Europe
  • Register

  • Here is the recording of the Hyperledger Indy Ecosystem June 2023 Summit.

  • The materials (documents, presentations) can be accessed here.

  • Need to take action on at least three fronts – technical, marketing, and regulations
• did:indy Indy VDR code is being merged into main

Release Status and Work Updates

• Indy Node/plenum
• Indy-test-automation
• Indy-Node test-automation integration next step after cleaning up the dependencies issues and getting the sovrin-test-automation finished.
• Indy SDK – to be deprecated
• 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, anoncreds-rs)
• Ursa
• Indy DID Method – https://hyperledger.github.io/indy-did-method/
• AnonCreds Specification: https://anoncreds-wg.github.io/anoncreds-spec/

Meeting Topics

• Open Discussion

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