Page Comparison

Summary

We intend to record this call.

...

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

• Identity Implementors Implementer Working Group call (Wiki Page)
  • Main place to get project updates, release status, and announcements.

...

• Move from Sovrin Foundation infrastructure
  • 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
• Indy Node
  • April: no release
  •  May:
    • Replacing Indy Crypto with Ursa (Kiva)
    • More "rich schema" objects
    • Ubuntu 20.04 (Kiva)
      • Need to check additional dependencies: 

        Jira Legacy
        server Hyperledger JIRA serverId 6326cb0b-65b2-38fd-a82c-67a89277103b key INDY-2196

• Indy SDK
  • March: 
    • 1.15.0:
      • LibVCX improvements to reject proof and connection redirect
      • Bug fixes
  • April: no release
  • May:
    • Indy VDR into LibIndy
    • Indy Credx into LibIndy
• Aries Verifiable Credentials Registry (VCR)
  • https://github.com/bcgov/aries-vcr
  • Working on transitioning to Hyperledger - rename, required files, documentation
  • Being deployed Deployed at Government of Canada
• Anoncreds 2.0
  • Mike: Creating a development plan in the Indy section of the wiki
  • Mike: Aries-Credx
  • Andrew: indy-credx
• Aries Shared Libraries
  • Aries Shared:
    • indy-vdr (Andrew Whitehead)  https://github.com/hyperledger/indy-vdr
      • Remaining workNearing release 1 - most work complete that was needed: Design doc, FFI, testing, CI / CD
      • As an Aries interface becomes standardized, will add that API layer
      • Split out an Indy-Util to contain common components between Indy-VDR and Indy-Credx
        • Need to check that duplicate copies of the util library doesn't cause trouble.
      • 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
        large
        • refactor in a PR
      • Put rich shemas behind a feature flag?
    • indy-credx / indy-credx
      • https://github.com/andrewwhitehead/indy-credx
        • need to move to at least BC Gov repo
      • ACA-Py branch created that can do credential exchange
      • Next up: adding revocation 2.0 support
    • indy-shared-rs - https://github.com/bcgov/indy-shared-rs
      • Shared features across indy-vdr and 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.
      • https://github.com/andrewwhitehead/indy-credxCan make a non-revocable credential and create proofs.
        • Tagging will be moved to the KMS.
        • Mike will be working on revocation registry 2.0
      • Integrating upgraded PyO3 library
      • Create an Indy-Util for API types and other utility functions?
    • Aries-Util
      • Pack / Unpack
      • Not started yet
    • Aries-KMSAries Secure Storage initiatives:
      • 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
      Aries-Storage
      • Non-KMS entities
  • Ursa 0.3.2
    • 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

• Move to GitHub Issues from JIRA for indy-sdk, indy-node, indy-plenum
  • Activate issues, update README to mention history
  • Possible: Migrate current, likely to happen JIRAs to Issues
• 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)
  • 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?

Future Calls

Next call:

Future:

...