2024-03-26 Indy Contributors Call

Summary

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

Recording: Call Recording

Welcome and Introductions

Attendees

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

• @Sylvain Martel (Gouv Qc) <sylvain.martel10@mcn.gouv.qc.ca>

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

• @Kim Ebert (Indicio, PBC) <kim@indicio.tech>

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

Related Calls and Announcements

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)

• Ursa

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

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

Meeting Topics

• Indy Besu updates and discussion

  • https://github.com/hyperledger/indy-did-method/pull/86 - sent a draft PR

  • https://github.com/hyperledger/indy-besu/pull/38 - updated error handling

• Ubuntu 22.04 upgrade

  • Indy-plenum work in progress

  • Work is being done here https://github.com/reflectivedevelopment/indy-plenum/tree/feature/ubuntu22.04

  • Most packages are being built via wheel2deb

  • Some packages are still being built with fpm, as not all compatible with wheel2deb

  • A package conflicts with base debian package, need to investigate further. bump_version script behaving differently, may need to build and install dependencies first

• Next Indy Summit

  • April 9

  • Topic: ledger redaction (tombstoning- marking txns as nonresolvable)

  • Register: https://zoom.us/meeting/register/tJMqdumsrDIvHt2Y-I3IHNpWeLUTyHnwYT3h#/registration

  • Meeting page

• Mentorship project submissions

  • TOC review until the 29th

• Any updates on upgrade or documentation contributions

• 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