Week 1 - Week 3

Jun 1 - Jun 18

Jun 18: 1st Quarter Evaluation

•  Install Ubuntu 20.04 LTS and set up environment.
•  Build Cactus.
•  Build Iroha.
•  Understand existing source code.
•  Start the Iroha and Cactus integration.

•  Project Plan.
•  Skeleton for Iroha and Cactus integration.

Week 3 - Week 6

Jun 19 - July 9

July 9: Midterm Quarter Evaluation

•  Implement the Iroha and Cactus integration.
•  Write tests for the Iroha and Cactus integration.
•  Write documentation.

•  ~50% of the Iroha and Cactus integration package.
•  Technical documentation for the package.

Week 6 - Week 10

July 10 - July 30

July 30: 3rd Quarter Evaluation

•  Write tests for Iroha and Cactus integration.
•  Write documentation.

•  Completed package for Iroha and Cactus integration.

Week 10

July 31 - Aug 10

Aug 20-31: Final Evaluation

•  Wrap up documentation.
•  Final report of the project.
•  Final presentation of the project

•  Code for unit tests and integration tests. *
•  Technical documentation for the entire project.
•  Final report.
•  Final presentation.
•  1 examples example of Iroha and Cactus integration. (Nice-to-have)
•  2 examples of Iroha and Cactus integration. (Optional)
•  2 examples of Iroha and Fabric integration. (Optional)

gRPC TLS option is not implemented.

Currently, only able to pass in TLS parameters( TLS Cert/ TLS Key/ TLS Port) to iroha test ledger, but those parameters are immediately discarded.

Implement gRPC TLS support for Iroha test ledger.

(Refer to Cactus PR #1190 as an example. )

2

1 

(important)

fetchCommits is not implemented. 

It is inside the plugin-ledger-connector-iroha.ts, but unable to test it due to its unique characteristic of streaming responses.

4

4a.

2

(will be important

once full support for smart contract)

There is no implementation for smart contract (InvokeContractV1Request).

4b. InvokeContractV1 is not implemented due to the lack of smart contract.

4c. On top of this, Call Engine is not implemented. (because it tries to call Call Engine calls smart contract)

( CurrentlyFor Call Engine, we intentionally reject the transaction within the ledger, and thus able to test then validate the rejection in the test case. ) 

4a. Implement Call Engine command and test it.

smart contract once Iroha fully supports smart contract.

4b. Implement InvokeContractV1 for Iroha connector once Iroha fully support smart contract.

4c. Given smart contract is supported by Iroha, implement Call Engine and test it.

5 ( will be important once Iroha fully supports smart contract)

Link

Link

setSettingValue is not implemented .  (Currently only can because this command can only be called inside genesis.block )file.

( Currently, always return Current connector implementation returns HTTP 405 Error in plugin-ledger-connector-iroha.ts)

Implement SetSettingValue command and When Iroha is able to run SetSettingValue outside of genesis.block, implement and test it.

When Iroha supports SetSettingValue...., implement

(It is being said that the Iroha team plans to support running SetSettingValue outside of genesis.block.)

removePeer is not fully tested. 

A valid Iroha testnet needs to be constructed to test this command removePeer.

Able to manipulate Iroha testnet ( An Iroha testnet usually composes of >= 3 Iroha nodes).

Then, construct Iroha test within the test case to test removePeer.

5

(important)

fetchCommits is not implemented. 

Put it inside the plugin-ledger-connector-iroha.ts, but unable to test it due to its unique characteristic of streaming responses.

7

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) In other words, it seems to be an issue with Iroha ledger itself instead of the Iroha Javascript library.

Able to produce a pending transaction in the test case.

Able to validate the pending transaction via getPendingTrasaction query.

Prometheus exporter metrics integration

The grpc tls option is not implemented.

Currently, only able to pass in tls parameters(tls cert/ tls key/ tls port) to iroha test ledger, but tls is not supported.

Add prometheus exporter to the Iroha connector plugin.

1a. Utilized iroha-helpers-ts because  since the original Iroha Javascript library gives “undefined” as output. 

However, iroha-helper-ts is based on a an old Iroha Javascript library (12/23/2020 release), which does not support some new features.

1b. Due to this, currently, one argument for compareAndSetAccountDetail, check_empty, is not dealt with inside the plugin-ledger-connector-iroha.ts file. The run-transaction test case also fail to use this argument.

1a. Build Construct our own iroha-helper-ts library (outputs tx status and tx hash) based on the Iroha Javascript library, so that it could be upgraded to match the most recent Javascript library . Its version. Moreover, our own iroha-helper-ts's output could be further optimized to suit test cases better. 

1b. After developing our own iroha-helper-ts library, correct compareAndSetAccountDetail's arguments. Also, correct the test case accordingly.

Link

Link

The test cases rely on a modified Iroha v1.2.0 all-in-one (AIO) docker image.

However, Iroha version 1.2.0 is outdated.

Embedded An Iroha Python SDK is embedded inside the Iroha AIO docker image for docker healthcheck. Although the current this healthcheck mechanism works fine, it makes the docker image ~100MB larger. 

For docs/source/support/iroha.md, the link to the transaction test link is not guaranteed to be valid.