2022-01-04 Indy Contributors Call

Summary

Recording of Call: dummyfile.txt

Welcome and Introductions

Attendees

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

• @Robin Klemens  (Institute for Internet Security) <klemens@internet-sicherheit.de>

• @Wade Barnes

• @Sean Bohan_personal

• @Sebastian Schmittner (EECC) <sebastian.schmittner@eecc.de>

Related Calls and Announcements

BC Gov Indy DiD Method Code With Us opportunity: https://digital.gov.bc.ca/marketplace/opportunities/code-with-us/e3dd1605-cc1d-4c30-a9ee-245940bccd0d

Training - significant response to these postings!

• Aries Training: https://twitter.com/Hyperledger/status/1472971986800316417

• Indy Node "Deep Dive": https://lf-hyperledger.atlassian.net/wiki/display/events/Hyperledger+Indy+Technical+Deep+Dive

Release Status and Work Updates

• Indy Node

  • GitHub actions led by @Wade Barnes

  • Ubuntu 20.04 upgrade led by @Robin Klemens 

  • Sovrin Updates @Wade Barnes 

  • New branching model led by @Wade Barnes

  • indy-node-container Crisitan Kubis ( https://github.com/tsurai ), has created a Node Controller Container (docs), allows containerized indy nodes to participate in pool restart and upgrade

• Indy SDK

  • GitHub actions led by @Patrik Stas

  • LibVCX tests are failing. Proposal is to deprecate LibVCX in the Indy SDK, and focus on aries-vcx.

• Indy Monitoring - https://github.com/hyperledger/indy-node-monitor

• Indy/Aries Shared Libraries - Hyperledger (indy-vdr, indy-shared-rs, aries-askar)

• Ursa

  • Appears that refactor has stalled? Need volunteers.

• Hyperledger Contribution Campaign ( @Stephen Curran )

• Indy DID Method – https://hyperledger.github.io/indy-did-method/

Meeting Topics

• Developer Experience:

  • VS Code Dev container: https://github.com/hyperledger/indy-node/pull/1718 - minor updates

  • Gitpod Dev container: https://github.com/hyperledger/indy-node/pull/1722 - minor updates

  • Documentation being updated and getting merged

• 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

  • indy-test-automation Status:

    • Merged (no circular dependencies!!!!!) - 16.04

    • Still to be done: 20.04 – systemd image needs to be replaced – may have to be created.

    • Workflow to trigger - needs a secret setup / @Ry Jones

  • Currently releasing development artifacts – left to do is a tag-based official release process - @Wade Barnes with help from @Robin Klemens

  • ** Sovrin Release - @Wade Barnes Status:

    • Working ready to start in the three repos in Sovrin

• Getting Started on the "did:indy" DID Method
  
  

  • Overview (if needed)

    • Indy DID Method – https://hyperledger.github.io/indy-did-method/

  • BC Gov code with us launched

  • IDUnion plans

  • Discussion

    • Need a pull request to add the new Indy DID method to the W3C registry: https://github.com/w3c/did-spec-registries

    • @Paulstarted the Indy DID Resolver driver. Will publish a WIP PR when he has an MVP.

• 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.

Future Calls

• Plans for a new Indy-SDK release?

  • A few people from the community have asked.

  • The most recent request has been for a release to include this feature; https://github.com/hyperledger/indy-sdk/pull/2400

• Indy Contributor Campaign

  • Focus: Indy Generation Next

    • Audience: Organizations building Indy Instances, applications built on Indy

      • Not going for casual, independent developers, more on organizations that can assign developers to work on the project for a set chunk of time (e.g one month)

    • Key Features:

      • Indy network of networks support

      • Indy support for W3C DID Standard 1.0

    • Tasks:

      • Update NYM to support new "diddoc_content" data element

      • Indy-sdk, indy-vdr support for new "diddoc_content" data element

      • Indy DID Resolver support for new "diddoc_content"

      • indy-sdk, indy-vdr support for multiple ledgers

      • Support for new ledger object identifiers

      • Handling cred_defs that references schema on other ledgers

      • Possible: support for NYM "keri_keystate" data element, indy-sdk/indy-vdr support and DID resolver support

      • Other?

    • Foundational Work:

      • did:indy spec. as a spec.

      • Tasks in GitHub Issues - tagged for campaign

      • Getting started with developing indy-plenum and indy-node

        • Tutorial: Sample feature to add to indy-node

          • Example: rich schema feature flag

    • Campaign work

      • Landing page

      • Video: Intro to Indy Generation Next

      • Meetup channels

• Changes to indy-node needed for did:indy

• 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