Summary:
Scheduled topics:
- Aries SDK threading model
Note: This call is Recorded. Recordings posted at the bottom of the page.
Date
(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>
- Daniel Bluhm (Sovrin Foundation) <daniel.bluhm@sovrin.org>
- Adam Burdett (Sovrin Foundation) <adam@sovrin.org>
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.
- Community project: Aries RFCs - process to move HIPES; RFCs that have been moved concepts / features / pull requests.
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
- Recording 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.
- Link
- Aries-Framework-Go (Troy)
- Aries-SDK-Ruby (Jack)
- Moving from personal repo (rindy) soon.
- Indy SDK
- Late July:
- GitLab migration alongside Jenkins (Foundation)
- LibVCX without agency (Evernym)
- Proof of possession
- CLI tab completion
- Migration of components to Aries (Error rendering macro 'jira' : null)
- Late July:
- 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
- https://docs.google.com/document/d/1MYMi4NkixfoIJeC79WBOfX_QA3_9rG-iK3lZa86vIR0/edit#heading=h.z1u0dzf62loi POA and discussion
- https://docs.google.com/drawings/d/1d-aCRC_Nzyywv9nyQif9_vBGbeWhp69M4T5_8_yYtAI/edit?usp=sharing Indy SDK Migration box diagram
- https://docs.google.com/drawings/d/1sUffkRPlufingeeRjjBniVt9Ek3CNih9lUqym8mUl4M/edit?usp=sharing Aries Architecture
- https://hackmd.io/_BhJewTlSUqMGNDc4SvgNw?edit developing ideas around APIs
RFC Progress
Other Business
- LibAries: library threading models and synchronicity
- Resolver and wallet might have different needs than other API functions.
Current design in Indy was implemented as part of IS-660
HIPE: https://github.com/hyperledger/indy-hipe/tree/master/text/0012-concurrency-improvement
- Mike's concerns: https://docs.google.com/document/d/1-oabbR7n4MsLsU-MGfrwbjJvB1V4nMroW_oh2BvYVXc/edit
- VON Anchor takes a significantly different approach:
- https://von-anchor.readthedocs.io/en/latest/von_anchor/anchors.html#revregbuilder
- "Neither multithreading nor green-threading primitives pass through the wrapper/shared-library barrier; subprocessing must occur early in the game before libindy sets up its dispatcher, as it operates in a separate thread(? message loop? it's been a while) that does not replicate over a fork (this is unix architecture not indy).
"In von_anchor, An external rev reg builder process uses file system semaphores as IPC, increases rev reg size as it scales up, and anticipates one rev reg in the future so that the issuer process never waits for a rev reg build."
- Other LibAries architecture suggestions
Future Topics
- Payments in Aries
- wallet query language
- IOT best practices (Robert Mitwicki, Adam Burdett , Lohan Spies )
Action items
Call Recording