Page tree
Skip to end of metadata
Go to start of metadata

Project

Hyperledger Iroha

Project Health

The development during the period has been a little slow, but community activities seem to be in order — people communicate in chats, receive their answers, everyone is acting appropriately and respectfully. Also, we have finished several Internship projects for the improvement of Hyperledger Iroha. 

Questions/Issues for the TSC

No issues at the moment. 

Releases

Hyperledger Iroha v1.2 Release Candidate 2

Overall Activity in the Past Quarter

Development was a little slowed down but at the same time, we managed to finish all the internship projects. Unfortunately, not all of them was finished successfully — 2 were terminated because of the lack of commitment from the students.

Chats are active even if the mailing list is not so much.

After the security audit and feedback from the community, we made several security fixes for the release.

Current Plans

Currently, we want to make a release with "1.2.0rc3" tag which will be thoroughly tested towards finding regression problems. After testing we will release version "1.2.0" with all the fixes, which could be a very stable and reliable milestone of the Hyperledger Iroha development.

After that we will start active development of the "2.0" version which will solve most of the current challenges — it is our longer-term plan. 

Maintainer Diversity

https://github.com/orgs/hyperledger/teams/iroha-maintainers/members represents people who help maintain Iroha.

Contributor Diversity

A company that uses Iroha contributed Turkish translation of the Iroha documentation on which we started basing our l10n repo - currently in development of simpler scripts. 

Iroha Blockchain Explorer - a useful #nodejs and #docker solutions were contributed by diva.exchange

Additional Information

Reviewed By


5 Comments

  1. Is the Iroha Blockchain Explorer distinct? Or does it build on top of Hyperledger Explorer?

    1. I believe it is a separate solution by diva.exchange team (smile)

  2. The report mentions "security audit and feedback from the community". Do each of the project document these in a place/is there a central artefact of these across the projects?

    1. I would probably ask the TSC or HL team regarding their ways of accessing security information about the audits. About the community feedback — a user found an issue that we fixed. It does not seem to be a severe one.