2024-12-17 Indy Contributors Call

Summary

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

Recording:

Welcome and Introductions

Attendees

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

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

• @Renata Toktar  (DSR Corporation) <renata.toktar@dsr-corporation.com>

Related Calls and Announcements

• Sovrin Foundation is preparing for the likely ending of operations of its MainNet ledger on March 31, 2025

Release Status and Work Updates

• Indy Node/plenum – PR needed to replace Ursa with the indy-blssignatures-rs implementation. Issue #

• Indy-Besu - https://github.com/hyperledger/indy-besu

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

  • Small update to Indy VDR to update the dynamic network discovery URL; needs to be published

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

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

Meeting Topics

• Coordinating Ubuntu-22.04 release

  • https://github.com/hyperledger/indy-node/pull/1870

  • Kim did Indy Plenum updates, Wade fixed the pipelines, next step was Indy Node release

  • Kim integrated the updated release for plenum + other pipeline changes

  • Next step is to fix the pipelines again

    • Do a pass, get it up and running

    • Determine next steps from there

  • Indy test automation is integrated into the pipeline

    • To Do: Update containers that the tests are being run on

    • Currently uses whatever package the Indy build uses

  • Create tickets for work items

  • Fix issues on the ubuntu-22.04 branch, then merge to main

  • Tools for coordination/regular updates

    • Tatsu: based on Slack https://tatsu.io/

    • Stephen will invite folks to Tatsu

  • To Do: define initial tasks on Jan 14th call, then assign

    • First thing: Enable the 22.04 branch in the workflows (only enabled on main currently)

    • Change FROM line on Dockerfiles to ubuntu-22.04 (including indy automation, needs a ubuntu-22.04 branch too)

  • @Wade Barnes will write issues

• Updates

  • Indy Besu updates and discussion

    • Deploy with Kubernetes and AWS

    • Finish before the end of the year

    • Try Indy Besu not only locally, but deployed

      • Test migration from existing indy network to Besu

  • DID Web VH

    • 0.5 almost ready

      • Updates on pre-rotation and witnesses

      • Will evolve into 1.0

    • Name change 

    • Resolver into Credo

    • Resolver and registrar into ACA-Py

    • Deployed did:webvh server, hosting dids there (still tdw or web)

    • Talking to Bluesky

    • Most controversial: portability

      • Not helpful for Bluesky

• Open Discussion

Next Meeting

• Presentation on Indy Read Replica Project from Hyperledger Mentorship Program mentee Bryan Elee

Future Calls

• 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

• Indy-Besu

  • Continue discussion about open questions https://github.com/hyperledger/indy-node/issues/1826#issuecomment-1868609236