2020-03-23 Indy Contributors Call

Summary

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

• Name (Organization) <email>

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

Related Calls and Announcements

• Identity Implementors Working Group call

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

• Results from call to discuss techniques for supporting an Indy Network

Release Status and Work Updates

• Indy Node

  • March:

    • Replacing Indy Crypto with Ursa (Kiva)

    • More "rich schema" objects

  • Future

    • Ubuntu 18.04 (Kiva)

      • Need to check additional dependencies: 

        Error rendering macro 'jira' : null

• Indy SDK

  • March: 

    • 1.15.0:

      • LibVCX improvements to reject proof and connection redirect

      • Bug fixes

• Aries VCR

  • https://github.com/bcgov/indy-catalyst

  • Working on transitioning to Hyperledger - rename, required files, documentation

  • Being deployed at Government of Canada

• Anoncreds 2.0

  • Mike: Creating a development plan in the Indy section of the wiki

  • Mike: Aries-Credx

  • Andrew: indy-credx

• Aries Shared Libraries

  • Aries Shared:

    • indy-vdr (Andrew Whitehead)  https://github.com/hyperledger/indy-vdr

      • Remaining work: Design doc, FFI, testing, CI / CD

        • PR for using GitHub actions to run unit tests for CI.

          • Mike can help review.

          • Mike and Artem can help with CD artifacts for the various platforms.

      • As an Aries interface becomes standardized, will add that API layer

      • Split out an Indy-Util to contain common components between Indy-VDR and Indy-Credx

        • Need to check that duplicate copies of the util library doesn't cause trouble.

    • indy-credx / aries-credx

      • https://github.com/sovrin-foundation/aries-credx-framework-rs

        • 6 most common attribute encodings

        • Does not yet have anoncreds 1 attribute encoding.

      • https://github.com/andrewwhitehead/indy-credx

        • Can make a non-revocable credential and create proofs.

        • Tagging will be moved to the KMS.

        • Mike will be working on revocation registry 2.0

    • Aries-Shared-Util

      • Pack / Unpack

      • Not started yet

    • Aries-KMS

      • Mike working on documentation and architecture as an Aries RFC (KMS architecture) and Ursa RFC (API)

        • PR is submitted: https://github.com/hyperledger/aries-rfcs/pull/440

      • Mike and Cam's aries-core-rs → aries-kms-mayaguez
        https://github.com/sovrin-foundation/aries-kms-rs

        • Persistence work allows plugging in any database engine.

        • Focus is using an external enclave.

      • Indy wallet crate might move to start another aries-kms implementation → aries-kms-vostok

• Ursa 0.3.2

  • To replace libsodium, need to have a replacement for the anoncrypt / authcrypt sealed box for pack / unpack.

    • Can be done in Ursa with two steps, but might add as a single function call.

Other Business

• Change to meeting room

  • https://lists.hyperledger.org/g/indy/viewevent?repeatid=13838&eventid=708081&calstart=2020-03-23​_

• Status of the Sovrin Network

• Pick an issue reported against the Sovrin networks, and show how we found the problem in the logs. @Sergey Khoroshavin

  • Error rendering macro 'jira' : null

Future Calls

Next call:

Future:

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

Action items

Call Recording

Open

Open

Open