Versions Compared

Old Version 2

changes.mady.by.user Richard Esplin

Saved on

compared with

New Version Current

changes.mady.by.user Ajay Jadhav

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary:

Excerpt
Planned
  • Work updates
  • Future meetings
  • Status of the Sovrin Network
  • Work updates
  • Formal verification by Sven Hammann

Note: This call is Recorded. Recordings posted at the bottom of the page.

Date

01 (7AM Los Angeles, 10AM New York, 3PM London, 4PM CET, 18H Moscow)

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.

Attendees                                                                                                                                                            

  • Name (Employer) <email>
  • Richard Esplin (Evernym) <richard.esplin@evernym.com>
  • Sven Hammann (ETH Zurich) <sven.hammann.90@gmail.com>
  • Mike Richardson (EuroLedger) <emerysolutions@yahoo@co.uk>
  • Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
  • Sam Curren (Independent) <telegramsam@gmail.com>
  • Ajay Jadhav (AyanWorks) <ajay@ayanworks.com>

Welcome / Introductions

Announcements

Related Calls

  • Previous Aries Working Group calls
  • DIF DIDComm WG Call: Rolling Agenda.
  • Identity Implementors Working Group call
    • Main place to get project updates, release status, and announcements.

Release Status and Work Updates

  • Aries Protocol Test Suite
    • Issue, credential, and proof tests are merged.
  • Aries Shared:
    • indy-vdr (Andrew Whitehead) https://github.com/hyperledger/indy-vdr
      • Remaining work: Design doc, FFI, testing, CI / CD
      • As an Aries interface becomes standardized, will add that API layer
      • HTTP Proxy App updates
        • ACAPy using it as a proxy in a branch
      • Integrating into LibIndy in a separate branch, goal is to release in April/May
      • Rich Schemas functions are coming soon
      • 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 and aries-credx
      • https://github.com/sovrin-foundation/aries-credx-framework-rs
        • Generic APIs that are pluggable
        • Test vectors for interop
        • Coming soon: Rich Schemas functions
        • 6 most common attribute encodings
        • Does not yet have anoncreds 1 attribute encoding.
      • https://github.com/andrewwhitehead/indy-credx
        • Improved revocation (Annoncreds 1) support (faster tails generation)
          • Python wrapper using Pyo3 is solid. Needs FFI.
        • 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
      • Integrating upgraded PyO3 library
      • Create an Indy-Util for API types and other utility functions?
    • Aries-Shared-Util
      • Pack / Unpack
      • Not started yet
    • Aries-KMS
      • Mike Lodder working Mike working on documentation and architecture as an Aries RFC (KMS architecture) and Ursa RFC (API)
        • Differs from Indy Wallet architecture by separating out auth and access control. Intention is to ensure a smooth transition from Indy.
        • Ability to export keys under certain conditions (metadata is set upon key creation)
        • PR is submitted: https://github.com/hyperledger/aries-rfcs/pull/440
      • Mike Mike and Cam's aries-core-rs → rs → aries-kms-mayaguez
        https://github.com/sovrin-foundation/aries-kms-rs
        • Evolution from lox
        • Persistence work allows plugging in any database engine.
        • Focus is using an external enclave.Will include a default storage that is not a different implementation from the plugins
      • Indy wallet crate might move to start another aries-kms implementation → aries-kms-vostok
    • Aries-Storage
      • Non-KMS entities
  • Aries-CloudAgent-Python (bc.gov)
    • Release 0.4.5 is on PyPi.
    • Revocation support has merged into master and is likely to included in the next release. Some smoothing of the edges happening.
      • Note: uses anoncreds 1.0 (hence, tails files) and so will be constrained in use cases to those with small numbers of credentials (e.g. ~25k per RevReg.)
  • Aries-Framework-Go (Troy) #aries-go
  • Aries-SDK-Ruby (Jack)
  • Aries-Framework-DotNet (Tomislav)
    • Release last week for Aries compatibility with ACApy and LibVCX (RFC 0094)
  • Aries-StaticAgent-Python
  • Aries-Toolbox
    • Added basic message admin
    • Working on a getting started video
  • Aries-SDK-Java
  • Aries-Framework-JavaScript / Aries-SDK-JavaScript
  • Rich Schemas and W3C Verifiable Credentials (Brent & Ken)
  • Aries-OSMA / Aries-MobileAgent-Xamarin
  • Ursa
    • 0.4.0 scheduled for late March
      • Hash Improved hash to curve algorithm
      • Updates to AMCL wrapper
    • 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.

RFC Progress

Other Business

Future of this meeting

  • 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.
    • No apology is needed if people take longer to respond to things.
    • Richard's role changed, so we need a change in host.
    • Fewer meetings and more async collaboration?

Formal protocol verification by Sven HammanHammann

https://docs.google.com/presentation/d/1qFYNhenEQvKlvXixUhJ7EQcdrG8NWgcuFQl0NXw11hA/edit?usp=sharing


Future Topics

Action items

  •   

Call Recording

Attachments
uploadfalse
labelsrecording

...