As our incubated projects continue to mature, we’d like to update the community monthly on the progress we make. Below are May updates on Hyperledger projects.

Hyperledger Explorer

  • We are currently understanding the Node SDK provided by Hyperledger Fabric
  • Created basic project setup with front end using popular react.js framework
  • Added two new developers and are busy getting them up to speed on contributing to Hyperledger Explorer

Hyperledger Burrow

  • We moved and renamed former eris-db v0.16 into Hyperledger Burrow v0.16 (logistics) to initiate Hyperledger Burrow
    • We upgraded Tendermint v0.8.0 (Burrow v0.16) to Tendermint v0.9.2 (on develop Burrow v0.17)
    • Initial design work completed on user interaction with Hyperledger Burrow’s EVM from within Hyperledger family, specifically looking at Hyperledger Composer for UI/UX (replacing monax/legacy-contracts.js) and Hyperledger Indy for identity
  • Started collaboration with Hyperledger Sawtooth to use Hyperledger Burrow’s EVM as a transaction processor on the Hyperledger Sawtooth platform

Hyperledger Cello

  • Added new user-dashboard to support multi-tenant
  • K8s support has been discussed and will make documentation on jira
  • Hyperledger Fabric 1.0 support script are submitted
  • Summer intern students were trained to get familiar with the project

Hyperledger Composer

  • Made great progress with our move to Hyperledger:
    • Moved all source code and builds into GitHub and Travis CI under the Hyperledger organization
    • Moved the main website and documentation to https://hyperledger.github.io/composer
    • Substantial rebranding effort of main website, documentation, and playground
  • Delivered support for deploying Hyperledger Composer to Hyperledger Fabric v1.0 alpha:
    • New version of the getting started guide and related documentation
    • Continuing to keep in step with the latest Hyperledger Fabric v1.0 changes
  • Delivered connection profile and identity management support in the playground:
    • Use connection profiles to connect to Hyperledger Fabric v0.6 and v1.0.
    • Use identity management to switch between different Blockchain identities.
    • Removed and deprecated the old, superseded UI
  • Upgraded the Angular generator to generate Angular 4 applications.
  • Began work on being able to model, publish, and subscribe to business events.

Hyperledger Fabric

  • We agreed to a feature/code freeze at the Hackfest in DC, and selected co-release managers for the v1.0 release: Chris Ferris (IBM) and Jonathan Levi (Hacera).
  • At the hackfest, we also discussed and agreed on some changes to the development process proposed by Dave Huseby, which we will implement as a function of creating the release branch for v1.0.0-alpha2.
  • The TL;DR: of the proposal is that we will manage change through feature branches that will be merged into a development branch to undergo the full gauntlet of testing, and reverted if they still need work. Once the development branch has merged the set of features agreed for a release, the develop branch will be fast forward merged into the release branch (also the master branch), tested once more, and then published. The release/master branch which will always have the most recent stable release as the default on GitHub (as opposed to the head of development as is the case today).
  • Hyperledger Fabric added three new maintainers to help keep reviews up with the pace of change requests.
  • The rate of bug fixing has consistently outpaced reporting for the past 3 weeks, with in excess of 50 defects resolved per week.
  • The unit test coverage has seen steady improvement, now more than 70% (it had been 61%) with many key areas of the code at 100%. The integration test framework is taking shape and we expect to have regular testing (daily, performance/scale and long running) operational shortly.
  • Maintainers cut a v1.0.0-alpha2 release the week of May 8

Hyperledger Indy

  • Hyperledger Indy team is currently planning Jira migration from Sovrin to Hyperledger and working on configuration post-Jira Upgrade
  • Planning migration of code from Sovrin GitHub to Hyperledger GitHub
  • The team is identifying participants for Healthcare, Performance and Scaling WGs as well as collaborators for Hyperledger Burrow and Hyperledger Composer

Hyperledger Iroha

Hyperledger Sawtooth

  • Hyperledger Sawtooth graduated to Active status, announced at Consensus
  • Good hacking at the DC Hackfest, getting started integrating the Hyperledger Burrow EVM and Hyperledger Sawtooth.
  • On track for 0.8 feature complete (one condition for 1.0 release this summer).
    • Updated PoET to Hyperledger Sawtooth 0.8 architecture
    • Implemented PoET Z, C, & K admission policies
    • Threaded peering code
    • Added docker compose features and docs
    • Automated binary package and docker images
    • Improved serial scheduler to take advantage of new context manager functionality
    • Implemented client-side Javascript SDK (Transaction/Batch creation)
    • Implemented Go SDK
    • C++ SDK in progress

That’s it for the updates! We encourage developers to join our efforts on these projects. You can plug into the Hyperledger community at github, Rocket.Chat the wiki or our mailing list. You can also follow Hyperledger on Twitter or email us with any questions: info@hyperledger.org.

Happy coding!