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.

...

• Richard Esplin (Evernym) <richard.esplin@evernym.com>
• Brent Zundel (Evernym) <brentzundel@evernym.com>
• Ken Ebert (Sovrin Foundation) <ken@sovrin.org>
• Sam Smith (ProSapien) <sam@samuelsmith.org>
• Matt Raffel (Kiva) <mattr@kiva.org>
• John Callahan (Veridium) <jcallahan@veridiumid.com>
• Daniel Bluhm (Sovrin Foundation) <daniel.bluhm@sovrin.org>
• Kumaravel (Ford) <nkumara2@ford.com>
• Steve McCown (Anonyome Labs) <smccown@anonyome.com>

Welcome / Introductions

...

• Moving tickets from Indy-SDK to Aries
  • Closing tickets related to the Indy SDK wrappers, LibVCX, and Wallet
  • Closing tickets in Indy Agent
• Next step on Aries Core Libraries
  • Proposal review of interface boundaries
    • Ken Ebert, Brent Zundel 
       
      • Daniel's feedback: concerns about splitting "Secure Storage" with "Key Storage".
        • "Key Storage" is a confusing term due to incorrect analogies to previous key storage solutions.
        • IIW discussions about Aries storage and hardware secure storage.
        • Previous work in Aries RFC 50.

          • https://github.com/hyperledger/aries-rfcs/tree/master/concepts/0050-wallets#enclave-wrapping

      • RFCs submitted
        • https://github.com/hyperledger/aries-rfcs/pull/249
        • https://github.com/hyperledger/aries-rfcs/pull/250
      • Ledger Resolver → Data Registry Interface
  • Evernym thinks the next step is to move the Indy Wallet
    • Indy SDK Epic: 

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

  • Kiva is also working on a wallet implementation
    • https://github.com/hyperledger/aries-wallet
  • See discussion in :
    • 2019-09-25-A Aries Working Group Call (US morning)
    • 2019-10-07 Indy Contributors Call
  • Sergey prepared a POC as a sub-directory in Indy SDK
    • https://github.com/hyperledger/indy-sdk/pull/1927
  • Parallel efforts?
    • Stub out other Aries Core repositories: 

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

      • Give 1 week for feedback, then create the repositories.
    • Work on the resolver interface?
      • Daniel has a Peer DID resolver we could quickly move to Rust and Aries Core
        •  

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

        • https://github.com/dhh1128/pypeerdid

Future Topics

• Next call
  • Architecture discussions at IIW (Daniel)
• Other:
  • Using hardware enclaves
  • Hubs vs Agents
  • Payments in Aries
  • wallet query language
  • IOT best practices (Robert Mitwicki, Adam Burdett , Lohan Spies )
  • DID Resolution W3C and Sam's concerns: https://github.com/hyperledger/aries-rfcs/issues/130

Action items

•   Richard: Create repos specified in Aries 3 

Call Recording

...