2020-02-12-A Aries Working Group Call (AMER morning)

Summary:

• Work updates
• Discussion of Aries-Framework-Go

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

Date

12 Feb 2020 (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>
• Troy Ronda (SecureKey) <troy.ronda@securekey.com>
• John Callahan (Veridium) <jcallahan@veridiumid.com>
• George Aristy (SecureKey) <george.aristy@securekey.com>
• Sven Hammann (ETH Zurich) <sven.hammann.90@gmail.com>
• Filip Burlacu (SecureKey) <filip.burlacu@securekey.com>
• Sam Curren (Sovrin Foundation) <sam@sovrin.org>
• Richard Esplin (Evernym) <richard.esplin@evernym.com>
• Sudesh Shetty (SecureKey) <sudesh.shetty@securekey.com>
• Rolson Quadras (SecureKey) <rolson.quadras@securekey.com>
• Marvin Berstecher  (esatus AG) <m.berstecher@esatus.com>

Welcome / Introductions

Announcements

• Hyperledger Diversity, Civility, and Inclusivity Survey

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/andrewwhitehead/indy-ledger-client
    • Basically usable
    • Remaining work: Design doc, FFI, and testing
    • Will migrate repo to Hyperledger
    • As an Aries interface becomes standardized, will add that API layer
  • indy-aries-anoncreds / indy-creds → indy-credx
    • https://github.com/sovrin-foundation/aries-credx-framework-rs
  • Aries-Shared-Util
    • Pack / Unpack
    • Not started yet
  • Aries-KMS
    • Will support multiple approaches
    • Mike and Cam's aries-core-rs → aries-kms-(placeholder)
      https://github.com/sovrin-foundation/aries-core-rs
    • aries-kms-taiga: evolution of the Indy wallet crate as a starting point
      
• Aries-CloudAgent-Python (bc.gov)
• Aries-Framework-Go (Troy) #aries-go
• Aries-SDK-Ruby (Jack)
  • Added DID/Verkey sign_and_submit to aries_sdk_ruby and published new gem (0.0.8)
  • Created aries-rails-docker experiment that support Rails 4 with Indy 1.8.1 on Heroku & Dokku
• Aries-Framework-DotNet (Tomislav)
• Aries-StaticAgent-Python
• Aries-Toolbox
  • Added basic message admin
  • Working on a getting started video
• Aries-SDK-Java
• Aries-Framework-JavaScript / Aries-SDK-JavaScript
  • Started regular meetings: Framework JS Meetings
• Rich Schemas and W3C Verifiable Credentials (Brent & Ken)
• Ursa
  • 0.3.1 release in January
  • 0.3.2 released in February, includes key exchange methods (can replace libsodium)

RFC Progress

Other Business

• Q&A about the Aries Framework Go (Troy Ronda and team)
  
  • Introduction: https://talks.troyronda.com/2020/01/aries-framework-go/
    • (Use Chrome, Firefox, or Safari Technology Preview 100+ to view the slides).
  • Evernym's questions for discussion: https://hackmd.io/3lDKx8nZT8OV6pXQiwT4Tw?view
  • Supported RFCs: https://github.com/hyperledger/aries-framework-go/issues/920
  • Generic API into the framework that can be used for any binding (started with JS worker and WASM)
    • https://github.com/hyperledger/aries-framework-go/commit/461943a54d9324302a3bd85d7e9842008b6b669c
  • Framework is modular, so the DID component can be used separately from credentials.
  • Framework Go Meetings
    • Public standup 10AM Eastern
    • Weekly planning Tuesday 10:30 Eastern
  • #aries-go
• DID exchange versus DID connections
  • Considered part of DIF DIDComm.
  • But need to solve practical problems now, so not waiting for DIDComm group.

Future Topics

• Next Meeting (February 26)
  • Aries KMS design
    • Mike Lodder 's work on https://github.com/sovrin-foundation/aries-kms-rs 
    • Evernym's work
    • Define approved algorithms
    • Define plugin interface (aries-kms)
    • 3rd party libraries we could leverage:
      • Google Tink as an encryption library
  • CI / CD Aries shared libraries
• Other:
  
  • Formal verification (Sven Hammann)
  • Where should we document interoperability results (AIP 1.0)? A page in this wiki space?
  • Hubs vs Agents
    • https://www.hyperledger.org/blog/2019/07/23/rhythm-and-melody-how-hubs-and-agents-rock-together
  • Status and future of wallet query language
  • IOT best practices (Robert Mitwicki, Adam Burdett , Lohan Spies )
  • DID Resolution W3C and Sam's concerns: https://github.com/hyperledger/aries-rfcs/issues/130
  • Architecture of Aries Verifiable Credentials Proof Formats (Mike Lodder)

Action items

Call Recording