2020-08-04 Indy Contributors Call
Summary
Planned:
Plans for next Indy Node release
Contributions needed on Indy Node
Preparations/pre-work for the Indy Interop-athon
The call recording is available here: 20200804 Indy Contributors Call
Remember the Hyperledger Code of Conduct
Anti-Trust Policy
Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.
Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.
Introductions
Attendees
@name (Employer) <email>
Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
Related Calls and Announcements
Identity Implementer Working Group call (Wiki Page) - every 2nd Thursday
Join Us: Indy Interop-athon Virtual Conference - Sept. 1, 2 - Indy Interop-a-thon - Making "Network of Networks" Real
Release Status and Work Updates
Indy Node
Timing TBD:
Indy SDK
Significant changes in LibVCX
Team at ABSA is considering a different architecture
https://github.com/AbsaOSS/libvcx/commits/masterRelease Timing TBD
Indy Monitoring - https://github.com/bcgov/indy-node-monitor
Improvements to the JSON output
Anonymous mode (no node_monitor DID needed)
Error/Warning Summary section added
Not accessible (either mode)
Unreachable Nodes warning
Freshness check
Remove docker info from output - pure JSON from ./run.sh script
Indy/Aries Shared Libraries
Aries Shared:
indy-vdr (Andrew Whitehead) https://github.com/hyperledger/indy-vdr
indy-credx - https://github.com/andrewwhitehead/indy-credx
indy-shared-rs - https://github.com/bcgov/indy-shared-rs
aries-credx
Aries Secure Storage initiatives:
Working on some low-level rust crates necessary for supporting Storage
Ursa
BBS+, Revocation work 2.0 work
Current Release: 0.3.4 is ready.
Meeting Topics
@Richard Esplin Who is going to lead releasing Indy Node? We have a backlog of fixes that need to go out.
Especially: https://github.com/hyperledger/indy-node/security/advisories/GHSA-wh2w-39f4-rpv2 (needed by end of August)
https://github.com/hyperledger/indy-node/pull/1604
@Richard Esplin Other "easy" Indy Node contributions needed
Sovrin Jenkins isn’t public due previous security problems, need to move to GitHub Actions
https://github.com/hyperledger/indy-node/pull/1605/Ledger bugs
ledger crash if more than F nodes are out-of-consensus:
https://github.com/hyperledger/indy-plenum/issues/1488new node can take other nodes out of consensus:
https://sovrin.atlassian.net/browse/SN-18
PRs that need small fixes to be accepted.
https://github.com/hyperledger/indy-node/pull/865
https://github.com/hyperledger/indy-node/pull/948
https://github.com/hyperledger/indy-node/pull/1409Update to Ubuntu 20.04
https://jira.hyperledger.org/browse/INDY-2186
https://github.com/hyperledger/indy-node/pull/1443
https://github.com/hyperledger/indy-plenum/pull/1332
Preparation for the initial topics at the Indy Interop-athon - Indy Interop-athon - Making "Network of Networks" Real
Current support for Fully Qualified DIDs in Indy SDK: https://github.com/hyperledger/indy-sdk/blob/master/CHANGELOG.md#1120---2019-10-08
Future Calls
Next call:
Future: