...
Excerpt |
---|
Planned:
|
...
|
The call was recorded and available: 20200420 Indy Contributors Call.mp4.
Remember the Hyperledger Code of Conduct
...
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
- Sergey Minaev (Evernym) sergey.minaev@evernym.com
- Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>Name (Organization) <email>
Related Calls and Announcements
- Identity Implementors Implementer Working Group call (Wiki Page)
- Main place to get project updates, release status, and announcements.
- IIW is next week - please register and join from your home.
Release Status and Work Updates
- Move from Sovrin Foundation infrastructure - Wade Barnes
- Move from Jenkins to GitHub actions
- Sovrin Foundation Jenkins machines are going away
- Sovrin resource migration
- #cicd discussion "Indy CI / CD Migration" (in #cicd use menu item "Discussions" to see/get to the discussion)
- Move repo.sovrin.org → Hyperledger Artifactory for all except Sovrin Foundation specific artifacts
- Move from Jenkins to GitHub actions
- Indy Node
- April: no release
- MayMay:
- Replacing Indy Crypto with Ursa (Kiva)
- More "rich schema" objects
- Ubuntu 20.04 (Kiva)
- Need to check additional dependencies:
Jira server Hyperledger JIRA serverId 6326cb0b-65b2-38fd-a82c-67a89277103b key INDY-2196
- Need to check additional dependencies:
- Indy SDK
- March: 1.15.0:
- LibVCX improvements to reject proof and connection redirect
- Bug fixes April: no release
- May/June:
- Indy VDR into LibIndy
- Indy Credx into LibIndy
- https://github.com/bcgov/aries-vcr
- Working on transitioning to Hyperledger - rename, required files, documentation
- Being deployed at Government of Canada
- Mike: Creating a development plan in the Indy section of the wiki
- Mike: Aries-Credx
- Andrew: indy-credx
- Aries Shared:
- indy-vdr (Andrew Whitehead) https://github.com/hyperledger/indy-vdr
- Remaining workNearing release 1.0(?) - most work complete that was needed: Design doc, FFI, testing, CI / CD
- CD not there
- No design doc, but crate docs
- As an Aries interface becomes standardized, will add that API layer
- Need to check that duplicate copies of the util library doesn't cause trouble.Do we hold off on setting the version until this is in place. Maybe 0.8
- GitHub actions runs unit tests and basic integration tests
- VON Network browser moved to Indy-VDR instead of LibIndy (no wallet needed because it is stateless)
- Andrew working a
- refactor in a PR
- Put rich shemas behind a feature flag?
- Remaining workNearing release 1.0(?) - most work complete that was needed: Design doc, FFI, testing, CI / CD
- indy-credx - https://github.com/andrewwhitehead/indy-credx
- need to move ASAP to at least BC Gov repo - Andrew Whitehead
- ACA-Py branch created that can do credential exchange with indy-credx
- Next up: adding revocation 2.0 support
- Integrating upgraded PyO3 library
- indy-shared-rs - https://github.com/bcgov/indy-shared-rs
- Shared features across indy-vdr and indy-credx
- pack/unpack on Ursa (not libsodium)
- home for revocation support? Or at least shared set membership proof handling?
- indy-credx / aries-credx
- https://github.com/sovrin-foundation/aries-credx-framework-rs
- 6 most common attribute encodings
- Does not yet have anoncreds 1 attribute encoding.
- Can make a non-revocable credential and create proofs.
- Tagging will be moved to the KMS.
- Mike will be working on revocation registry 2.0
- Create an Indy-Util for API types and other utility functions?
- https://github.com/sovrin-foundation/aries-credx-framework-rs
- Aries-Util
- Pack / Unpack
- Not started yet
- Aries Secure Storage initiatives:Aries-KMS
- Mike working on documentation and architecture as an Aries RFC (KMS architecture) and Ursa RFC (API)
- PR is submitted: https://github.com/hyperledger/aries-rfcs/pull/440
- Mike and Cam's work aries-core-rs → aries-kms-mayaguez - repo? features?
https://github.com/sovrin-foundation/aries-kms-rs- Persistence work allows plugging in any database engine.
- Focus is using an external enclave.
- Indy wallet crate might move to start another aries-kms implementation → aries-kms-vostok
- Mike working on documentation and architecture as an Aries RFC (KMS architecture) and Ursa RFC (API)
- Aries-Storage
- Non-KMS entities
- indy-vdr (Andrew Whitehead) https://github.com/hyperledger/indy-vdr
- To replace libsodium, need to have a replacement for the anoncrypt / authcrypt sealed box for pack / unpack.
- Can be done in Ursa with two steps, but might add as a single function call.
Other Business
- Working on Postgres storage; will need help on lox
- Something out the end of the week.
- Ursa
- Not covered
Other Business
- Move to GitHub Issues from JIRA for indy-sdk, indy-node, indy-plenum
- Activate issues, update README to mention history
- Plan - Lazy Migration: Migrate current, likely to happen JIRAs to Issues as needed
- NOTE: about 200 open issues on indy-sdk with a guess of about 50% to be moved
- Even more open issues on plenum and node
- NOTE: about 200 open issues on indy-sdk with a guess of about 50% to be moved
- Action: Stephen to get Ry to activate Github issues; update READMEs to reflect change.
- Migrate Jenkins to GitHub Actions (and perhaps Azure pipelines)
- Plan started - Sovrin resource migration
- Resources: Wade Barnes (BC Gov), Thor Wolpert (BC Gov) for first step (Indy SDK/Linux)
- Revocation 2.0
- Presentation (summary of what was presented on the Aries WG Call)
- General agreement on the approach.
- Comments from discussion:
- The limiting factor will be the calculations and space needed by the prover to create the merkle tree interior nodes
- What are the space/time trade-offs between repeating calculations per proof vs. caching the calculated tree?
- Action: need some experimenting with the approach - compression and space/time for tree calculations
- Please provide feedback on the proposed design (see JIRA: Indy-2365)
- Do we need to update/release indy-node if transactions are the same but data is new?
- Yes, but not much. Mainly to verify the content of the data before writing to the ledger.
- Presentation (summary of what was presented on the Aries WG Call)
Future Calls
Next call:
Future:
...
- PR to RFC #0019 to compare pack/upack to msgpack (Sergey)
- Review the 61 cases of "unsafe" libindy calls and figure out if they are justified.
Call Recording
View file | ||||
---|---|---|---|---|
|