2020-02-03 Indy Contributors Call

Summary

Timezone: America afternoon / APAC 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

• Name (Organization) <email>

Related Calls and Announcements

• Aries Working Group: Performance Testing LibIndy and ACA-Py
  • Presentation: 2020-01-22-B Aries Working Group Call (starting ~65 minutes in)
  • Follow-up Q&A: 2020-01-27-A Aries Working Group Call
• Identity Implementors Working Group call
  • Main place to get project updates, release status, and announcements.

Release Status and Work Updates

• Indy Node
  • January:
    • Bugfix-release for edge cases in consensus protocol 
    • 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
    • Replacing Indy Crypto with Ursa (Kiva)
      • Debian packages for Ursa-0.3.0 are uploaded to repo.sovrin.org
  • Future
    • Ubuntu 18.04 (Kiva)
      • Need to check additional dependencies: 
        Error rendering macro 'jira' : null
    • Anoncreds 2.0 (Sovrin Foundation)
• Indy SDK
  • January:
    • Bugfixes 1.14.2
  •  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
  • https://github.com/bcgov/indy-catalyst
  • Migrating to Hyperledger Aries: plan is to moving to aries-verified-credential-registry
    
    • Needs more documentation
• New design for revocation / Anoncreds 2.0 (Mike)
  • Need a plan for changes to Indy Node
    • Design: https://github.com/hyperledger/ursa-docs/tree/master/specs/anoncreds2
    • 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, starting with extracting anoncreds from libindy into indy-aries-anoncreds
  • Comparison of Anoncreds 1.0 and 2.0: https://docs.google.com/presentation/d/18aqk5q1sqRI_UhOEuXWAS46-Oltsu_HNk_JtKfDVBGc/edit#slide=id.g790163706e_0_0
• Aries Shared Libraries
  • indy-aries-vdr (Andrew Whitehead) https://github.com/andrewwhitehead/indy-ledger-client
    • Rust API is almost completed
    • No FFI
    • HTTP proxy
  • Next is indy-aries-anoncreds with anoncreds 1 (ready to add anoncreds 2)

Main Business

Future Calls

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

• HIPE #138, Issue #144 (Ken and Brent)
  
  • Create a PR for changing status to ACCEPTED
  • Check for an Aries RFC
• PR to RFC #0019 to compare pack/upack to msgpack (Sergey)
• Richard and Sergey will close old pull requests with a descriptive comment.
• Mike wants to review the 61 cases of "unsafe" libindy calls and figure out if they are justified.

Call Recording