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.

...

• Aries-CloudAgent-Python (bc.gov) - Release 0.3.2 has been tagged and is on PyPi
  • Support for RFC 0036 and RFC 0037 Credential Exchange protocols, 0.1 version of those protocols deprecated
  • Working on next release, particularly on revocation support.
• Aries-Framework-Go (Troy)
  • First milestone: Framework Go v0.1.0
  • Weekly planning notes
• Aries-SDK-Ruby (Jack)
  • Released as a Gem (0.0.3) due to Rails 6 issues
  • Developed docker image with Rails 6 (Ruby 2.5.1) with Indy-SDK to test Aries-SDK-Ruby via Dokku deployment
  • Needed for exploring concurrency and compatibility issues with Sidekiq, Resque, SuckerPunch, etc.
• Aries-Framework-DotNet (Tomislav)
  • Moved from StreetCred to Aries: https://github.com/hyperledger/aries-framework-dotnet
• Aries-StaticAgent-Python - Release 0.4.0
  • Move from Pysodium → PyNacl
  • Improved module interface and routing.
• Aries-SDK-Python - Wrapper from JeromK and SBCA?
• Aries-SDK-Java
  • People are expressing interest in Rocket Chat, but no one has started contributing code yet. Could start by moving the Indy SDK wrapper to Aries.Aries-SDK subchannel / discussion aries-sdk-java
• Aries-SDK-JavaScript
  • Need a reviewer for the pull request moving code from Indy-SDK to AriesPeople are collaborating in the repo.
• Indy
• Ursa
  • Working on release of 0.2.0 (September / October)
    • ZKP  / ZKLang improvements
    • Debian packages
    • Refactor internal plumbing for anoncreds 2.0, shouldn't impact external interfaces
    • Refactor multi-signature BLS in addition to aggregated signature
  • Sovrin Foundation is looking to build a Indy specific Ursa,  with ZKPs. Other Aries clients would build a different Ursa.

...

• Rich Schemas and W3C Verifiable Credentials (Ken)
  • Working on context object in Node. PR for Indy-Node is almost ready for review.
  • Making progress on the new schema object.
  • In order to do the review, need new Indy HIPEs: each new object, the new flow for creating credentials, creation of presentation request and presentation, compatibility with the old credential format
• 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
  • Aries Presentations
  • https://hackmd.io/@gjPgYQjMT3azdpSAFgo5PA/HyjVdhVGr Daniel B's proposal for separating wallet and crypto
  • https://docs.google.com/document/d/18kHgTsHkSIIW9cakbampv8rxKxNchWycthHnXGyxkls/edit# Daniel H's analysis of challenges and approaches
• Architecture of Aries Verifiable Credentials Proof Formats
  • Boundary between the claim type and the signature type
  • Where should it live? Anoncreds (ZKPs), JWTs, Link Data Signatures
    • FYI: Go Framework Verifiable Credential package: https://github.com/hyperledger/aries-framework-go/tree/master/pkg/doc/verifiable, with the next work item being JWT proof format: https://github.com/hyperledger/aries-framework-go/issues/173
  • Aries Anoncreds Framework

RFC Progress

Other Business

• Aries shared libraries export their API as C-callable, but the implementation language doesn't matter: C, Rust, Go
• DIDDoc parser in Rust:

  • https://crates.io/crates/did_doc

  • https://github.com/dhuseby/did
• What is the next step we can take:
  • Order Richard's proposal for order of work
    • Move Indy-SDK into Aries-Core (October release)
    • Split out wallet into Aries-Wallet (November release)
    • Define the resolver interface (November effort)
    • Split out resolver into Indy-Resolver (December release)
  • Questions
    • Iterative approach: do something that we can improve on.
      • Start with the needs of the agents (Aries-Cloud-Agent) and build the Aries core architecture from that.
    • Maintain Indy-SDK alongside Aries-Core / Aries-Wallet / Aries-Resolver?
    • Who will be the maintainers of the new libraries? Do we want cross-organization PR reviews?
    • Best way to maintain history, and  make the reorg transparent (
      • History continues public in Indy-SDK, so might be better to start clean in Aries
      • concerns with old DCO process
      ).
      • : can use Mike Lodder's approach he used for moving indy-crypto to ursa
    • What to do with the Indy CLI?
    • CI / CD in Jenkins or GitLab?
  • Daniel's proposal for order of work
    • Split out Indy wallet into Aries-Wallet
    • Define the resolver interface and create the resolver libraries (indy and peer)
      • The peer DID resolver isn't dependent on other libraries https://github.com/dhh1128/pypeerdid
    • Wait on Aries-Core
• Architecture of Aries core library
  • What is our fastest path to a library that framework implementors could consider using?
  • Daniel's analysis of Aries API Surfaces https://docs.google.com/presentation/d/1ODtHCeB6x7yVGfhyJHFUKn0f070sqZXhff1C8M7jfTY/edit?ts=5d658905#slide=id.p
  • Background in previous meetings: July 31, August 14
  • Progress of Ken's POC
  • Key questions: https://docs.google.com/document/d/1w_n8EztyLbNlRa3FfuuN8YXKUISYRfM5p_6ijIig6jk/edit#

...

• Next call
• Other:
  • 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

•  Schedule a deep dive into Aries / Indy architecture (Ken / Richard)

...