Zoom Link: https://zoom.us/j/99220079317?pwd=OHk0U05ITnBkSmZ0aXlIQzFDYWg3UT09
Summary
- Update on the "mixed node" problem
- Update on Sovrin Node pipeline
- The Indy "Corporate Firewall Problem" and the idea of a Proxy Server on Nodes?
- Q&A
Recording of Call:
|
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
Attendees
Wade Barnes (Neoteric Technologies Inc.) <wade@neoterictech.ca>
Related Calls and Announcements
- DIF Interop WG is conducting a survey: https://forms.gle/aLxj8MK2TuViyMav5
- Help shape the topics of future WG meetings!
Release Status and Work Updates
- Indy Node
- 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
- Root cause and solution to the "mixed node" problem: Indy Node issue 1769
- Another issue found by Christian Bormann
- Audit ledger is supposed to create an entry every 5 minutes, but is actually creating 3 every 5 minutes (one per ledger instead of one across ledgers).
- Sovrin Node build
- indy-vdr – how do we get that released?
- 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 443 for HTTP/S requests and arrange to have them processed?
- Other Topics
Future Calls
- GDPR and the right to be forgotten – mitigations and approaches.
- Status of Indy-SDK
- Statement on the future of the Indy SDK: PR 2329
- Plans for future of Indy CLI (move to Indy VDR?)
- Indy SDK in test for Indy Node (move to Indy VDR?)
- Status of GitHub Actions for the Indy-SDK
- Indy bugs
- Using GitHub tags "Good First Issue" and "Help Wanted"
- Node 1490: problems with large catch-up
- Plenum 1506: view change message consensus calculation error