2022 Q1 Hyperledger Iroha

Created by Sara Garifullina, last modified by Peter Somogyvari on May 25, 2022

Project Health

We are still continuing working as 2 teams – Iroha 1 and Iroha 2. Both teams develop features, fix issues, talk to the community. Still, once in 2 weeks we meet for our community meeting (where anyone could attend). Iroha 2 is planning to show their first working version soon, Iroha 1 constantly improving the production-ready versions and implemented a couple of very nice features to increase the performance and experience. We have questions from the community on various integrated projects which we might need to discuss soon (e.g using Burrow or Ursa). 

Required Information

  1. Have you switched from master to main in all your repos ? Yes
  2. Have you implemented the Common Repository Structure in all your repos ? Yes

Questions/Issues for the TSC

No questions for now

Releases

https://github.com/hyperledger/iroha/releases/tag/1.4.0-rc.1  - Soon to publish RC 2 and after testing – 1.4.0

Overall Activity in the Past Quarter

In terms of communications, chats were rather active, mailing lists - not so much. The questions are being answered, communication continues as well as the community calls – so if someone wants to connect, they certainly can. 

In terms of development: 

Iroha v1:

Made a release of 1.4 - rc1 (tag is ready for rc2 as well - just needs to be published as a release)

Added the feature of syncing node

Healthcheck

Fixes on the memory consumption and others

Iroha v2:

Improved performance

Added prometheus metrics for profiling

Integrated WASM to support more smart contracts

Integrating triggers

Current Plans

Both Iroha 1 and Iroha 2 teams are active and have their own objectives:

Iroha v1: 

Release 1.4 based on release candidate 2

Speed up internal communication within Iroha

Moving configuration into the blockstore

Minimise OS traffic

Iroha v2:

Refactor Sumeragi consensus

Memory consumption improvements, 

Final testing for preview release candidate 1

New procedure for SDK synchronisation

Maintainer Diversity

1 C++ developer and 1 QA specialist joined Iroha 1 team. Iroha 2 was joined by a new project manager who will be leading the development and the project in general and a Rust developer as well as several specialists contributing into the libraries 

Contributor Diversity

Soramitsu maintains Iroha still with help from  Grzegorz Bazior ‘s team

Additional Information

Reviewed By

Submission date

06-Feb-2022

Comments:

e.g using Burrow

Arnaud mentioned that he communicated with the Iroha community that Burrow has been deprecated. These may be the conversations that you are referring to. I wanted to make sure that this is the case.

Posted by tkuhrt at Feb 08, 2022 15:21

Sara Garifullina – That's great to hear that Iroha 2 is planning to show their first working version soon.  We're happy to coordinate with the team to help them share this on Hyperledger's channels.  And if they have interest in connecting with people who'd like to contribute, we could organize a contribution campaign around this.  Feel free to reach out if you'd like to talk more about that.

Posted by davidwboswell at Feb 08, 2022 17:48

Yes, that is the case. We are currently thinking about how to approach this. 

Posted by SaraG at Feb 08, 2022 19:39

Thank you, that would be great! As soon as we have everything in order, I hope we will all find the time to come up with something interesting for the community  (smile) 

Posted by SaraG at Feb 08, 2022 19:40

Apologies for the late review. LGTM

Posted by Peter Somogyvari at May 25, 2022 05:32