2024-08-13 Indy Contributors Call

Summary

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

Recording:

Welcome and Introductions

Attendees

Kim Ebert <kim@indicio.tech>

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

Related Calls and Announcements

• Hyperledger Mentorship Project - acceptance complete

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)

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

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

Meeting Topics

• Indy Project Charter:

  • Stems from the recent "intent to form" announcement from the Linux Foundation and Hyperledger Foundation about LF Decentralized Trust.

  • Proposed Charter: https://docs.google.com/document/d/1rFPDlH5VYS9sVqcGRbWfOoxwhVTZQ7jaX9b8R6fhtsw/edit

  • Plan:

    • Create an "indy" repo, similar to this Aries repo.

    • Put into it a "TSC.md" file that lists the Indy TSC members (currently on the Indy Admin Team list) and processes – same as this TSC.md in Aries.

    • Put into it a "MAINTAINERS.md" that points to the Hyperledger "access-control.yaml" file and processes of Maintainers – same as this MAINTAINERS.md in Aries.

    • Put a "MAINTAINERS.md" (like this one) file in all Indy repos that points to the "access-control.yaml" file and to the indy repo MAINTAINERS.md

    • Update the charter to match roughly what is in the Aries Charter

• Ubuntu 22.04 upgrade

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

• Indy Besu updates and discussion

  • Revocation is in progress.  CPQD has implemented some code for revocation / API and design, based on revocation list.

    • https://github.com/hyperledger/indy-besu/pull/76

  • Hyperledger Meetup planned for the end of September – "Indy on Besu" – looking for contributors to lead the meetup re: Indy / Besu -- Both / Either.

• Updates

  • Indy Mentorship Project (Read Replicas)

• 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