You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is one smart contract per BPI used to store all anchor hashes across all workgroups that are active in it
Smart contract owner is an account controlled by the BPI
Smart contract contains a map of workgroup id -> content addressable hash array and a pair is created each time there is a new workgroup created
content addressable hash array contains the list of all of the transactions hashes, where tx hash is txResult.hash = hashFn(${merkelizedInvoiceRoot}${witnessHash}).toString('hex');
and is updated after each successful execution of a workstep (succesfull state change) for a given workgroup
It is the responsibility of the account in control of the BPI to trigger the smart contract methods after events
We need a following list of issues to be implemented for this mechanism to work:
implement the smart contract with the needed functionalities (add workgroup, add CAH...)
Enable BPI to store relevant infomration to communicate with the smart contract (private key, address ...)
trigger add workgroup onchain on workgroup creation in the BPI
trigger add CAH on succesfull workstep execution
implement an endpoint to fetch StateTreeLeafValueContent object with accompanying info based on the provided CAH
Overview
This issue tackles as conditions and controls regarding deploying and calling the ccsm contract functions.
Tasks
The text was updated successfully, but these errors were encountered: