Summary

• Update on the Indy Ubuntu 20.04 Upgrade
• Root cause of the "mixed node" problem
• Moving the AnonCreds implementation out of Indy – to where?
• Q&A

Recording of Call: 

Welcome and Introductions

Attendees

Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>

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

Richard Esplin(Avast) <richard.esplin@avast.com>

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

Related Calls and Announcements

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 

• Progress on completing the Ubuntu upgrade.
• Update on the Indy Ubuntu 20.04 Upgrade
• Root cause of the "mixed node" problem: Indy Node issue 1769
• Moving the AnonCreds implementation out of Indy – to where?
  • We previously discussed moving AnonCreds to Aries as part of aries-credx.
  • Could also be a DIF project?
• Avast (soon Norton) won't be participating in Indy going forward, at least for 2022. We intend to still participate in Hyperledger Aries. Richard Esplinwon't be able to attend future meetings or follow the chat, but will try and respond to direct messages.

Upgrade Notes

• Update on CI/CD Update and Ubuntu Upgrade 
  • Indy Shared GHA Repo
  • Indy-Plenum: 
  • Indy-Node:
  • indy-test-automation:
  • indy-node-container:
    • Call time changed – 17:00 CET / 8:00 Pacific on Thursdays.
  • Indy-SDK build progress
  • Related work - Sovrin token-plugin repo being reworked to match indy-node/plenum.
    • Mostly done the code.
    • Working on the pipeline
    • Linting issues documented and being cleaned
      • https://github.com/sovrin-foundation/token-plugin/issues/413
• The root cause of the "Mixed Node" issue has been found – and it's not a mixed node issue.
  • Christian Bormann has been investigating and looks like he's figured it.
  • Join us to find out the details – it's pretty interesting...

Future Calls

• GDPR and the right to be forgotten – mitigations and approaches.
• Dealing with Indy Node DoS attacks.

• 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

Action items