You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Projects

Distributed Ledger
Client Tools
Shared Components

Project Health

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

  1. Hyperledger Aries as the new home of the interoperable agent work.
  2. Ratification of former Indy Agent standards as Aries Standards and bootstrapping the Aries Community.
  3. Schema improvements are now in a proposed overview HIPE for community comment and feedback. A detailed HIPE exists for the context object for community comment. Work has begun on the context object.

Indy’s codebase has 22012 commits from 170 unique contributors. This represents an increase of 6 contributors this quarter and about 2,000 additional commits. Forums and chat channels are monitored and responses to questions are frequent, timely, and helpful.

Issues

Measuring the size and make-up of our user community

Progress was not made on this issue during the past quarter.

Further remediation planned:

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

 

Releases

May 2019:

Indy SDK 1.8.3
  • Fixed behavior of auth_rule and get_auth_rule request builders
  • Extended windows packages to contain *.dll.lib file.
  • Fixed boolean datatype representation for FFI.
Indy SDK 1.9.0
  • Added a set of functions to support work with Transaction Author Agreement concept.
  • Updated Indy-CLI to use session based approach
  • Updated Libindy indy_verifier_verify_proof function to check restrictions on requested predicates during validation of proof.
  • Updated Libindy to use Ursa instead of Indy-Crypto.
  • Updated Indy-CLI to provide a functionality of saving transactions into CLI context and the following usage of them.
  • Implemented State Proof verification for some types of GET requests to the ledger.
  • Bugfixes
Indy Node 1.7.1
  • Audit Ledger
    • helps keeping all other ledgers in sync
    • helps recovering of pool state by new or restarted nodes
    • can be used for external audit
  • Correct support of multi-signatures
  • Configurable Auth Rules in config state
  • Stability fixes
Indy Node 1.8.0
  • Add Transaction Author Agreement Acceptance Mechanisms and Transaction Author Agreement support
  • Configurable Auth rules improvements
  • Stability fixes

June 2019:

Indy SDK 1.8.2
  • Added auth_rule feature
  • Set default freshness threshold to 600 seconds
  • Send GET requests to two Nodes
  • Bugfixes
Indy Node 1.8.1
  • Hotfix to repair problem that nodes were restarting every 30-50 seconds
  • Other bugfixes

July 2019:   

Indy SDK 1.10.0
  • Added indy_build_auth_rules_request function to Libindy Ledger API to change multiple ledger auth rules. 
  • Added correspondent ledger auth-rules command to Indy CLI.
  • Bugfixes
Indy SDK 1.10.1
  • Updated Indy CLI to persist command history between sessions.
  • Bugfixes:
    • Corrected behavior of Indy-CLI ledger set-fees-prepare command to not add Transaction Author Agreement to request.
    • Corrected response data types in Indy-CLI ledger get-fees command.
    • Fixed State Proof verification for GET_REVOC_REG_DELTA requests in case of from and to are before first entry.
    • other minor bugfixes
Indy Node 1.9.0
  • Pluggable Request Handlers have been implemented

Overall Activity in the Past Quarter

Schema

  • Rich schema improvements are now in a proposed overview HIPE as well as a detailed HIPE for the context object. Community comment and feedback is underway. Work has begun on the context object. Three layers in the code base are affected: node, resolver, and SDK. Currently test node code can write and read contexts to and from the ledger. Initial work has started on contexts in the Indy-SDK layer as it is migrating into the Indy Resolver and Hyperledger Aries.

 Current Plans

Schema

  • Rich schema improvements will continue to document and implement additional objects and functions to fully implement rich schemas.

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 Semantics Working Group also continues to receive a lot of interest.

Contributor Diversity

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. Indy’s codebase has 22012 commits from 170 unique contributors. This represents an increase of 6 contributors this quarter and 2012 additional commits.

POCs, Pilots, Projects

Sovrin

http://www.sovrin.org

Sovrin is the first instantiation of the Indy codebase and has moved from the provisional network phase of development to production usage.

Verifiable Organizations Network

https://von.pathfinder.gov.bc.ca

The Province of British Columbia, the Government of Ontario, and Public Services and Procurement Canada have a trusted digital network of verifiable data about organizations.

Evernym

https://www.evernym.com/

Evernym is creating applications that will make it easy for organizations and users to issue, hold, and verify credentials through the Sovrin network.

Additional Information

Reviewed by

  • Arnaud Le Hors
  • Baohua Yang
  • Binh Nguyen
  • Christopher Ferris
  • Dan Middleton
  • Hart Montgomery
  • Kelly Olson
  • Mark Wagner
  • Mic Bowman
  • Nathan George
  • Silas Davis


  • No labels