Summary
Planned:
- Work updates
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
- Going forward, we will not be holding the AMER afternoon / APAC morning call
- Identity Implementors Working Group call
- Main place to get project updates, release status, and announcements.
Release Status and Work Updates
- Indy Node
- February:
- Replacing Indy Crypto with Ursa (Kiva)
- More "rich schema" objects
- Future
- Ubuntu 18.04 (Kiva)
- Need to check additional dependencies:
- February:
- Indy SDK
- February:
- Bug fixes
- February:
- Indy Catalyst
- https://github.com/bcgov/indy-catalyst
- Migrating to Hyperledger Aries: plan is to moving to aries-verified-credential-registry
- Needs more documentation
- Anoncreds 2.0 (Mike)
- Implementing in an Aries Shared Library
- Aries Shared Libraries
- indy-aries-vdr (Andrew Whitehead) https://github.com/andrewwhitehead/indy-ledger-client
- Next steps:
- VDR Design Doc
- FFI
- Unit tests
- Functional tests
- Migrate repo to Hyperledger
- First commit should point to previous history in indy-sdk
- Integrate into existing LibIndy
- HTTP proxy
- Next steps:
- indy-aries-anoncreds
- Mike has started. Repo for Aries cred exchange framework.
https://github.com/sovrin-foundation/aries-credx-framework-rs - Microsoft might be taking a different approach to ZKP revocation
https://eprint.iacr.org/2019/550.pdf
- Mike has started. Repo for Aries cred exchange framework.
- Aries-Shared-Util
- Need a place for Rich Schemas functions
- Lift-and-shift would be Indy specific, but refactoring for Aries could take a long time
- Aries-KMS
- Would like a volunteer to move the wallet crate so we have a starting point
- Overlap with Mike's aries-core-rs → aries-kms-ml
https://github.com/sovrin-foundation/aries-core-rs - Evernym will move the Indy wallet → aries-kms-taiga
- indy-aries-vdr (Andrew Whitehead) https://github.com/andrewwhitehead/indy-ledger-client
- Ursa 0.3.2
- Releasing this week?
- Implements key exchange, so LibSodium hopefully is no longer required
Main Business
- Special call on troubleshooting Indy
- Tuesday February 25
- Conflicts: US February 17, Russia February 24, HL Global Forum March 2, Russian March 9
- Collaborate on Rich Schemas
- Ken has a conflict
- 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?
- INDY-2305: Add IP address range for outbound TCP connections from validator nodes
- IS-1222 blocked by Ursa CI / CD
- IS-1099: anoncreds.prover_get_credentials_for_proof_req should return per-credential timestamp
Future Calls
Next call:
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.