...
- Name (organization) <email>
Related Calls and Announcements
- Previous Indy Contributors call
- Identity Implementors Working Group call
- Main place to get project updates, release status, and announcements.
- Bootcamp Russia: Event Location
- Hyperledger Maintainers Summit: Minneapolis October 8-10
- Aries Workshop/Connectathon December 3-5 in Provo, Utah (details to follow)
Summary of Prior Call
Release Status
- Indy Node
- September: 1.10.0
- Refactoring for PBFT View Change and BLS signature
- Bug fixes
- Indy Node and Indy Plenum support for Ubuntu 18.04 is at risk for September
- October: 1.11.0
- PBFT view change
- September: 1.10.0
- Indy SDK
- September: 1.12.0
- Fully qualified DIDs
- Platform Updates: MacOS, CentOS
- Future
- GitLab migration alongside Jenkins (Foundation)?
- Aries / Indy split: next step is aries-core-wallet
- Anoncreds 2.0 (Sovrin Foundation, BC.gov?)
- September: 1.12.0
- Ursa
- September: 0.2.0
- ZKP / ZKLang improvements
- Debian packages
- Encryption for Anoncreds 2.0
- Refactor multi-signature BLS in addition to aggregated signature
- September: 0.2.0
- Aries
- Lots of progress on language libraries, frameworks, and agents.
- Lots of progress on language libraries, frameworks, and agents.
- Indy Catalyst
- Production deployment testing: volume loads.
- Won't go live in production at BC.gov until October.
- Not yet migrated to Hyperledger. Needs more documentation.
...
- Documentation improvements: Michael B and Stephen C
- Need to review and prune out-of-date documentation (Alice / Faber treatment of pairwise DIDs is a key pain point)
- Michael is working on Indy Agent walkthrough using C#
- Finishing work on ReadTheDocs (2 more weeks?)
- Cloud Compass is building the Linux Foundation EdX courses for Indy and Aries
- SDK 2.0 architecture / Indy-Aries split (Sergey)
- Kiva is working on a Futures implementation of threading (instead of call-backs) (https://github.com/kiva/aries-sdk.git)
- CI / CD: GitLab migration (Mike and Steve G)
- Demos in the Identity Implementers WG calls
- Hyperledger is also evaluating Azure Pipelines
- Advanced Schemas and W3C creds (Ken)
- Can successfully write and retrieve the Context object from the node code. Will track through all layers up to Aries.
- 5 additional objects need to be added.
- Working on the HIPE for the new Schema object.
- Warnings from rust cargo clippy (Mike and Axel)
- IS-1270 through IS-1274
- 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
- First draft is latex document in Ursa repo. Will be published as PDF and HTML.
- 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
- HIPE for overall changes, then a design PR for the changes specific to the different repos.
- Getting Ursa artifacts published that can be used by Indy Node and Indy SDK (Mike and Cam)
Other Business
- Update on Indy / Aries split
- Define pull request review process for Indy Node.
- Should define the process, including how we handle exceptions (emergency fixes shouldn't be blocked, but would require notification)
- What is important in a good review?
- If a review must be skipped, should note it in the Git commit message.
- Non-secrets in the Indy Wallet
- Cam is working on pluggable crypto. They 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
Future Calls
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.
...