Date
Attendees
Goals
- Provide an overview of current Iroha 2 functionality
- Define important parts of future development
- Polish scenarios for broader audience demonstrations
Plan
Add asset scenario
Description
Given "User" role
And "Domain" domain with default role "User"
And "Account" account in "Domain" domain
And "XOR" asset in "Domain" domain, belonging to "Account" account with initial amount 0
When client sends `AddAssetQuantity` instruction to Iroha with Asset Id ("XOR", "Domain") and Account Id ("Account", "Domain") and amount 200
Then "XOR" asset in "Domain" domain, belonging to "Account" account has amount 200
Execution script
cargo test -p iroha_client --test add_asset
Transfer asset scenario
Description
Given "User" role
And "Domain" domain with default role "User"
And "Account1" account in "Domain" domain
And "Account2" account in "Domain" domain
And "XOR" asset in "Domain" domain, belonging to "Account1" account with initial amount 100
When client sends `TransferAsset` instruction to Iroha with Source Account Id ("Account1", "Domain") and Destination Account Id ("Account2", "Domain") and Asset Id ("XOR", "Domain") and amount 20
Then "XOR" asset in "Domain" domain, belonging to "Account2" account has amount 20
Execution script
cargo test -p iroha_client --test transfer_asset
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 15 min | Demonstration |
| |
| Improvements |
| ||
| Next Scenario |
|
Action items
- Nikita Puzankov prepare architecture review (with code)
- Nikita Puzankov map current architecture with a whitepaper (project roadmap and status)
- Egor Ivkov + Nikita Puzankov prepare peer to peer scenario (it may be propagation of transfer asset changes from one peer to another and we can send isi to peer1 while querying peer2 for results)
- Vadim Reutskiy , Andrei Lebedev and Makoto Takemiya provide more scenarios to cover