2025-01-28 Indy Contributors Call

Summary

• Indy Annual Report
• Ubuntu-22.04 upgrade progress reports
• GitHub Organization discussion
• Updates
  
  • Indy Besu updates and discussion
  • DID Web VH
• Open Discussion

Zoom: https://zoom-lfx.platform.linuxfoundation.org/meeting/97572546272?password=5da46f0a-57dc-4de9-8831-708ba60d97ae

Recording: 

Welcome and Introductions

Attendees

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

Related Calls and Announcements

• Note the new Zoom link
  • Regenerate calendar invitation
  • https://zoom-lfx.platform.linuxfoundation.org/meetings/indy?view=week

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

• Indy Annual Report
  • Due Jan 30th
  • Template: https://github.com/tkuhrt/lfdt-governance/blob/20250116/tac/project-updates/0000-annual-review-template.md
    • Last Quarterly Report: https://github.com/LF-Decentralized-Trust/governance/blob/main/tac/project-updates/2024/2024-Q4-Hyperledger-Indy.md
    • Last Annual Report: https://github.com/hyperledger/toc/blob/gh-pages/project-reports/2024/2024-annual-Hyperledger-Indy.md
  • Draft: https://hackmd.io/NY6T19p2Tni4Mq-LxsRjwg
• Coordinating Ubuntu-22.04 release
  • Branches
    • Use main for indy test automation
    • Use ubuntu-22.04 for node and plenum
  • Moving back to Discord from Plenum
• GitHub Organization
  • Potential requirement to move repos from Hyperledger to Hyperledger-Indy
  • Impacts links, docs, GHA
  • Little value from branding perspective
• Updates
  
  • Indy Besu updates and discussion
    • Article: https://www.lfdecentralizedtrust.org/blog/lf-decentralized-trusts-hyperledger-indy-on-besu-joins-the-didindy-method-six-months-of-progress
    • Indy on Besu in-person event in Lisbon
    • Revocation - finalized technical review, processing review comments. Will be merged soon
    • IaC - PR in review, DSR used for a cloud deployment
  • DID Web VH
    • v0.5 is finalized
    • Working on AnonCreds method update
    • DID Web VH server to receive and post those files
      • Updates to ACA-Py and Credo
• Open Discussion

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