Iroha 2
- Vadim Reutskiy
- Nikita Puzankov
Iroha is a straightforward distributed ledger technology (DLT), inspired by Japanese Kaizen principle — eliminate excessiveness (muri). Iroha has essential functionality for your asset, information and identity management needs, at the same time being an efficient and trustworthy crash fault-tolerant tool for your enterprise needs.
Features
Iroha has the following features:
- Creation and management of custom fungible assets, such as currencies, kilos of gold, etc.
- Management of user accounts
- Taxonomy of accounts based on domains in the system
- The system of rights and verification of user permissions for the execution of transactions and queries in the system
Navigation
The main inspiration for Iroha 2 described in the White paper.
User guides and good information to start placed on Read the Docs.
Confluence pages of Iroha 2 provide you with information about software development related aspects:
Github repository contains developers oriented information about builds, tests, contribution to project and usage of project inside your projects.
Contribution and Requests
Every new feature should go through the following steps:
- Requests for Comments is created and filled according to the instruction
- All stakeholders commented or wrote a comment that they do not have anything to add or time to comment
- Decisions, Assumptions and all other Solution's sections filled
- Status changed to "Completed".
- RFC moved to the Architecture Decision Records Log
- Requirement placed into the table Needs and Requirements with reference to the RFC
- Issues and Epics created in Jira
- All issues linked back in the table Needs and Requirements
List of contents
- Decision log
- General Profiling for improving Iroha2 TPS
- Meeting minutes
- 2020-07-07[2] Meeting notes
- 2020-08-11 Iroha DSL RFC Discussion - Meeting notes
- 2020-06-02 Meeting notes
- 2020-08-18 Meeting notes
- 2020-07-28 Status Meeting notes
- 2020-04-16 Iroha 2 status meeting notes
- 2020-08-13 Weekly RFC Review - Meeting notes
- 2020-07-23 Meeting notes
- 2020-07-23 Status Meeting notes
- 2021-01-26 Meeting Notes - Suggestions from Java client library developers
- 2020-04-30 Status meeting notes
- 2020-05-19 Meeting notes
- 2020-05-08 Demonstration meeting notes
- 2020-06-09 Meeting notes
- 2020-09-01 Meeting notes
- 2020-07-09 Meeting notes
- 2020-08-11 Meeting notes
- 2020-04-21 Meeting notes
- 2020-05-21 Status meeting notes
- 2020-04-23 Iroha 2 status meeting notes
- 2020-05-17 Meeting notes
- 2020-08-25 RFC: Triggers discussion meeting notes
- 2020-06-25 Meeting notes
- 2020-07-27 Meeting notes - Asset-store RFC discussion
- 2020-05-28 Status meeting notes
- 2020-08-06 RFCs Review - Meeting notes
- 2020-07-30 RFC review Meeting notes
- 2020-07-02 Meeting notes
- 2020-07-30 Status Meeting notes
- 2020-08-04 Meeting notes
- 2020-05-12 Meeting notes
- 2020-06-04 Meeting notes
- 2020-04-28 Meeting notes
- 2021-06-02 - Iroha Runtime Improvements Discussion
- 2020-07-07 Meeting notes
- 2020-08-18 Permissions RFC Review - Meeting notes
- 2020-05-26 Status meeting notes
- 2021-01-28 Meeting Notes - Suggestions from Java client library developers
- 2020-08-21 Iroha RFC discussion: Permissions, part II - Meeting notes
- 2020-04-14 Iroha 2 status meeting notes
- 2020-06-23 Meeting notes
- 2020-09-03 Meeting notes
- 2020-08-13 Meeting notes
- 2020-06-11 Status meeting notes
- 2020-07-16 Meeting notes
- 2020-08-27 Meeting notes
- 2020-08-06 Meeting notes
- 2020-05-05 Meeting notes
- 2020-04-17 Iroha 2 Demonstration Meeting notes
- 2020-07-28 BDD Demonstration Meeting notes
- 2020-08-20 Iroha Modular Data Model RFC - Meeting notes
- 2020-06-16 Meeting notes
- 2020-05-07 Meeting notes
- 2020-07-21 Meeting notes
- 2020-06-18 Meeting notes
- 2020-08-25 Meeting notes
- 2020-07-15 Planning Meeting notes
- 2020-05-14 Status meeting notes
- 2020-06-08 Meeting notes
- 2020-06-11 Meeting notes
- Architecture Decision Records Log
- Prevent replay of rejected transactions
- Permissions
- Rust Async Runtime
- Key-centric accounts structure
- Triggers
- Sumeragi Error Handling
- Set of OOB ISIs
- P2P network
- Different key types
- Scheme generation of model-objects
- Library usage for HTTP and WebSocket protocols
- DEX Generic Scenarios
- Blocks sign off
- Genesis Block and Network Setup
- Scripting Languages and Runtimes for Iroha2 Smart Contracts
- Iroha Special Instructions DSL
- Async-std API usage
- Query Permissions Do Not Apply to Validators
- Message Versioning
- Pluggable modules and actor model
- Bridges
- Encapsulation of crypto related functionality
- Use serde-json for deserialization of `config.json`
- Modular Data Model
- Cloud Events
- Web API
- Networking stack
- Logging
- Place of assets in Iroha model
- Maintenance Endpoint
- Multisignature transactions
- Iroha crates naming for crates.io
- Serialization Format
- Change View Drawback in Sumeragi
- Block Synchronization
- Environments
- Product requirements
- Requests for Comments
- zzz_[ARCHIVE]
- Extensible serialization
- Merkle Tree
- Iroha Configuration
- Blockchain Explorer
- Telemetry
- Iroha positioning – SWOT analysis
- Modular cryptography providers
- WebAssembly FFI - module linking
- Promote Iroha Runtime Validator into Iroha Runtime Executor
- Hijiri algorithms
- Iroha configuration changing
- Iroha API for Clients
- Merkle-zation World State
- Template
- Suggestions and ideas for HL Iroha 1.x and 2.0!
- Mentorship articles
- Architecture