| Page Properties | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Goals
Hyperledger Iroha v2 aims to be an even more simple, highly performant distributed ledger platform than Iroha v1. V2 carries on the tradition of putting on emphasis on having a library of pre-defined smart contracts in the core, so that developers do not have to write their own code to perform many tasks related to digital identity and asset management.
Background and strategic fit
...
| ID | Item | EPIC | Importance | ADR/RFC | Brief description | Notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| IF2-200 | World State View |
| Iroha must have an in-memory representation of the World State View for optimization of access and change time. | In-memory, read fast data representation of the current World's State. | ||||||||||
| IF2-201 | Kura |
| Iroha must have abstraction over the disk-based block storage, which will cover all validation- and world-state-view-related functionality. Iroha should have the Kura as a detachable library, so other Hyperledger solutions can easily reuse it. | Kura is a decorator on top of Disk Block Storage and provides validation and World State View synchronization functionality. | ||||||||||
| IF2-202 | Blocks Synchronization |
| Block Synchronization | Iroha must perform seamless synchronization of block storage between peers, so new peers or lagging ones will quickly synchronize their state with the network and join the decision-making process in consensus. | //TODO Egor Ivkov please add a small note about the gossip design and concernsPeers periodically gossip with each other, sharing the latest block hash. If the hashes differ, then the peers discover they are out of sync and request synchronization. | |||||||||
| IF2-203 | Merkle Tree |
| Merkle Tree | //TODO: Egor Ivkov , may I ask you to fill that?Iroha provides a general purpose implementation of a Merkle Tree, which is used to verify the state of committed blocks and their transactions. |
Consensus
| ID | Item | EPIC | Importance | ADR/RFC | Brief description | Notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| I2-300 | Sumeragi | HI2-3 |
| Iroha must have a reliable BFT consensus of blocks between all peers, which should keep effectively prevent attacks and malfunctioning in case of (details of Sumeragi are described in the white paper) Sumeragi should be implemented as a detachable component and be available as a library, so other Hyperledger solutions can reuse it. |
...