raiden-contracts
raiden-contracts copied to clipboard
deployment_*.json should contain the relevant hash of `contracts.json`
Then an incident like https://github.com/raiden-network/raiden/issues/5122 can be prevented earlier. TravisCI can compare the hash stored in the deployment files against that stored in contracts.json
.
When we upgrade only the service contracts, we do not want to deploy the other contracts. So the stored hash must not be overall_hash
but the hashes of the relevant sources.
This means, each entry of contracts.json
must contain a hash for each deployment file. Currently, service
and raiden
.
- Does
contracts.json
contain one source hash for each bytecode? - Does
contracts.json
contain one hash forraiden
and another forservices
?