Summary
| Excerpt |
|---|
|
...
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.
...
- Indy Node
- December: 1.12.1
- Improvements to the TAA behavior
- 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
- Future
- Ubuntu 18.04 (Kiva)
- Need to check additional dependencies:
Jira Legacy server Hyperledger JIRA serverId 6326cb0b-65b2-38fd-a82c-67a89277103b key INDY-2196
- Need to check additional dependencies:
- Replacing Indy Crypto with Ursa (Kiva)
- Debian packages for Ursa-0.3.0 are uploaded to repo.sovrin.org
- Remove replicas (Aardvark BFT) ?
- Anoncreds 2.0 (Sovrin Foundation)
- Ubuntu 18.04 (Kiva)
- December: 1.12.1
- Indy SDK
- December: 1.14.0
- LibVCX support for Aries Interop v1
- Improvements to the TAA behavior
- 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
- Indy Catalyst
- Production deployment testing: volume loads.
- Happy with performance now.
- Not yet migrated to Hyperledger. Needs more documentation.
- Production deployment testing: volume loads.
- 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.
- HIPE for overall changes, then a design PR for the changes specific to the different repos.
...
- 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
- INDY-2305: Add IP address range for outbound TCP connections from validator nodes
Future Calls
...
- 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?
- IS-1099: anoncreds.prover_get_credentials_for_proof_req should return per-credential timestamp
- 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
...