Distributed Ledger
Client Tool
Shared Components

Project Health

The work on the Indy DLT (indy-node and indy-plenum) slowed this quarter to a focus only on the CI/CD capabilities and upgrading to Ubuntu 20.04; no new functionality was added. The transition of the CI/CD from an older, undocumented Jenkins/manual process to a GHA-based CI/CD pipeline has been slow. The work on the CI/CD and OS Upgrade has prevented any progress on new features – blocking most notably the upgrade to the new "did:indy" DID Method. With the change of the W3C DID Specification to "Proposed Standard" it is appropriate that work start (and finish) soon.  In addition to the CI/CD work, the team is add some tooling to make it much easier to get started doing development on the project. The goal is to promote the tribal knowledge about the projects into easily followed steps to deploy for development, make changes, debug and run tests. To be clear, these changes are focused on making it easier to make changes to the DLT code itself.

On a positive note, the interest in deploying instances of Indy continues, with lots of questions on Hyperledger Chat from people learning to run their own instances. Further, there are no significant bugs that are pending action, and no demand for new functionality from the user base. Indy "just works". For example, the Sovrin networks (MainNet, StagingNet and BuilderNet, operated by more than 50 organizations) is celebrating its 5th birthday this month, and coming up to 2 years without an outage. Even demand for the new "did:indy" DID Method is moderate at best. 

Work has proceeded on the replacements for Indy SDK – indy-vdr and indy-shared-rs, with a tagged release of both projects.  

Per the Indy Activity Dashboard (2021-04 to 2021-06), there were just 34 commits from 7 contributors. which is a significant drop from the last quarter.

Questions/Issues for the TSC

Issues from previous reports:

Build Pipelines

Update: Work was not completed last quarter as expected on this task. We'll see how it goes this quarter...

Diversity of Contributor Community

Update: Contributor community diversity remains a top of mind issue with the maintainers.  We are considering a "Contributor Campaign" in conjunction with Hyperledger Staff to build attention to both Indy and the new "did:indy" DID Method. The need is not for "drive-by" devs doing their first commit, but rather those that are building their businesses on Indy and should be contributing to the evolution of the project. To a degree, the project is a victim of its quality and completeness, as mentioned in the "Project Health" section.


  • indy-sdk 1.16.0
  • indy-shared-rs 0.3.0
  • indy-vdr 0.3.0

Overall Activity in the Past Quarter

In the past quarter, ledger code development has slowed as we focus on code management – upgrading the Indy Node and Plenum CI/CD pipeline and upgrading Indy Node to run on Ubuntu 20.04.  

There was no progress on the new Indy DID Method. The work left at the end of the last quarter remains: wrapping up the specification and defining the backlog of work for indy-node, indy-sdk and indy-vdr. With the CI/CD work blocking progress on indy-node, it's very difficult to convince contributors in the community to work on the DID Method if it is so hard to test and impossible to release.

Current Plans

The push will be to complete the new CI/CD Indy Node and Plenum pipelines, the Ubuntu 20.04 upgrade, and tools to make it easier to do Indy Node development. Until that is completed, there will not be changes to the functionality.

Maintainer Diversity

The bi-weekly Indy Contributors call continues to be the medium by which maintainers coordinate work, discuss critical issues to the Indy codebase, and agree on HIPEs. Topics and attendance has dropped recently, somewhat due to holidays, but also due to the lack of topics other than "how is the CI/CD work coming along?"

Contributor Diversity

See the comments in the "Issues" section (above). With work limited to CI/CD work on the Indy DLT side, there is little else to be done until that is complete.

Additional Information

(Note – no change)

Reviewed by