-
Notifications
You must be signed in to change notification settings - Fork 283
Description
Purpose
This issue documents the implementation status of Iroha v2 as of commit 884f870.
It provides a clear view of the current milestone status—covering both implemented and ongoing work—so that the baseline remains reproducible, traceable, and informative for future iterations.
Snapshot metadata
-
Milestone: 2.0.0-rc.3
-
Reference commit:
884f870 -
Docker image:
hyperledger/iroha:2-snapshot-2025-10docker pull hyperledger/iroha:2-snapshot-2025-10
-
Total issues: 37 (excluding sub-issues)
-
Categories:
- Open – feature issues
- Open – non-feature issues
- Closed issues
Open – feature issues
Core functional items still in progress or planned for the next incremental release.
- Research transaction fees #1177
- Introduce a set of waiting peers #1225
- Refactor Execution Cycle #5356
- feat: generic structure through execution cycle #5355
- Include the transaction hash in data events #5250
- Record Wasm trigger executions for auditing #5522
- Query permissions (Visibility Control 1) #5338
- Event subscription permissions (Trigger Safety 2-A / Visibility Control 2) #5439
- Quota-based economic deterrence (Trigger Safety 3) #5440
- Account aliases (for recovery?) #4372
- Guardian scheme for account recovery #5486
- Private validators (hub-chain as a cross-border tx solution) #4637
- Client-side block header validation to support Merkle proofs #5498
- Add technical account that will receive network fees #5315
- Permissionless accounts: registration-free model #4426
- Address dynamic IP addresses without requiring a restart with new configuration #5351
- Integrated webhook support for transaction events #5477
Open – non-feature issues
Maintenance and improvement tasks that can be addressed after release, including bug fixes, performance tuning, documentation updates, and security hardening.
api-changesData integrity inWorld#4672api-changesNamespace dimension vs. lightweight IDs #5361api-changesReplace public keys with those compressed #5280api-changesDeny external access to non-personal accounts #5022api-changesRegister and call Wasm instructions #5147api-changesRegistrable permissions #5359api-changesPipeline triggers: re-evaluate the necessity and safety #5512- Size limits for individual instructions or entire transactions #5342
- Performance degradation in executor for permission check #4756
- Ensure every execution path goes through the executor #5442
- Reintroduce topology shuffling to restore fault tolerance #5495
- Verify that features are additive #5416
- Transactional queries execution context #5171
- Stateful communication protocol and initialization handshake #2112
- DAG-based consensus #5375
Closed issues
Changes already merged but not yet included in a tagged release.
- Consensus hash should reflect the validation outcome #5473
- Record trigger execution as a transaction #4968
- Data triggers should inherit origin authorities (Trigger Safety 2-B) #5441
- Per-transaction triggers #4937
- Trigger that fires too often #5232
State of Iroha JavaScript SDK
A pre-release version of Iroha JS supporting 884f870 (as clearly seen here) is available at the current main (https://github.com/hyperledger-iroha/iroha-javascript/tree/c7fad03a54e2317ccf63f9960c7bfe198a2e9f3d) and is published on JSR:
SDK API changes are briefly documented in the relevant PR: