| 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
...
Assumptions
- Users will work with provided client libraries (iOS, Android, JS).
- 3f+1 nodes are enough to tolerate f Byzantine nodes in the network.
- Iroha uses a simple data model made up of domains, peers, accounts, assets, signatories, and permissions, as shown in the figure below - all other entities are built on top of them.
...
- The main source of core structure: Iroha 2 white paper, authored by 武宮誠
- List of requests from the Soramitsu projects regarding features
- Decisions made during the discussion, which are fixed in the list of RFCs
Functional
Peer to peer communication
| ID | Item | EPIC | Importance | Status | ADR/RFC | Notes | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| IF2-100 | Peer to Peer Network Library |
|
| Networking stack | Plain TCP\IP based protocol with SCALE as de\serialization format. Iroha must have a specific peer-to-peer protocol for effective communication and provided it as a detachable library. | |||||||||||||||||
| IF2-101 | Transactions Time to Live | HI2-38 |
| Prevent replay of rejected transactions | Iroha must provide the possibility to explicitly state time-to-live (TTL) for each transaction, so the clients can set time interval in which transactions should be confirmed and put into the block store or removed from the queue by timeout. | |||||||||||||||||
| IF2-102 | Multisignature Transactions | HI2-13 |
| Iroha must provide the possibility to configure each account to have a list of signatories, which needs to provide their signatures to confirm the transaction. Also, Iroha should provide the possibility to perform conditional multi-signature transactions, so the conditions will automate transaction creation or signing them | ||||||||||||||||||
| IF2-103 | Transaction dependencies |
| Transaction tags | (Proposed by Kamil') Iroha may provide a possibility to perform tag-based dependencies between transactions for making their sequence configurable by the client |
...