TCF Monitor: Work Order Request

[kss-espeo]

Adapt monitor to connect to TCF rather than Gardener. Specifically, monitor Work Order Request off TCF JSON API. In order to interact with this API, you will need to set up TCF locally following this tutorial - API should be deployed on port 1947. In order to figure out details on how to integrate with that API, refer to an example client .

Submit Work Order Request via monitor Call input . It should add an entry in the table, having following fields (refer to docs linked above) :

workerId, workorderID, workloadId, inData (by default encrypted with session key. So monitor can just display a message that data is encrypted). Monitor can add an option to show data in plain text if user provides encryption key (which is session key by default )

Refer to docs for an encryption example.

This is just a first iteration - while right now we just monitor a JSON API, in future we will monitor Ethereum Smart Contracts using Ethereum Events and Web3.js - similarly to how gardener-monitor works right now. Keep that in mind while designing a solution.

[manojgop]

The JSON RPC http listener port is configurable and default value is 1947 https://github.com/hyperledger-labs/trusted-compute-framework/blob/master/config/tcs_config.toml#L35

[kss-espeo]

Method to create a worker: https://entethalliance.github.io/trusted-computing/spec.html#sec-direct-worker-register-request