Page tree
Skip to end of metadata
Go to start of metadata


  • Work updates
  • Architecture of Aries Verifiable Credentials Proof Formats (Mike Lodder)
  • Ledgerless approach to VC - Robert Mitwicki - canceled due to lack of time,
  • Open Discussion (as time permits)

Note: This call was recorded and the recording and chat transcript are at the bottom of the page.


(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 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>
  • Robert Mitwicki <>
  • Stephen Curran (Cloud Compass Computing Inc.) <>
  • Sam Curren ( <>
  • Phil Feairheller (Scoir, Inc) <>
  • Mike Lodder <>
  • Steve McCown (Anonyome Labs) <>
  • Alexander Jonsson (

Welcome / Introductions


  • IIW April - virtual event
  • KERI API conference next week 8-9th of Dec

Related Calls

  • Previous Aries Working Group B calls
  • DIF DIDComm WG Call: Rolling Agenda.
  • Indy contributors call
  • 2020-12-3 Identity Implementers WG Call (9am MT / 4pm UTC), presentation:  Nicole Khor (Anonyome Labs, University of Queensland) will discuss her ongoing research into integrating SSI technologies with existing browser-based authentication protocols, such as WebAuthn.  

Release Status and Work Updates

  • Aries Protocol Test Suite
  • Aries Agent Test Harness
  • Aries Shared:
  • Aries-CloudAgent-Python (
    • Release 0.5.6 released
      • Getting close on an ACA-Py branch that used Aries Shared
      • PR merged adding DID Exchange protocols
  • Aries-Framework-Go (Troy) #aries-go
    • 2020-11-03 Meeting Notes
    • BBS+ Verifiable Credentials implemented using pure Go. Example.
      • Next tasks: interop testing against Mattr implementation and selective disclosure capabilities.
    • Working on adding remote encrypted storage capability - with a default implementation of DIF Secure Data Storage - Encrypted Data Vaults.
      • Encrypted Data Vault (EDV) from DIF SDS spec format has been implemented. Works as an encryption wrapper to underlying storage providers.
      • DIF EDV/SDS REST client is in progress. Docker image will support configuring EDV endpoint as wallet storage.
    • Remote KMS support is in progress. Docker image will support configuring remote KMS. 
    • Created repo to handle pluggable go framework components such as Indy VDR:
      • MySQL and CouchDB components moved to ext repo.
      • New contributions of MongoDB and RabbitMQ support to the ext repo.
  • Aries-SDK-Ruby (Jack)
  • Aries-Framework-DotNet (Tomislav)
  • Aries-Toolbox
    • Connections Update Complete
    • ACA-Py Toolbox Plugin updated to support ACA-Py 5.3
    • Dependency Updates
    • Converted to a web application by HCF - repo 
  • Aries-SDK-Java
  • Aries-Framework-JavaScript
  • Rich Schemas and W3C Verifiable Credentials (Brent & Ken)
  • Aries-MobileAgent-Xamarin (Aries MAX)
  • Pending contributions from GlobalID:
    • indy-sdk PR for IOS
    • indy-sdk-android
    • Aries Framework IOS (Swift)
    • Aries Framework Android (Kotlin)
  • Ursa


RFC Progress

Other Business

Future Topics

Action items


Call Recording

  • No labels

1 Comment

  1. > Where should we document interoperability results (AIP 1.0)? A page in this wiki space?

    The Trust Over IP Technical Stack Working Group has an Interoperability Task Force where we have been doing interop testing and recording results. Each vendor publishes their own results. Our initial interoperability profile is focused on AIP 1.0.

    Our announcement is here:

    More information is here (work-in-progress):