...
Peer to Peer Network
Blocks Storage
Smart Contracts
| Item | EPIC | Importance | RFC | Notes |
|---|
| Iroha Special Instructions mechanism |
| |
|
|
| Out of the box set of Iroha Special Instructions | HI2-28 HI2-29 HI2-35 | |
| Several Tiers of Iroha Special Instructions provide: - Basic building blocks that can be used to build Custom Iroha Special Instructions
- Maintenance related Iroha Special Instructions (Add Peer, Change Build Block Time, etc.)
- Iroha Modules related Iroha Special Instructions (Bridge, DEX, etc.)
|
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.
Maintenance
Clients
| Item | EPIC | Importance | RFC | Notes |
|---|
| Rust Client Library | HI2-32 | |
Discussed in chat, Nikita Puzankov will create an RFC based on the discussion |
| Iroha Client encapsulates network related functionality and provides "local" Rust Interface for: - Submitting of Iroha Special Instructions to Iroha Peer
- Querying Data from Iroha Peer
- Maintenance Endpoint API
|
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.
User interaction and design
...