- Work updates
- Pull request review process for Indy Node
Timezone: US afternoon / APAC morning
We intend to record this call.
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.
Related Calls and Announcements
Release Status and Work Updates
- Indy Node
- November: 1.12.1
- Bug fixes
- Ubuntu 18.04 (Kiva)
- Need to check additional dependencies:
- Replacing Indy Crypto with Ursa (Kiva)
- Additional rich schemas objects: schema object (Sovrin Foundation)
- December / January: 1.23.0
- Remove replicas (Aardvark BFT) ?
- Rich Schema progress: encoding object
- Anoncreds 2.0 (Sovrin Foundation)
- Indy SDK
- November 1.13.0
- Issue reported by BC.gov:
- Need to include a manual release of iOS artifacts
- LibVCX support for some Aries protocols
- Deprecating some docs (IS-1425: Getting Started Guides) and wrappers (IS-1423: Python and DotNet)
- Bug fixes
- 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.
- Trying to identify performance bottlenecks. Currently think it's calls to the database.
- Performance problems is preventing going to production.
- 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)
- Cloud Compass is building the Linux Foundation EdX courses for Indy and Aries
- Overview launch date: November 21st
- More content will follow
- 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.
- 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.
- Define the pull request review process for Indy Plenum/Node
- Consensus protocols in Indy
- Besu uses BFT:
- Concerns with Aardvark versus RBFT
- Update on LibVCX support for Aries
- Indy performance analysis (BC.gov)
- Migration of Indy-SDK to Aries-Core
- Requirements question: IS-1099, 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
- 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 was not recorded