-
Notifications
You must be signed in to change notification settings - Fork 5
[DRAFT] V1 => V2 Contract Upgrade #32
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
Conversation
…ell as upgrade flow
…n_legacy into feat/token-upgrade
scripts/upgrade/upgrade-test.ts
Outdated
@@ -0,0 +1,70 @@ | |||
import * as hre from "hardhat"; |
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.
we need this to be a proper production ready script
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.
flows should be separated or withdraw flow removed, since we will use a Safe for the call.
We need at least one script that just does the upgrade and validation on any network.
81dce9b
to
f0c7ade
Compare
f0c7ade
to
18f6387
Compare
…and make a new test for full flow in upgrade
…oc. Also split and improve testing for full flow
State validation for V2 Upgrade
Add functionality to withdraw ERC20 token that is on the contract