Re: Request to move forward with the first major release of Hyperledger Iroha

Mic Bowman

I'm a little confused about the DCO comment. Could you explain how you're going to conform to the DCO?

On Mon, Mar 11, 2019 at 12:07 PM Nikolay Yushkevich <nikolai@...> wrote:
Dear Members of the Technical Steering Committee,

As Hyperledger Iroha maintainers we would like to request committee's permission to move forward with the first major release (1.0) and present the following achievements as a proof of the project's code maturity.

The latest release of Hyperledger Iroha available is Hyperledger Iroha v1.0 Release Candidate 4 Hotfix 1 version, available at: In this release we delivered a complete set of features that can be used to build DLT-powered enterprise-grade applications with the following features:

• Rich API with command-driven architecture
 for asset and identity management.
• Native support of Linux, MacOS and Windows environments.
• Crash fault-tolerant (CFT) consensus with experimental Byzantine fault-tolerant (BFT) algorithm and decentralized ordering service.
• Role-based access control.
• Client libraries, including example apps for iOS, JS (vue.js), Android (Java 8).
• Universal peer role and easily scripted deployment with Docker, Kubernetes, and Ansible Playbooks.
• Multi-signature transactions.
• Ordered and atomic batches of transactions.

We see Iroha as a universal solution for tokenization of assets or data, and we want it to be a simple and straightforward blockchain platform for enterprise, and blockchain enthusiasts.

The project is in active state and maintains the required level of quality over its lifespan:

• All of our code is licensed under the Apache-2.0 license.
• Sufficient test coverage:
• We have a significant amount of documentation available online in several languages:
• We have completed the CII certification, which can be viewed here:

Here is the list of current issues with the project and suggested solutions:

• Project maintainers' and contributors' diversity. At the moment, the Iroha node codebase is maintained mostly by Soramitsu; contributors are comprised of Soramitsu employees with some non-Soramitsu individual contributions. Internationalization of the documentation is more diverse — language versions of English docs are maintained by many native speakers. We have a diversity plan and it is already in effect:
• DCO — at the moment we are still introducing changes to the source code (mostly bug fixes), therefore it makes it hard to do the complete code freeze and modify the commit history so that it conforms to the standards. We would like to ask TSC's permission to ignore the issues until the code is frozen and only after fixing DCO we release first major release. We have a plan to execute once version 1.0 is released here:

We have a strong end user support base; this can be seen from the significant activity that we see on our Rocket.Chat channels (755 users), telegram chat (291 member) and Stack Overflow (41 questions). Our docker image was pulled 54'000 times as of 2019-03-11

We welcome the TSCs review of this request, and we are happy to follow-up and answer questions via email or by joining the weekly TSC call as required.

Best regards,

HL Iroha Maintainers team

Contact person: Nikolai Iushkevich, nikolai@...

Join { to automatically receive all group messages.