| Stepan Lavrentev | - Checked possible issue with storing of blockstore into the DB
- Could not find the reason and circumstances for a repeat, but looks like that it was caused by another issue with env vars.
- Found lack of documentation for the RemovePeer – there is no information that the last node cannot be deleted.
- Tried to build Iroha on Big Sur vis updated vcpkg – everything succeeds.
- If there are too many simultaneous transactions (for example, 500 per minute) – Iroha stops creating new rounds of consensus.
- Found the issue – if restarting through Docker Compose with the usage of 2 nodes, without reusing WSV, one node starts rereading blockstore from the start after the end.
- There is a "new" client application for Iroha – TUI (Text User Interface) client.
|