Summary
| Excerpt |
|---|
|
Recording of Call:
...
Indy Contributors Call Recording
|
Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct. |
|---|
Welcome and Introductions
...
- Char Howland (Indicio, PBC) <char@indicio.tech>
- Philipp Schlarb (esatus AG) <p.schlarb@esatus.com>
- Wade Barnes (BC Gov / Neoteric Technologies Inc.) <wade@neoterictech.ca>
- Lynn Gray Bendixsen (Indicio, PBC) <lynn@indicio.tech>
- Kim Ebert (Indicio, PBC) <kim@indicio.tech>
- Christian Bormann (Robert Bosch GmbH) <christiancarl.bormann@de.bosch.com>
- Samuel Rinnetmäki (Findy Cooperative) <samuel.rinnetmaki@findy.fi>
- Alexandra Walker (Indicio, PBC) <alex.walker@indicio.tech>
Related Calls and Announcements
- IIW: April 18-20
Release Status and Work Updates
...
- Sovrin Node build
- Transition of indy-node from RC to final
- Value of Indy
- Results of Findynet's SSI tech stack survey: Samuel Rinnetmäki
- Preliminary results overview (PDF), actual results will be published on Findynet's web site later (this week?)
- Indy Roadmap Discussion follow-ups: https://hackmd.io/GeRP00i0Sj-7z4zXn2MB5g?view
Ubuntu-20.04 upgrade
Clean up issues and PRs on Indy repos
Tombstoning
Generalize how to anchor documents to the ledger
Overlay Capture Architecture (OCA)
Indy Node Monitor for stewards
Read replicas
Firewalls in Indy
- DIDComm protocol to read from an Indy networkScoping out top priority tasks
- 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...
...