...

• Added VCX - a library built over libindy for Verifiable Credentials eXchange. API is EXPERIMENTAL.

• At the current moment mobile Mobile builds are not currently available - they should will be added in future releases.

• Added Logging API

• Added function indy_get_logger for plugins to give their logging to libindy.

• Added function indy_set_logger for client apps and wrappers to receive logs from libindy

• Integrated libindy logging into Slf4j for Java wrapper and into python logging facade.

• Updated API of Rust wrapper. Now there is no not three methods for each API call, there is only one that returns Future.

• Introduced multithreading for Wallet API and CRED_DEF generation.

• Bug fixes

Indy Node 1.6.79

• Fixes to improve stability.

• Output of validator-info changed and enhanced to meet growing need.

• Bug fixes

Indy Node 1.6.80

...

• Incubation status graduation.

• Complete the three items mentioned earlier in this document and apply for graduation.

• Continue to refine documentation.

• Consolidate documentation for onboarding contributors.

• Network stability of the first production deployment (Sovrin).

• Schema improvements!
  • We are currently working on enhanced schemas that will be compatible with the W3C Verifiable Credentials standards.   Our current credentials use schemas that are simple flat lists of untyped strings and this effort will allow complex data structures such as those available from  from schema.org .
  • New encoding methods (to convert properties to signature values) and presentation (proof) requests will be able to preserve privacy and security through zero-knowledge proofs (ZKP) while maintaining the cryptographic assurances that the credential values have not been modified. The new encoding methods will expand the number of credential values that can be used in predicate proofs, such as "greater than", "less-than-or-equal", etc.
  • Schema re-use between Verifiable Credential issuers will promote interoperability.
• Indy Catalyst
  • The OrgBook implemented as part of British Columbia's Verifiable Organization Network (VON) is being contributed to Hyperledger as Indy Catalyst. It provides a template for bootstrapping credential ecosystems built on Indy.

...

• Consume official builds of Hyperledger Ursa (the shared crypto-lib), as they are approved.

• Further improvements to automated testing.

• Audit ledger
  • As we move moved permission management to the config ledger, we identified the need for an audit ledger to make it easy to verify what permissions were in place with each write.
  • The audit ledger will also ensure deterministic catch-up between ledgers which resolves some BFT consensus corner cases.

• Research into Ledger 2.0

  • We are confident that Indy Node can scale to millions of users, but we have identified a number of problems with the existing implementation that will limit future scalability. Solutions are likely to require fundamental architectural changes.

  • Improve the stability and performance of View Change, Catch-up, and Replication.

  • Establish a cache for reads, such as observer nodes.

  • We are recruiting contributors from various organizations to assist in designing the future of the ledger and starting implementation.

• Broader OS support.

...

• Standardizing agent-to-agent protocol through an agent test suite.

• Tests associated with each major aspect of the protocol.

• Multiple interoperable agents in the community.

  • Mobile agents from the Sovrin Foundation and Evernym, and web agents from BC.gov, BYU, and StreetCred.

• Addition of a reference cloud agent.

...

Hyperledger Indy continues to see contributions from developers and organizations around the world. Our weekly Working Group call is normally attended by two dozen people representing nearly a dozen organizations. Not Please note the number of contributors and contributions listed in the Project Health Section section above.

POCs, Pilots, Projects

...