Versions Compared

Old Version 2

changes.mady.by.user Lynn Bendixsen

Saved on

compared with

New Version Current

changes.mady.by.user Lynn Bendixsen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The contributors to Hyperledger Indy spent this past quarter working on three these key initiatives:

  1. Addressing ledger stability concerns raised during testing and during production outages of client networks.

  2. Adding Hardening the ledger and adding ledger monitoring to continue preparation for widespread usage.

  3. Maturing agent standards to build ecosystem compatibility.

  4. Developing and develop reference agents so that they are usable by new participants in the ecosystem.

  5. Documentation improvements to enhance ease of use and encourage new contributors.

These three efforts have yielded significant results.

  1. Ledger monitoring scripts have been implemented and real time notifications are in place and operational on some ledgers.

  2. Work has accelerated significantly on agent standardization. Multiple implementations of agents are nearing the ability to connect to each other thanks to efforts from members of the community from many different organizations. An Agent “Connect-a-thon” is scheduled for this month (February) to demonstrate the ability to connect different agents, resolve any remaining issues, and determine next steps as a community. See Agent Connectathon Agenda .

  3. Superb effort has been put in to consolidate the Hyperledger-Indy documentation for ease of use. See hyperledger-indy.readthedocs.io and doc.sovrin.org .

Other important outcomes this quarter:

...

  1. Indy’s codebase has

...

  1. surpassed 17,000

...

  1.  commits from 143 unique

...

The Indy team continues to work with other Hyperledger teams to transition from the indy-crypto component to Hyperledger Ursa.

...

An audit ledger was added.

...

Graduation from incubation status only requires 3 more action items:

  1.  contributors.

Issues

Our top issues from last quarter continue to be our central concerns, but we have made some useful progress.

  • An Indy use cases document (a community effort just started with this doc)

  • Confirmation that indy projects implement perfect forward secrecy

  • Automated code coverage collection (This is very difficult considering our tech stack. There is active development on this front and it will hopefully be implemented soon)

Some new and exciting things that are in the works:

Schema improvements! In the Schemas area we are currently working on enhanced schemas that will be compatible with the W3C Verifiable Credentials standards. This will allow complex data structures such as those defined in schemas like those available from schema.org to be used with Hyperledger Indy Verifiable Credentials. This will be a substantial improvement over our current credentials, which use schemas that are simple flat lists of untyped strings. 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.

...

Ensure quality releases for downstream users

Improvements over last quarter have been made for this issue. Releases and deployment have been consistent and timely as improvements to the ledger have been tested and delivered.

...

  • The Indy team will continue to focus on providing releases that can be immediately deployed downstream.

  • The team is being more deliberate about preserving backwards compatibility. (More work is still needed here)

  • The “ledger 2.0” design project is under way and includes representatives from many organizations within our community.

Inconsistent documentation

...

...

  • Work with Hyperledger to get analytics about web sites, and Rocket Chat usage.

  • Begin measuring usage of the Sovrin forums: new contributors, questions asked, and questions answered

  • Measure Indy tags on Stack Overflow.

Build Issues

Progress made:

...

  • 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

...

  • Additional hotfixes for improved stability.

January 2019:   

No new Releasesreleases

Overall Activity in the Past Quarter

General

  • Graduation from incubation status only requires 3 more action items:

    • An Indy use cases document (a community effort just started with  this doc  )

    • Confirmation that indy projects implement perfect forward secrecy

    • Automated code coverage collection

      • This is very difficult considering our tech stack. There is active development on this front and it will hopefully be implemented soon

    See the notes above regarding progress made on key issues

      • .

Indy Node

  • Significant focus on performance and stability. Several stability fixes have been implemented and ledgers are running better than ever.

  • Continued research into a future ledger architecture.

Indy SDK

  • Release of experimental LibVCX.

  • Started work to support HIPEs defining Agent to Agent compatibility.
  • The Indy team continues to work with other Hyperledger teams to transition from the indy-crypto component to Hyperledger Ursa.
Indy Agent

  • Many HIPEs moved to accepted status.

  • Significant iterations on and discussion surrounding several HIPEs.

  • Increased collaboration with new contributors in the community.

Current Plans

Additional organizations are making ongoing contributions. This is shown by the shared Running Roadmap for Hyperledger Indy.

...

  • 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 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.
Indy Node

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

  • Further improvements to automated testing.

  • Audit ledger
    • As we 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.

Indy SDK

  • Broader OS support.

  • The SDK is being updated to comply with HIPEs documenting interoperability standards which we call Agent to Agent compatibility.

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

  • LibVCX, the credential exchange library, is available in Indy SDK as an experimental API. We are evolving that API to respond to community feedback.

  • These efforts are likely to require backwards incompatible changes to the API, requiring an Indy SDK 2.0.

Indy Agent

  • 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.Contributing a reference mobile agent to the Sovrin Foundation.

Maintainer Diversity

Indy maintainers remain active in developing and contributing to working group calls and public discussions. The bi-weekly Indy Maintainers Circle call has consistently been the medium by which maintainers coordinate work, discuss critical issues to the Indy codebase, and resolve HIPEs. The Indy Agent call continues to be the focus of much attention, and the Overlays Working Group also continues to receive a lot of interest .

...

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

...

  • Join the Indy Working Group Calls: every Thursday 8am PT, 9am MT, 11am ET, 4pm BST (Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/232861185 )