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.

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.

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?

https://github.com/hyperledger/iroha/releases/tag/1.2.1

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

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

Our contributor @baziorek (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. 

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