search

MaastrichtU-IDS / DecentralizedHealthcareBackend

Other
0 stars 2 forks source link

Main.sol deployment #17

Closed Giacomo-Terragni closed 1 year ago

Giacomo-Terragni commented 1 year ago

When deploying the Main.sol contract using: tx_hash = YourContract.constructor().transact() The constructor requires two values: verifier and commitment. I believe that the verifier is the address of a deployed IVerifier contract, so the PlonkVerifier.sol needs to be deployed first. Is this correct? While for the commitment I believe it's an array that sets the boolean variables corresponding to the data provider's preferences. If this is the case what are the size and range of accepted values?

File: https://file.io/hbW8gHvlkwCD

klifish commented 1 year ago

You need to deploy smart contracts with LUCE APIs, which provide proper context for them