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:
- The community is stress testing the Aries frameworks and some issues have been reported, and addressed, as you will see. The addition of an open source Aries Load Generator tool (which I think will be moving to Hyperledger) provides an amazing tool for exploring these issues. The combination of the load test generator and some focused work in Aries Askar both addressed the intermittent problems and boosted Askar performance by 11% in the process. Very cool!
- The load test generator also enables an easy way to do a direct comparison of the old IndySDK and the new Aries Askar and shared components. As seen by these results, Askar is far more stable than the Indy SDK (doesn't slow over time) and is about twice as fast as the Indy SDK – the differences are stark! See the follow test run results for ACA-Py 0.7.3+IndySDK and ACA-Py 0.7.4+Askar
- Both the Aries Agent Test Harness and the Aries Mobile Test Harness continue to evolve with more contributions provided this past quarter in making them work together and in expanding the tests being run.
- Attendance at the regular communities meetings is up, with 35+ people at recent Aries Cloud Agent Python User Group meeting.
- Work has begun in integrating DIDComm V2 into the Aries frameworks – some design and some implementation work. We think this will progress slowly as interest is clearly in what people can do today but these proof-of-concepts demonstrate that Aries frameworks are well designed to enable such evolutions.
There continues to be lots of delivered, verified code, let alone the increases in participation and use of Aries.
As mentioned in the last report, the focus on making AnonCreds a standard vs. a de facto standard is gaining momentum. The standard drafting process is going will, producing this work in progress spec, with a strong contingent working regularly to evolve it.
The Indy/Aries stack continues to be the global leader in SSI/verifiable data solutions.
Questions/Issues for the TSC
The following Aries releases occurred in the last quarter:
- Aries Cloud Agent Python Release 0.7.4-rc0, 0.7.4-rc1
- Aries Askar 0.2.5
- Aries VCX Releases 0.28.0 through 0.45.0
Interoperability status can be seen here: https://aries-interop.info.
Overall Activity in the Past Quarter
Per the Aries Activity Dashboard for the first quarter of 2022 (Jan-March), Aries codebases had 1.37k commits (up significantly) from 60 contributors (up slightly).
Community participation is extremely active in Discord channels, community calls, and repo PR reviews and issues. Email lists are less frequently used.
Coordination with the DIF DIDComm working group is healthy, with regular reports being shared.
Project work in main repos is healthy and active. A potential concern raised last quarter was the lack of activity in the Aries Framework .NET repository, but even that had some activity this quarter, with a couple of interesting PRs completed and merged.
- Based on feedback from the community – a lot of effort has gone into stress testing Aries – especially Aries Cloud Agent Python, with good results.
- A split focus between deploying more production solutions and moving the Aries frameworks forward to use new protocols – AIP 2.0 and DIDComm v2.
- A focus on standardizing AnonCreds to provide increased comfort of the solid foundation in Aries and use beyond Aries.
In addition to the code contribution statistics (above), here are a few indicators of our current diversity:
- We hold community calls each Wednesday at 7am Pacific to cover (the mostly) US and European contributors.
- Call attendance for each is typically in the 15-20 range, up somewhat lately.
- Most organizations have only one attendee; it is rare for more than three to attend from the same organization.
- Cross codebase interoperability efforts indicate cross-organization cooperation.