Project Health

Everything is going ok: there are 2 lines of development - of Iroha v1 (on C++, production ready) and Iroha v2 (in Rust, in development). There are internship projects for both of them.  Work is being done, updates are provided to the community every 2 weeks on the community meetings from both lines of development.

Required Information

  1. Have you switched from master to main in all your repos? Switched in the main repository, others (library repositories) are not yet
  2. Have you implemented repolinter.json in all your repos? We believe that Ry Jones added it to the repos.

Questions/Issues for the TSC

While moving to main branch we've realised that we have DCO issues that were not reported by the DCO tool before. Also, from where does the DCO tool gets what it expects in the sign-off?


Overall Activity in the Past Quarter

In general, communication is going smoothly, we try to answer questions that come to the chat and also hold our bi-weekly meetings synchronously. 

Regarding some more technical developments:

Iroha v1:

  • Performance degradation fix
  • Stability fixes that handle cases when other nodes are not accessible or have slow connection
  • Performance metrics endpoint using prometheus (currently in support/1.2.x branch)
  • Replacement RxCPP dependency with custom subscription engine for more predictable thread management (currently in test and review)
  • Key-Value storage (currently under review)

Iroha v2: 

  • Introduced lockfree data structures
  • Introduced Grantable permissions
  • Added Roles
  • Deployed longevity stand
  • Increased significantly linting strictness
  • Covered several DOS attack vectors
  • Improved error reporting
  • Introduced transaction, block and message versioning support
  • Added pagination for queries

Current Plans

Iroha 1:

  • Introduce UDP-based peer-to-peer gossiping to boost networking
  • Improve ordering service and consensus to improve performance

Iroha 2:

  • Record telemetry and display it as a web app
  • Prometheus endpoint
  • Researching possibility of migrating async runtime to Tokio
  • Researching Triggers for our smart contract language
  • Implement autogeneration of client libs data model

Maintainer Diversity

Our contributor Grzegorz Bazior (Grzegorz) is now a maintainer and already helped us a lot by helping others in the chat, adding new functionality to Python library and by mentoring one of the internship projects. 

Another addition to the team is Ivan Kuvaldin who developed the metrics feature. 

Contributor Diversity

Core team still consists of Soramitsu team as well as contributors from other companies, such as Grzegorz and Sonoko Mizuki.

Additional Information

Reviewed By


  1. Could you please provide a bit more info on the DCO check failure? Was the sign-off totally missing, badly formed, or something else?

    Ry Jones can tell exactly how the check works but as far as I know it's merely a check on the commit log based on a regular expression.


    1. the check just looks to see if there is an SoB line. Plus, some people have over-ridden it.

      commit b4d1fc8a3a28818efd467fa4e3f8a80f18d4d016

      Author: kamilsa <>

      Date:   Fri Mar 26 10:16:28 2021 +0300

          Missing docs from master (#892)


          * Add peer documentation


          Signed-off-by: Sara <>


          * issue template fix


          Signed-off-by: Sara <>


          * fix in documentation


          Signed-off-by: Sara G <>


          Co-authored-by: Sara <>

          Co-authored-by: Sara G <>

      1. We had this issue with some commits, where there was a sign-off but with other credentials of the same people, so to make it work we had to rebase it. It was something like this:

        Expected "kuvaldini j***", but got "Ivan Kuvaldin k***