Page Comparison

Summary

Recording of Call:

...

2023-03-14 Indy Contributors Call Recording

Welcome and Introductions

...

Release Status and Work Updates

• Indy Node/plenum
  • Issue with rocksdb dependencies https://github.com/hyperledger/indy-plenum/issues/1632
  • Needs Rework of Buildimage and Pipeline
    • https://github.com/hyperledger/indy-plenum/issues/1634
    • https://github.com/hyperledger/indy-node/issues/1799
• Indy-test-automationreworked pipeline with fewer inputs needed from sovrin working. Just need some minor cleanup and merging after https://github.com/hyperledger/indy-plenum/issues/1632 is solved.
• Indy-Node test-automation integration next step after cleaning up the dependencies issues and getting the sovrin-test-automation finished.
• Indy SDK
• 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)
• Ursa
• Indy DID Method – https://hyperledger.github.io/indy-did-method/
• AnonCreds Specification: https://anoncreds-wg.github.io/anoncreds-spec/

Meeting Topics 

• Sovrin Node build
  • Rocksdb circular dependency issue has been resolved
  • Working on reducing number of variables needed for Indy test automation
    • Packages specify their dependencies, don't need to install dependencies separately
• Transition of indy-node from RC to final
• Discussion: Running an Indy network
  • Indy scan
    •  https://indyscan.io/
    • https://indyscan.indiciotech.io/home/INDICIO_TESTNET
    • https://candyscan.idlab.org/txs/CANDY_PROD/domain?page=1&pageSize=50
    • https://github.com/Patrik-Stas/indyscan
  • Indy Node Monitor
    • https://github.com/hyperledger/indy-node-monitor
  • Indy CLI
    • https://github.com/hyperledger/indy-cli-rs
    • https://github.com/bcgov/von-network/blob/main/docs/Indy-CLI.md
• Other Topics

Future Calls

• Indy Roadmap
• 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...

...