2023 Q3 Hyperledger Indy

Created by Stephen Curran and the Hyperledger Indy Maintainers.


Distributed Ledger

Client Tools


Project Health

The project had less activity this quarter than previously, with fewer updates from (most) of the same organizations. The community had an Indy Ecosystem Summit on June 29, 2023, with over 50 participants talking about what they are doing with Indy. A follow up meeting to be held on September 7, 2023 is planned to convert the interest expressed in the first meeting into action, ideally based on the Indy Roadmap.

Per the Indy Quarterly Activity Dashboard, there were 97 commits (the same as last quarter) from 24 contributors (almost double last quarter).

NOTE: As of 2023.08.02 only some of the Indy repositories are visible on LFX Insights. The additional repositories are being added.

Questions/Issues for the TOC


Issues from previous reports

Diversity of Contributor Community

See the updated type of information in the appropriate section of this report.


  • indy-vdr - - v0.4.0-dev.13 to v0.4.0-dev.16
  • indy-node-container - v1.2.5
  • indy-shared-rs - v0.3.3

Overall Activity in the Past Quarter

Activity was focused on the so-called Shared Components (indy-vdr, indy-shared-rs and aries-askar) and the transition away from the Indy SDK. The maintainer community has discussed the formal deprecation of the Indy SDK and the Aries maintainers have been busy making the Shared Components the default in Aries, in preparation for the deprecation announcement.

The archiving of the Hyperledger Ursa project triggered a refresh of the underlying CL-Signatures code base (now anoncreds-clsignatures-rs), and a number of improvements along with a couple of bug fixes. The release as part of indy-shared-rs was the first upgrade to CL Signatures in several years, and included a speed up of 50% in creating a revocation registry, and 25% in the other revocation operations (issuance and revocation).

Little changed with the Indy Node implementation beyond further deployments of the software and confirmation of its stability. However, no migrations of existing networks to the Ubuntu 20.04 release have been performed. Testing, experimenting and documenting that process continues.

Current Plans

The second Indy Ecosystem Summit in September will be a key event as we look to see indications of contributions to the Indy code base and progress on the deployment of the new network releases.

The Aries Frameworks are rapidly moving to indy-vdr and aries-askar and away from indy-sdk, which will enable its deprecation. The high priority work on Hyperledger AnonCreds implementation will also drive that effort.

Progress is being made on enabling the “did:indy” DID Method in indy-vdr. Its use requires the upgrade of Indy networks to use the new Ubuntu 20.04-based releases.

Maintainer Diversity

There are 35 individuals on 22 Indy GitHub Teams representing at least 16 organizations.

That said, cleanup of the teams are needed as some of the individuals are no longer active in the community.

Contributor Diversity

See the Indy Quarterly Activity Dashboard for information about contributors this quarter. The 18 individual contributors came from at least 9 different organizations.

Additional Information