2019-07-17-A Aries Working Group Call (US morning)

Summary:

Scheduled topics:

• Proposals for an Aries SDK

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

Date

17 Jul 2019 (7AM Los Angeles, 10AM New York, 3PM London, 17H 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 (organization) <email>
• Richard Esplin (Evernym) <richard.esplin@evernym.com>
• Ken Ebert (Sovrin Foundation) <ken@sovrin.org>
• Daniel Bluhm (Sovrin Foundation) <daniel.bluhm@sovrin.org>
• Adam Burdett  (Sovrin Foundation) <adam@sovrin.org>
• Alan Krassowski (Kiva) <alank@kiva.org>
• Stephen Curran <swcurran@cloudcompass.ca>
• Jakub Koci (Absa) <jakub.koci@gmail.com>
• Steve McCown (Anonyome Labs) <smccown@anonyome.com>

Welcome / Introductions

Announcements

• BC Gov is interested in collaborating with groups working on Mobile Agents that could be ready for a live implementation at the end of the summer. Contact Stephen Curran.
• BC Gov Keycloak/OpenID Connect Code With Us (bounty) awarded to MattrGlobal.
• Community project: Aries RFCs - process to move HIPES; RFCs that have been moved concepts / features / pull requests.
• Aries-* Repos Created: https://github.com/hyperledger?utf8=%E2%9C%93&q=aries-sdk&type=&language=
• Repo aries-cloudagent-python has been transferred!
• #aries-sdk on chat.hyperledger.org
• Repo aries-framework-go has been created

Summary of Prior Calls and Related Meetings

• Aries WG
• Indy
• Ursa

Release Status

• Aries-CloudAgent-Python (bc.gov) - Release 0.2.0, 0.2.1 tagged
  • Join us for: aries-cloudagent-python: Architectural Deep Dive - Tuesday July 23, 8AM Pacific - https://zoom.us/j/491220480
  • Likely will do it again at 3PM Pacific time as well.
• Aries-Framework-Go (Troy)
• Indy SDK
  
  • Late July:
    • GitLab migration alongside Jenkins (Foundation)
    • LibVCX without agency (Evernym)
    • Proof of possession
    • CLI tab completion
    • Migration of components to Aries ( Unable to render Jira issues macro, execution error. )
• Ursa
  • PRs for Anoncreds 2.0 are in progress
  • ZMix specification in progress

Work Updates

• Documentation improvements: Michael B and Stephen C
  • First draft in aries-cloudagent-python from 0 to coding in Aries
  • Need to review and prune out-of-date documentation (Alice / Faber treatment of pairwise DIDs is a key pain point)
• SDK 2.0 architecture / Indy-Aries split (Sergey)
  • http://jira.hyperledger.org/browse/IS-1285 

RFC Progress

Other Business

• Proposals for an Aries SDK
  • Key questions:
    • Should there be an Aries SDK, used by most language frameworks?
    • Should it be in Rust?
    • What parts of Indy should we take?
    • How should it change over time?
  • Discussion summary:
    • A Rust C-callable API is very useful for functions that are common across the various Agents.
    • A ledger resolver API below the C-callable API is really useful, but higher level functions for writing schema defs and cred defs should be implemented on top of those primitives by the language libraries
      • Need to recruit a second ledger implementation besides Indy to ensure that the resolver API is sufficiently generic.
    • https://docs.google.com/drawings/d/1d-aCRC_Nzyywv9nyQif9_vBGbeWhp69M4T5_8_yYtAI/edit?usp=sharing Indy SDK Migration Plan
      • Should payments belong in Aries (libnullpay?)
    • https://docs.google.com/drawings/d/1sUffkRPlufingeeRjjBniVt9Ek3CNih9lUqym8mUl4M/edit?usp=sharing Aries Architecture
    • https://hackmd.io/_BhJewTlSUqMGNDc4SvgNw?edit developing ideas around APIs

Future Topics

• Library threading models and synchronicity
  • Resolver and wallet might have different needs than other API functions.
• Payments in Aries
• wallet query language

Action items

Call Recording