• Work updates
  • Payments in Aries
  • Hardware enclaves

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


(7AM Los Angeles, 10AM New York, 3PM London, 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 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 (Employer) <email>
  • Troy Ronda (SecureKey) <>
  • John "Jack" Callahan (Veridium) <>
  • Matt Raffel (Kiva) <>
  • Ken Ebert (Sovrin Foundation) <>
  • Stephen Curran (Cloud Compass/BC Gov) <>
  • Richard Esplin (Evernym) <>
  • Sam Curren (Sovrin Foundation) <>
  • Cam Parra (Kiva) <>
  • Steve McCown (Anonyome Labs) <>
  • Brent Zundel (Evernym) <>
  • Oskar van Deventer (TNO) <>

Welcome / Introductions


  • Aries Workshop/Connectathon December 3-5 in Provo, Utah - Dates Confirmed, Food Sponsors welcome!
  • Webinar on peer DIDs Nov 21 at 1 PM MST,
  • Proposal to renumber RFC 0289

Related Calls

  • Previous Aries Working Group calls
  • Identity Implementors Working Group call
    • Main place to get project updates, release status, and announcements.

Release Status and Work Updates

  • Aries Protocol Test Suite
    • Works, and ready for test contributions
  • Aries-KMS
    • Moving Indy Wallet crate into aries-ams / aries-kms (might change the repo name)
    • cam's rust aries-kms (just old code in repo right now, once I add more to my RFC I will focus my attention to adding code here)
    • SQLite as the default wallet.
    • aries-ams-sqlite is archived
    • Need to migrate Postgres wallet plugin from Indy to aries-ams-postgres
  • Verifiable Data Registry Interface library
    • Static Peer DIDs in aries-vdri as the default implementation
    • aries-vdri-peer is archived
    • Ken's POC
  • Other Core Libraries (pack / unpack)
  • Aries-CloudAgent-Python ( - Release 0.3.5 has been tagged and is on PyPi - caching/performance issues
  • Aries-Framework-Go (Troy)
    • Weekly planning notes (2019-11-05)
    • Wrapping up 0.1.0 release and starting on 0.1.1.
    • is now used as the prefix for message types (replaces did:sov:....)
    • Successful experimentation on the possibility of exposing additional bindings (C, WASM).
      • (We currently have Go and REST.)
    • You can play with the framework by running BDD tests (make bdd-test) or with the OpenAPI (swagger) interface (See README).
  • Aries-SDK-Ruby (Jack)
  • Aries-Framework-DotNet (Tomislav)
  • Aries-StaticAgent-Python
  • Aries-SDK-Python - Wrapper from JeromK and SBCA?
  • Aries-SDK-Java
  • Aries-SDK-JavaScript
    • DIF people interested in implementing a Java Script library that might share some of the functionality of the Aries SDK. We need to keep that in mind.
  • Rich Schemas and W3C Verifiable Credentials (Brent & Ken)
  • Migration from LibIndy
    • Closing PRs related to Indy wrappers with pointers to Aries language libraries
    • LibVCX support for some Aries protocols
  • Ursa 3.0 release in November
    • Updated BLS signature (multi-signatures, small-BLS)
    • Compilation optimization for specific hardware
    • Rest of predicates for Anoncreds 2.0 and delegatable credentials

RFC Progress

Other Business

  • Payments in Aries
    • Currently have the payment decorator defines how to request payment and prove that payment happened (same information as the W3C Web Payments standard).
      • Protocol gap in actually making the payment. Should be pluggable (application agnostic).
    • Payments are defined as part of credential issuance and presentation
    • Top level concept like KMS?
  • Using hardware enclaves (Mike L.)
    • Agent KMS Considerations: 
    • Steve M. has played a lot with the Apple enclave and can help.
    • Tension between security of a hardware enclave, and the portability promises of SSI.
      • Assumption is that any key put into an enclave cannot come out.
    • Ursa will provide an interface for interacting with an enclave (abstract the complexity).
      • Needs flexibility: mobile enclave, enterprise HSM

Future Topics

Action items


Call Recording

  File Modified
Multimedia File GMT20191106-150141_Community-_1652x1080.mp4 Call recording Nov 06, 2019 by Richard Esplin

  • No labels