2019-12-16 Indy Contributors Call

Summary

Timezone: EMEA afternoon / America morning

We intend to record this call.

Remember the Hyperledger Code of Conduct

Anti-Trust Policy

Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.

Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

Introductions

Attendees

• @Richard Esplin(Evernym) <richard.esplin@evernym.com>

• @Sergey Khoroshavin  (Evernym) <sergey.khoroshavin@evernym.com>

• @Tomislav Markovski (Streetcred) <tomislav@streetcred.id>

Related Calls and Announcements

• Note the updated calendar invitation on the Hyperledger Calendar

• Call schedule

  • December 16 (US+EMEA): normal

  • December 23: cancelled

  • December 30: cancelled

  • January 6 (US+APAC): cancel

  • January 13 (US+EMEA): normal

• ssimeetup.org webinars

  • December 17: Deep dive into the Plenum Ledger

• Hyperledger edX course - Introduction to Hyperledger Sovereign Identity Blockchain Solutions: Indy, Aries & Ursa

• Previous Indy Contributors call

• Identity Implementors Working Group call

  • Main place to get project updates, release status, and announcements.

Release Status and Work Updates

• Indy Node

  • December: 1.12.1

    • Improvements to the TAA behavior

    • Additional rich schemas objects: schema object (Sovrin Foundation)

      • Just posted Indy HIPE
        https://github.com/hyperledger/indy-hipe/pull/149

      • Aries RFC
        https://github.com/hyperledger/aries-rfcs/pull/281

      • PR of schema object in progress for December

      • Making progress on other RFCs for objects and one that shows how all the objects fit together.

      • Next: encoding object, then mapping object

  • Future

    • Ubuntu 18.04 (Kiva)

      • Need to check additional dependencies: 

        Error rendering macro 'jira' : null

    • Replacing Indy Crypto with Ursa (Kiva)

    • Remove replicas (Aardvark BFT) ?

    • Anoncreds 2.0 (Sovrin Foundation)

• Indy SDK

  • December: 1.14.0

    • LibVCX support for Aries Interop v1

    • Improvements to the TAA behavior

  •  Future

    • Deprecating some docs (IS-1425: Getting Started Guides) and wrappers (IS-1423: Python and DotNet)

    • Deprecate  additional wrappers (IS-1424) and LibVCX (IS-1416)

    • GitLab migration alongside Jenkins (Foundation)?

    • Warnings from rust cargo clippy (Mike and Axel), epic: IS-1401

• Indy Catalyst

  • Production deployment testing: volume loads.

    • Happy with performance now.

  • Not yet migrated to Hyperledger. Needs more documentation.

• New design for revocation / Anoncreds 2.0 (Mike)

  • Would be useful to have a comparison in performance between Anoncreds 1.0 and Anoncreds 2.0

  • Need a plan for changes to Indy Node

    • HIPE for overall changes, then a design PR for the changes specific to the different repos.
      https://github.com/hyperledger/indy-node/tree/master/design

    • BC.gov will implement the existing revocation capability in ACA-Py for use in constrained cases

      • Looking to build against Anoncreds 2.0 as soon as it is available.

      • Unable to contribute to the Anoncreds 2.0 revocation capability at this time - no resources for that work.

Main Business

• Changes to the Transaction Author Agreement

• Migrating LibIndy to Aries
  

  

  • Indy Resolver becomes Indy-Aries-VDRI

    • Can wait to follow the DID-resolution spec, because the spec doesn't have enough detail today.

  • Indy Anoncreds becomes Indy-Aries-Anoncreds

    • We prefer keeping it as a separate repo in Indy until another ledger shows interest.

    • We considered Aries-Shared-Creds-Anoncreds, but it is likely that it is closely tied to Indy at least in the short term. The interface should live in Aries.

  • Indy Wallet becomes Aries-Shared-KMS

    • Includes plugin interface

    • Aries-Shared-KMS-PostgreSQL

    • Aries-Shared-KMS-SQLite

• Evernym can assist with:

  • Consensus

  • Revocation

  • Rich Schemas

  • DID Doc

• Other themes from the Aries Connect-a-thon

• Requirements questions:

  • INDY-2305: Add IP address range for outbound TCP connections from validator nodes

    • Changes the way nodes are represented in the Pool Ledger

• How soon should we deprecate the LibIndy .NET wrapper.

Future Calls

• January 13: Indy performance analysis (BC.gov)

• Requirements questions:

  • IS-1099: anoncreds.prover_get_credentials_for_proof_req should return per-credential timestamp

    • Should we allow duplicate credentials from the same issuer?

• Non-secrets in the Indy Wallet

  • Cam is working on pluggable crypto. The wallet shouldn't decide what encryption you should be using.

  • Use cases where we would want to move keys between wallets

    • Moving the link secret / credential data from one device to another (synchronized storage).

    • Debug use cases

    • Richard's hit other uses cases that were better solved with DID Doc,  pre-signing, signing API.

  • Work-around with the web-crypto API

• Migration of Indy-SDK to Aries-Core

Action items

Call Recording

Open