Provide script to verify git branch matches proposed contracts system #5083
Assignees
Labels
Comments
mergify bot
pushed a commit
that referenced
this issue
Oct 8, 2020
### Description
Adds two bash wrappers around `verify-bytecodes`:
* `verify-deployed` checks that the current Celo contracts correspond to Solidity sources on a given branch.
* `verify-release` checks that after executing a given proposal, the onchain contracts will correspond to Solidity sources on a given branch.
### Other changes
Added a `-f` flag to several of our bash scripts, and modified `truffle-config` to take a `--forno` parameter that allows Truffle scripts to run with a Forno provider on testnets/the mainnet for which a Forno instance exists.
Added comments, cleaned up scripts.
### Tested
#### verify-deployed
celotooljs port-forward -e baklava
yarn verify-deployed -n baklava -b baklava -f
#### verify-release
git checkout rc1
yarn devchain generate-tar devchain.tar.gz
git checkout -
yarn devchain run-tar devchain.tar.gz
yarn make-release -a rc1 -b m-chrzan/bytecode-scripts -n development -p proposal.json -i example-initialize-data.json -r report.json
yarn verify-release -b m-chrzan/bytecode-scripts -n development -p proposal.json
### Related issues
- Fixes #5082
- Fixes #5083
### Backwards compatibility
+1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
yarn verify-proposal -b BRANCH -n NETWORK -p PROPOSALverifies that the Solidity source codes underpackages/protocol/contracts.onbranch BRANCH match the bytecodes deployed to NETWORK, including any changes that PROPOSAL would cause.Current Behavior
No such script.
The text was updated successfully, but these errors were encountered: