Page tree
Skip to end of metadata
Go to start of metadata

Project

Hyperledger Aries

Project Health

The Aries Project transitioned to "Active" in the last quarter, reflecting the project's current community state. Lots of active discussion, activity and growth internally, and a lot of external interest in the project and artifacts from the deliverables.

Questions/Issues for the TSC

A discussion is happening email with Brian Behlendorfand leaders in the Ursa community about how to get an audit report on Ursa and it's use in Aries and Indy. That is progressing, but it's a tricky subject, so any help from the TSC on moving the effort forward would be appreciated.

Releases

The following releases occurred in the last quarter:

  • Aries Cloud Agent Python Release 0.6.0
  • Aries Framework Go Release 0.1.6
  • Aries Framework JavaScript – multiple "unstable" releases that are leading up to the 0.0.1 release
  • Aries Askar 0.1.3
  • Aries VCX Releases 0.16.0, 0.17.0, 0.17.1

We expect that we'll get to designated "1.0.0" releases in the next few months for some of the sub-projects.

The Aries Agent Test Harness continued to evolve with the launch of a status page about the state of Aries interoperability – https://aries-interop.info. As well, a mechanism was added to allow for the testing of mobile agents using the Aries Agent Test Harness, so that interop between frameworks as issuers and verifiers and mobile agents as holders.


Overall Activity in the Past Quarter

Per the Aries Activity Dashboard for the first quarter of 2021, Aries codebases had 696 commits in 549 PRs from 53 contributors.

Community participation is extremely active in rocketchat 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.

Current Plans

  • AIP 2.0 is very (very!) close to completion, with key additions to make Aries ledger agnostic and to add the use of new verifiable credential formats in W3C Standard format.
    • Lots of work is proceeding as the discussions about AIP 2.0 continue.
  • Work is active to extend Aries beyond support just Indy ledgers and Indy AnonCred verifiable credentials to supporting other ledgers and other verifiable credential formats – most notably BBS+ signatures, supporting ZKPs and selective disclosure.
    • AF-Go has working code
    • ACA-Py has works in progress (as of the end of 2021-Q1) on multi-ledger resolution and verifiable credential formats.
  • The Aries Mobile Agent React Native (aka Bifold) built on Aries Framework JavaScript has gained some traction and could be the open source wallet a larger community rallied behind.
  • Interoperability testing continues to be a key focus.

Maintainer Diversity

Aries is a multi-codebase effort, and each codebase has its own set of maintainers. The diversity of maintainers closely matches contributors, with notes below.  Cross framework collaboration is increasing. For example, work is happening on interop testing capabilities across the Python, Go, .NET and JavaScript frameworks.

As interest in verifiable credentials has increased with COVID-19 use cases (proof of testing, proof of immunization and mobile medical workforces), interest and attendance has increased, as have deployments of Aries-based implementations.

Contributor Diversity

In addition to the code contribution statistics (above), here are a few indicators of our current diversity:

  • We hold two community calls on Wednesdays: weekly at noon Pacific to cover US and Pacific contributors, and biweekly at 7am Pacific to cover US and European contributors.
  • Call attendance for each is typically in the 15-20 range.
  • Most organizations have only one attendee; it is rare for more than 3 to attend from the same organization.
  • Cross codebase interoperability efforts indicate cross-organization cooperation.

Additional Information

Related activity to Aries is occurring in DIF (Decentralized Identity Foundation), the Trust over IP Foundation, and especially in their Good Health Pass initiative, and in Linux Foundation Public Health (LFPH).

Reviewed by