| Page Properties |
|---|
| Target release | 2.0.0 |
|---|
| Epic |
|
|---|
| Document status | |
|---|
| Document owner | |
|---|
| Designer | |
|---|
| Developers | |
|---|
| QA | |
|---|
|
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
https://github.com/hyperledger/iroha/blob/iroha2-dev/iroha_2_whitepaper.md#11-relationship-to-hyperledger-fabric-hyperledger-sawtooth-hyperledger-besu-and-others
Assumptions
Requirements
Functional
Peer to Peer Network
Blocks Storage
Consensus
Queries
| Item | EPIC | Importance | RFC | Notes |
|---|
| Iroha Queries | HI2-31 | |
| Iroha Queries provide information about World State View based on client permissions. |
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.)
|
| Permissions | HI2-36 | | Permissions and Event Listeners | Permissions in Iroha implemented based on Assets and Iroha Special Instructions. |
| Triggers | HI2-37 | | Permissions and Event Listeners | Triggers in Iroha implemented based on Assets and Iroha Special Instructions. |
| Domain Specific Language |
| | DSL Structure | Custom Iroha Special Instructions and usage of the full set of Iroha Special Instructions should be easy for developers. |
| Advanced Permissions Model |
| | Expand Iroha Permission model | Full-fledged rights model in Iroha will greatly reduce the amount of server development for Iroha-based applications. |
Modules
| Item | EPIC | Importance | ADR/RFC | Notes |
|---|
| Bridge |
| | Bridges | Mechanism for communication between third-party blockchains. |
Maintenance
Clients
| Item | EPIC | Importance | ADR/RFC | Notes |
|---|
| Rust Client Library | HI2-32 | |
| 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
|
| `no-std` client |
| | Migration from Strings |
|
| Mobile SDK | HI2-33 HI2-9 HI2-8 | |
|
|
| Web SDK | HI2-34 HI2-10 | | Web API |
|
Non Functional
Security
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.
Development related
Benchmarks
Maintenance
- Logging -
| Jira Legacy |
|---|
| server | Hyperledger JIRA |
|---|
| serverId | 6326cb0b-65b2-38fd-a82c-67a89277103b |
|---|
| key | IR-832 |
|---|
|
- Service Discovery
Continuous Delivery
- Docker images publish
- Binary and documentation publish
Longevity Stand
Distributed testing
- 10 servers, each on a different machine and in different geographies.
- Run data through them for several minutes to really get some meaningful data.
- Here is what each peer should do:
- sync with peers about latest blocks
- gossip about (forward) transactions that are pending that they have
- propose or vote on a block (as part of consensus)
- ping and verify peers as part of the Hijiri reputation system (basically something like eigentrust++)
- share time information as part of a p2p network time service
User interaction and design
Questions
Below is a list of questions to be addressed as a result of this requirements document:
Not Doing