2021-10-26 Indy Contributors Call

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

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

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

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 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/

Update on CI/CD Update and Ubuntu Upgrade: Status Document

• Indy-Plenum Status: 

  • Done

• Indy-Node Status:

  • Done

• indy-test-automation Status:

  • All tests running in GHA – PR to remove the circular dependencies / no delete just move (separate branch?)

    • Leave the tests in the repo but not being called

    • Next would be to put them into a separate repo

      • Run core tests, option to run other tests from other repos.

  • All tests are passing!

  • Removed all the sovtoken

  • Still need to test the new dependencies in artifactory – still using sovrin repo.

• Sovrin Release - @Wade Barnes Status:

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.