2022-09-27 Indy Contributors Call

Summary

	Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct.

	Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct.

@Wade Barnes (Neoteric Technologies Inc.) <wade@neoterictech.ca>

@Lynn Gray Bendixsen (Indicio, PBC) <lynn@indicio.tech>

@Christian Bormann(Robert Bosch GmbH) <christiancarl.bormann@de.bosch.com>

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/

Root cause and solution to the "mixed node" problem: Indy Node issue 1769
Discussed https://github.com/hyperledger/indy-node/pull/1783
- @Christian Bormann would appreciate some extra eyes on the code. @Char Howland indicated she and possibly @Daniel Bluhm would take a look.
Need a way to test the network migration (16.04 to 20.04) on test networks affected by the ordering issue.
- Testing to include migration and then switching to sorted txn ordering.
- @Christian Bormann indicated he would look into creating a tool to write affected transactions to a network. This would allow testing on pure disposable indy-node networks.

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