2024-02-13 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>

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

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

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

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 Annual Report

  • Community input needed: https://docs.google.com/document/d/1xI0ZJeVcQt5nu5SNdWJbzQDu19WkAnr3wnjEXouB2U0/edit#heading=h.6v4ntnevnxr8

    • Add Indy Besu to Goals section @Renata Toktar 

  • Annual Report should be presented and discussed at the TOC Meeting on Thurs, Feb 15: https://lists.hyperledger.org/g/toc/viewevent?repeatid=52670&eventid=2208914&calstart=2024-02-15

• Release 1.13.2 completed: https://github.com/hyperledger/indy-node/releases

• Indy Besu update and discussion

  • Status

    • Implemented on-ledger API for migrating entities from Indy to Indy-Besu 

    • Designing did:indybesu method

  • General issues:  

    • Credential Definition identifiers are not defined in Anoncreds specification

    • There are different libs (anoncreds-rs, indy-data-types) with different anoncreds entities format

• Any updates on upgrade or documentation contributions

• Ubuntu 22.04

  • Ubuntu 20.04 support ends in April 2025

  • What are pain points for the upgrade

    • Some dependencies aren't available in 20.04.

      • Unable to install some in 22.04

  • First step in the Indy 20.04 => 22.04 update would be to setup builds and tests running on 22.04 so we know what breaks.

• Cacti Project uses Indy

• Indy Besu Migration

  • https://github.com/hyperledger/indy-besu/tree/main/docs/migration

• 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

  • Create a new Indy repository and move the Indy Besu code there

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