Page Comparison

Summary

...

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.

...

• Name (Organization) <email>
• Richard Esplin (Evernym) <richard.esplin@evernym.com>
• Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
• Kumaravel N (Ford) <nkumara2@ford.com>

Related Calls and Announcements

...

Release Status and Work Updates

• Move from Jenkins to GitHub actions
  • Jenkins machines are going away
• Indy Node
  • April:
    • Replacing Indy Crypto with Ursa (Kiva)
    • More "rich schema" objects
  • May:
    • Ubuntu 18.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
• Aries VCR
  • https://github.com/bcgov/indy-catalyst
  • Working on transitioning to Hyperledger - rename, required files, documentation
  • Being 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 work: Design doc, FFI, testing, CI / CD
        • PR for using GitHub actions to run unit tests for CI.
          • Mike can help review.
          • Mike and Artem can help with CD artifacts for the various platforms.
      • 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.
    • 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-credx
        • 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
    • Aries-Shared-Util
      • Pack / Unpack
      • Not started yet
    • 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 aries-core-rs → aries-kms-mayaguez
        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
• 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

• Future of this meeting (and Indy collaboration generally)

  • We recognize as a community that each of us needs to adapt to current global events: improving the upstream open source libraries is likely to be slower.
    • Note from Aries calls: no apology is needed if people take longer to respond to things.
    • My role changed, so we need a change in host.
    • Fewer meetings and more async collaboration?

Future Calls

Next call:

Future:

...