...
| Category | Current implementation | Expected improvements | Difficulty level |
|---|---|---|---|
Iroha connector plugin | 1 Call Engine is not implemented. (made the transaction rejected within the ledger, and thus rejected in the test case. ) | Implement Call Engine command in the connector. | |
2 SetSettingValue is not implemented. (returned http 405 Error) | Implement SetSettingValue command in the connector. | ||
| 3 removePeer is not implemented because a valid Iroha testnet is required to use this function. | Able to manipulate Iroha testnet (>= 3 Iroha nodes are recommended) Building on top of that, implement removePeer command in the connector. | 4/5 | |
| 4 fetchCommits is not implemented. | fetchCommits could be implemented as something similar to Besu connector's WatchBlockV1. | 3/5 | |
5 getPendingTransaction is not fully tested. There is an issue with producing a pending transaction, the code will get stuck and fail the test suite. It seems like Iroha ledger itself is struggling to generate the pending transaction. (https://jira.hyperledger.org/browse/IR-1010) | Able to produce a pending transaction in the test case. Able to validate the pending transaction via getPendingTrasaction query. | 4/5 | |
| Iroha-Javascript library | 1 I used iroha-helper-ts, but it could be further optimized. | Improve the JS library. The JS library gives “undefined” as output. It would be better for us to do the testcases if it outputs tx status and tx hash. | 2/5 |
| Iroha docker container | 1 The test cases rely on a modified Iroha v1.2.0 all-in-one (AIO) docker image. | Iroha version should be upgraded to improve Iroha ledger's performance. | 2/5 |
2 Embedded Iroha Python SDK inside the Iroha AIO docker image. Although the current healthcheck mechanism works fine, it enlarges the docker image by ~100MB. | The Iroha docker image could be shrinked once the Iroha team introduces the grpc healthcheck/ once the Iroha team make metrics page an option for v1.2.2. | 2/5 | |
| 3 Each Iroha docker container relies on a corresponding Postgres database container to store information. | The Postgres database docker container could be replaced by RocksDB ( needs just one folder - it should be docker volume - to keep data between different runs of image.) | 3/5 | |
| Documentation | 1 For docs/source/support/iroha.md, the test link is not guaranteed to be valid. | Updating the test link to be a valid link once the current Iroha PR gets merged/released. | 1/5 |
...