2022 Q1 Hyperledger Aries
Project
Hyperledger Aries
Project Health
Hyperledger Aries continues to grow stronger in terms of activity by contributors and in the interest from those using Aries in various use cases. It has an extremely diverse and global community. In addition to the steady progress made in most of the sub-projects, a number of significant events occurred in the project including:
- Progress on Aries Framework JavaScript in implementing Aries Interop v2.0 (AIP 2.0), and its capability as the foundation of an Bifold, an Aries React Native mobile wallet.
- An "Aries Mobile Summit" was held and significant progress as been made in open source mobile wallet delivery velocity. There are now Aries React Native mobile wallets being deployed by various groups into the App Stores.
- A new repo "aries-mediator-service" has been created that can be used by mobile Wallet providers as an Aries Mediator to enable communication between the mobile wallet and all other Aries agent. The repo is built on the latest ACA-Py release configured to act as an Aries mediator.
- Continued progress on the Aries VCX framework toward AIP 2.0, a Rust-based framework suitable for use in a number of server-side and mobile use cases.
- Continued evolution of the open source implementation of the Aries Interop Profile RFCs by the FIndy (Finland) project.
- The Aries Agent Test Harness, continues to be a focal point for the community in verifying interoperability, with ongoing adjustments based on test results as the various frameworks evolve.
- A new Aries Mobile Test Harness was added for automating the testing of Aries Mobile Wallets.
There continues to be lots of delivered, verified code, let alone the increases in participation and use of Aries.
This quarter has also seen an increased focus on the use of the verifiable credentials mechanism found in Hyperledger Indy–AnonCreds as a "long term" approach versus the plan this time last year of moving to the W3C VC 1.x data model. After a lot of effort in moving to the W3C VC data model, practical limitations have meant that for those wanting to deploy solutions today, AnonCreds has been found by many to be the better approach. In response to that, a number in the Aries community have started the process of making AnonCreds not just open source, but also an open standard, and to remove a perception by some of it being proprietary. We expect that a v1.0 specification will be produced fairly quickly that (more or less) documents what we have today, and in parallel or soon after, we'll work on an AnonCreds v2.0 that retains all the capabilities of AnonCreds, but based on "newer" approaches, such as replacing CL-Signatures with BBS+ Signatures. Note that although AnonCreds is currently a part of Hyperledger Indy, AnonCreds itself is more relevant at the higher levels of the Trust over IP stack, and thus is more of a concern of Aries contributors and those using the Aries in building and deploying real world applicatio