2020-01-20 Indy Contributors Call
Summary
- Work updates
- Getting started in the Hyperledger community
Timezone: America afternoon / Pacific 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>
- Richard Esplin (Evernym) <richard.esplin@evernym.com>
Related Calls and Announcements
- 2020-01-13 Indy Contributors Call
- Identity Implementors Working Group call
- Main place to get project updates, release status, and announcements.
- Recording and slides are posted for the SSI Meetup webinar on Indy and Plenum.
Release Status and Work Updates
- Indy Node
- December: 1.12.1
- Improvements to the TAA behavior
- Roll-out to Sovrin Network delayed: Post-release identified corner cases related to View Change, and weirdness seen during Builder Net upgrade. Investigation is ongoing.
- January:
- 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
- Just posted Indy HIPE
- Replacing Indy Crypto with Ursa (Kiva)
- Debian packages for Ursa-0.3.0 are uploaded to repo.sovrin.org
- Additional rich schemas objects: schema object (Sovrin Foundation)
- Future
- Ubuntu 18.04 (Kiva)
- Need to check additional dependencies: Error rendering macro 'jira' : null
- Need to check additional dependencies:
- Remove replicas (Aardvark BFT) ?
- Anoncreds 2.0 (Sovrin Foundation)
- Ubuntu 18.04 (Kiva)
- December: 1.12.1
- Indy SDK
- December: 1.14.0 / 1.14.1
- LibVCX support for Aries Interop v1
- Improvements to the TAA behavior
- January:
- Bugfixes
- 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
- December: 1.14.0 / 1.14.1
- Indy Catalyst
- https://github.com/bcgov/indy-catalyst
- Production deployment testing: volume loads.
- Happy with performance now.
- Migrating to Hyperledger Aries: plan is to moving to aries-verified-credential-registry
- 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.
- 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.
- Aries Shared Libraries
- indy-aries-vdr (Andrew Whitehead) https://github.com/andrewwhitehead/indy-ledger-client
- Next is indy-aries-anoncreds with anoncreds 1 (ready to add anoncreds 2)
Main Business
- Getting started in the Hyperledger community:
- Get a Linux Foundation ID: https://identity.linuxfoundation.org/
- Rocket Chat: http://chat.hyperledger.org
- Indy Jira: http://jira.hyperledger.org/browse/INDY
Indy SDK Jira: http://jira.hyperledger.org/browse/IS - Mailing Lists: https://lists.hyperledger.org/g/indy
- Identity WG and Identity Implementers WG
- SSI Meetup (especially the session on Indy announced above)
- Learning about Rich Schemas:
https://github.com/hyperledger/aries-rfcs/tree/master/features/0281-rich-schemas
https://github.com/hyperledger/aries-rfcs/tree/master/features/0249-rich-schema-contexts
Future Calls
- Jan 27: Results from performance testing LibIndy (BC.gov)
- 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?
- INDY-2305: Add IP address range for outbound TCP connections from validator nodes
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.