-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scripts and unit tests for contract upgrade and ownership transfer #89
Conversation
I am now testing ownership/upgrade with a multisig. |
2907cca
to
f487ecf
Compare
##################################### | ||
|
||
: "${FIL_CALIBNET_RPC_URL:?FIL_CALIBNET_RPC_URL not set. Please export it and rerun.}" | ||
: "${FIL_CALIBNET_PRIVATE_KEY:?FIL_CALIBNET_PRIVATE_KEY not set. Please export it and rerun.}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Purely out of curiosity how do you get your private keys? In the past I've ended up needing to write my own script to extract from eth keystore since that design works hard to avoid extraction.
) | ||
|
||
# Extract the deployed address from JSON output | ||
PDP_VERIFIER_ADDRESS=$(echo "$DEPLOY_OUTPUT_VERIFIER" | jq -r '.deployedTo') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm having trouble parsing this on both OSX and linux. There is no deployedTo field in my output json. Have you gotten it working since making this change?
09ba0a4
to
ccab75e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Working!
@ZenGround0
Manually tested
_authorizeUpgrade
function in the upgradedPDPVerifier
contract always revert.This PR has unit tests for testing contract upgrade and ownership transfer and also scripts to do it all on calibnet.