Skip to content
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.

Hyperledger Iroha v1.0 Release Candidate 4

Compare
Choose a tag to compare
@neewy neewy released this 01 Mar 13:20
· 44 commits to master since this release
4e9fac8

For this release we focused on performance, memory consumption so now Iroha is faster and more efficient. There are also some new features added.
Here are new improvements that are being released with RC 4!

Fixes and updates reducing memory consumption and improving performance:

Fixed nested object copy in shared_model proto backend: hyperledger-iroha/iroha#2096
Prevented CommandValidatorVisitor objects from copying: hyperledger-iroha/iroha#2107
Unsubscribe fix: hyperledger-iroha/iroha#2121
Reworked proposal sharing: hyperledger-iroha/iroha#2085
Fixed busy waiting in transaction status stream loop: hyperledger-iroha/iroha#2104
Removed block memory leak: hyperledger-iroha/iroha#2103
Fixed command service infinite replay: hyperledger-iroha/iroha#2102
YAC storage cleanup: hyperledger-iroha/iroha#1947

Test improvements:

Added performance test based on locust.io
Now Iroha’s performance can be tested. Read more here: hyperledger-iroha/iroha#2087
Test for new RX operator combine_latest_until_first_completed: hyperledger-iroha/iroha#2122

Documentation improvements:

Added important details about AddPeer command (public key validation): hyperledger-iroha/iroha#2098
Updated Iroha README: hyperledger-iroha/iroha#2114

Among other important updates:

We finally removed SWIG dependency from the project: hyperledger-iroha/iroha#2113
Added two more Ordering Gate configuration parameters: hyperledger-iroha/iroha#2094
Added test@test keypair into samples close to the example genesis block: hyperledger-iroha/iroha#2128
Fixed Ansible deployment scripts: hyperledger-iroha/iroha#2099

Known issues

Synchronization in networks, where more than f peers might shutdown, will fail after a node restarts since hyperledger-iroha/iroha#1947 PR was merged. This happens because synchronization between rounds relies on commit synchronization event. The issue will be fixed in further RC with the propagation of the last commit for the unsynchronized node.

You can also check the full list of updates below.
よろしくね!