SRI - Trigger storage of CAH in BPI smart contract on successful workstep execution

[ognjenkurtic]

Overview

Once the workstep executes successfully, we want to store the resulting content addressable hash in the BPI smart contract, so that a third party can validate that the workstep was executed with the correct inputs.

Scope of this one is to trigger the setAnchorHash method of the registered BPI smart contract with the workgroup id and the actual CAH as parameters, after the workstep has been successfully executed by the BPI.

This one is currently blocked by #803

Reference

• SRI use case design doc
• SRI - CCSM integration discussion #751

Questions

• Do we wait for the execution of the blockchain transaction?

Acceptance

• CAH is stored in the BPI smart contract after successfully execution of the workstep
• e2e test is extended to verify behavior with local hardhat node

Tasks

• Implement triggering of setAnchorHash
• Extend e2e test