Hyperledger Ursa: adding generic wrappers and implementation for password hashing, encryption and other use cases
Trying to move crypto code to Ursa to make it reusable and facilitate interface boundaries between Indy and Aries
Building blocks for ZKLang being put in place to describe what proof traits you want in a system, implementation going into ZMix
Ursa call is every other week at 8 am Mountain. See #ursa on Rocket.Chat, mailing list, and github.
RFC Standards work
Transition of a large number of indy-hipe docs into aries-rfcs repository. Working on ratifying RFCs that already have active implementations
Cloud Agent Python - continuing work and PRs to support the protocol and demos that help get things up and running quickly
Tooling & Testing - New tool on an electron-based app for connecting to and interacting with agents in direct ways (for developers and admins). The test suite coverage for proving compatibility in advance of the next IIW is very active.
Semantics WG - Rich Schemas work is active with work on defining the Resolver Interface in the Aries SDK and node code in Indy. End-to-end context object is nearly ready, and looking for help to do the next four or five objects in parallel.
Work going on about OCDA and how to decorate and annotate data and describe all fields and interactions around those semantics.
Ledger News - indy-node 1.10 has come out with a "late July" bugfix release coming very soon. Public access mode with the auth_rules has some good fixes for being able to provide payments at write-time. This allows 0-signature transaction configurations.
Tab completion in the CLI is improved
Dependency of libvcx in the cloud agent is ready for those who want to experiment
Migration to GitLab is underway, we expect demos next week. Code will continue to reside in GitHub. Community may contribute runners.
Payment Interfaces - proof of posession of payment addresses added. Scripts for helping mint and test offline signing and wallet creation are starting to show up.
Governance Frameworks and Trust Architecture
Four active task forces in the Sovrin group: Guardianship, Domain specific governance, SSI in IoT, Business models of SSI
Verifiable Credentials has reached CR2 (a JWT fix was made). After 28 day review period, there will be a vote to move to a proposed recommendation followed by a vote to become an approved specification
The credentials community group (CCG) has been incubating the DID specification and it is now readying a charter to become a DID Working Group to produce a standards-track specification. There is a weekly call on Thursday afternoons to move that spec forward (under the CCG).