• Before this meeting: did:indy DID Method Meeting (one hour earlier)
  • Status of indy-node CI/CD and the Ubuntu upgrade
  • Presentation on the indy-node-container repo / project
  • Q&A

Recording of Call: 20220329 Indy Contributors Call Recording.mp4

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


Related Calls and Announcements

Release Status and Work Updates

Meeting Topics

  • Before the meeting: "did:indy" DID Method
    • Separate meeting held prior to this one. 
  • Update on CI/CD Update and Ubuntu Upgrade: Status Document
    • Indy-Plenum Status: 
      • Done, 16.04, 20.04, Jenkins and GHA
    • Indy-Node Status:
      • Done, 16.04, 20.04, Jenkins and GHA
      • One 20.04 running in the IDUnion network of 16.04 nodes
      • Preparing and executing the automated release process.
    • indy-test-automation Status:
      • Working systemd image for 20.04, but the tests are not working – client messages not getting to the server.
      • Seems like there is a solution in the indy-node-container work.  To be checked with Robin Klemens.
    • Developer tools
      • indy-node-container (moved to Hyperledger) and GitPod tools available (node and plenum)
      • NEED THIS FIXED – HELP NEEDED: On plenum – error with building the dev containers about Indy SDK version – need to get the metadata version correct (
        • Philipp raised a question on this, but no one had the info for an answer yet.
    • Indy-SDK build progress
      • Unblocked – builds are going and PRs are being reviewed (and rebasing PRs).
  • NEXT MEETING: How are we going to work through this issue and upgrade the various networks?
    • Concern - running mixed nodes 16.04 and 20.04 a consensus problem occurs "in a while" (sometimes immediately, sometimes a few days has been seen)
    • Robin has the details of what tests have been run and what observations have been done. See Hack MD document with some details. 
    • Perhaps because of libsodium v18 and v23.
    • It might also be a ledger corruption issue, perhaps with the lead node having corruption issues and then propagating those issue.
    • Can we get the indy-node-container folks run tests with a mixed environment of nodes
  • Presentation on the indy-node-container repo / project by Sebastian Schmittner

Future Calls

  • Issues that could impact indy-node on 20.04
    • indy-sdk: needs an upgrade to OpenSSL 1.1 to properly support Ubuntu 18.04/20.04.  For indy-node, just using indy-sdk as is.
    • Multiple libsodium versions could impact consensus – intermittent issue on a mixed network.
  • Plans for a new Indy-SDK release?
  • 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
  • Hyperledger campaign to recruit additional developers.

Action items