...
- Users will work with provided client libraries (iOS, Android, JS).
- 3f+1 nodes 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 build on top of these set.
Requirements
Functional
Peer to Peer Network
| Item | EPIC | Importance | Notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Peer to Peer Network Library | HI2-6 |
| Plain TCP\IP based protocol with SCALE as de\serialization format. | ||||||||
Blocks Storage
| Item | EPIC | Importance | Notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Blocks Synchronization | HI2-2 |
| //TODO Egor Ivkov please add small note about the gossip design and concerns. |
Non Functional
Target Platforms
Iroha deployment should support GNU/Linux, MacOS and Windows machines with x86 and Arm64 CPUs.
Transactions Processing
Iroha Peer should be able to process 20,000 transactions per second.
Blocks Processing
Iroha should be able to commit a new block every 3 seconds.
| # | Title | User Story | Importance | Notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Transfer Assets | Account owner able to transfer assets to other accounts |
|
| ||||||||
| 2 | Peer to Peer Network | https://soramitsucoltd.aha.io/features/HI2-6https://soramitsucoltd.aha.io/features/HI2-2 |
|
| ||||||||
| 3 | Smart Contracts | https://soramitsucoltd.aha.io/features/HI2-29 |
|
| ||||||||
| 4 | Storage | https://soramitsucoltd.aha.io/features/HI2-1 |
|
| ||||||||
| 5 | Permissions | https://soramitsucoltd.aha.io/features/HI2-36 |
|
| ||||||||
| 6 | Event Listeners | https://soramitsucoltd.aha.io/features/HI2-37 |
| |||||||||
| 7 | Maintenance Endpoint |
| Maintenance Endpoint | |||||||||
| 8 | Transactions TTL |
|
|
...