2022-09-13 Indy Contributors Call

Zoom Link: https://zoom.us/j/99220079317?pwd=OHk0U05ITnBkSmZ0aXlIQzFDYWg3UT09

Summary

Recording of Call: 

Welcome and Introductions

Attendees

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

@Philipp Schlarb (esatus AG) <p.schlarb@esatus.com>

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

@Daniel Bluhm(Indicio PBC) <daniel@indicio.tech>

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

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 

• Vulnernabities - Published

  • https://github.com/hyperledger/indy-node/security/advisories/GHSA-r6v9-p59m-gj2p

  • https://github.com/hyperledger/indy-node/security/advisories/GHSA-x996-7qh9-7ff7

• Update on the Indy Ubuntu 20.04 Upgrade – Done?

  • Token-plugin nearly done. 

    • → found a problem with prepare script with indy-node Issue: https://github.com/hyperledger/indy-node/issues/1778
      PR: https://github.com/hyperledger/indy-node/pull/1779

  • libSovToken is nearly done as well, one outstanding Jenkins issue.

  • Sovrin package is next in line

• Root cause and solution to the "mixed node" problem: Indy Node issue 1769

  • It's worse than expected,,,,

  • A flag was added to the 20.04 based branch to set default ordering to sorted ordering, this unblocks the creation of new Ubuntu 20.04 networks.

  • Next step.  Explore a new config transaction to signal point in time events.  Modeled to be generic for other such issues, complete with helpers in the code to detect and cache the txns.

    • Transactions handling and caching could all be generic.  Only concrete implementation(s) (plugins) needed would be for the specific transaction types, such as the ordering switchover point we need now.

  • Timing of the fixes/release:

    • Decision point - Do we release 1.13.x with just compatibility ordering or wait until we have a mechanism to be able to switch to sorted ordering?

      • The group decided we should investigate the new config transaction proposal more and discuss the releases again in 2 weeks when we know more about implementation effort.

  •  Need volunteers to start looking into the proposed design. 

• Action item: work on did-indy-networks

  • https://github.com/hyperledger/indy-did-networks

    • @Christian Bormann started working on  a draft PR with documentation.

  • https://anoncreds-wg.github.io/anoncreds-objects-methods-registry/#governance

    • Reuse content from here for the indy-did-networks content.

re Calls

• GDPR and the right to be forgotten – mitigations and approaches.

• 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