Page Comparison

Summary:

...

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.

...

• 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>
• John Callahan (Veridium) <jcallahan@veridiumid.com>
• Nicholas Rempel (BC Gov) <nick@lucent.is>

Welcome / Introductions

Announcements

...

• 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 (https://github.com/johncallahan/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 (

      Jira Legacy
      server Hyperledger JIRA serverId 6326cb0b-65b2-38fd-a82c-67a89277103b key IS-1285

      )
• Ursa
  • PRs for Anoncreds 2.0 are in progress
  • ZMix specification in progress

...

• 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

  • Uncompleted work documented as IS-898, IS-943, IS-1135

  • 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
  • Daniel Bluhm : https://hackmd.io/@gjPgYQjMT3azdpSAFgo5PA/HyjVdhVGr

Future Topics

• Hubs vs Agents
• Payments in Aries
• wallet query language
• IOT best practices (Robert Mitwicki, Adam Burdett , Lohan Spies )

...