Date: Tue, 19 Mar 2024 10:34:31 +0000 (UTC) Message-ID: <260508141.55049.1710844471099@aws-us-west-2-hyp-confluence-1.web.codeaurora.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_55048_1635294129.1710844471099" ------=_Part_55048_1635294129.1710844471099 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Hyperledger Iroha
Project Health<= /span>
After the production-ready release the community is very active, new pro= jects start using Iroha as solution for their backend. People exchange info= rmation, help each other, although most of the advanced help is still on th= e maintainers. We also receive proposals for new features from the communit= y members.
New features:
Configurable validators
Synchronization improvements
Passing updated peer list on initialization
Peer management options: added RemovePee= r command and GetPeers query
TLS: client-to-peer and peer-to-peer
CompareAndSetAccountDetail command
Executor Integration Test Framework for testing business lo= gic
We also work closely with HL interns and engaged interns fr= om the Innopolis University (Innopolis, Russia). Great results are expected= .
Issues=
There are no specific issues at the moment. There are questions such as = diversity and consensus improvements architecture but we are addressing the= m already and see progress in that.
= Hyperledger Iroha v1.0 on May, 7th
= Release 1.0.1 on June, 24th
We receive questions through mailing lists from time to time and use the= m for sending out important information. Chat channels are much more active= - mostly active members of the community are communicating their questions= and try to help newcomers. There is a very positive experience of communit= y members starting working on projects together. All the questions are bein= g answered either by the community members or the maintainers.
Currently, we are working on 1.1 version of Iroha that will include new = features such as new queries and permissions as well as refactoring changes= to create a stronger and more secure system. There has been a slight delay= with this release but we are planning to have it as soon as small fixes ar= e made that prevent it at the moment.
We have some major plans, currently: consensus improvements, suppor= t for Burrow (EVM) (already in process), support for WASM, improv= ed permission model (in progress including the ideas from the community),&n= bsp;support for Ursa (also in progress), complex object support, = support for Explorer, improved reporting capabilities using the databa= se, integration with Polkadot. We also hope to collaborate with the co= mmunity more.
We have an addition in Iroha team: Eugene Kovalev (architecture speciali= st)
New code contributors:
Alexander Andryukov (https://= github.com/Exctues)
Yash Chaudhary (https://github.com/yash2code)
Alexander Matson (https://github.com/alexmat2on) - HL intern= working on Ursa integration
Ivan Tyulyandin (https://github.com/IvanTyulyandin) - HL= intern working on Burrow integration
Artyom Yurin (https://github.com/artyo= m-yurin) - Innopolis University intern, working on configuration i= n the ledger
Ruslan Tushov (https://github.com/turuslan= ) - HL intern working on Explorer integration
Leonid Lygin (https://github.com/ionagamed) - intern from Inn= opolis University working on TLS
Non-code contributors:
Bobby Jackson
and other members of the comm=
unity from our chats that are not here yet but share their Iroha use experi=
ence helping us as well as sharing their ideas.
Additional In= formation
Work with interns is going very well so we hope to have integration with= several HL projects very soon thanks to the interns' effort and hard work = as well as helpful guidance from Ig= or Egorov and Andrei Lebedev&nb= sp;