-
Notifications
You must be signed in to change notification settings - Fork 438
feat: v1.4.0 upgrade script #1244
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
ca8ac56
to
b9f6a4d
Compare
_permissionController: Env.proxy.permissionController(), | ||
_DEALLOCATION_DELAY: Env.MIN_WITHDRAWAL_DELAY(), | ||
_ALLOCATION_CONFIGURATION_DELAY: Env.ALLOCATION_CONFIGURATION_DELAY(), | ||
_version: Env.deployVersion() |
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.
What zeus variable does this correspond to? Is it ZEUS_VERSION
because that seems to be 1.3.1
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.
ZEUS_DEPLOY_TO_VERSION
}); | ||
|
||
deployImpl({ | ||
name: type(AVSDirectory).name, |
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 assuming this is only changes with the SignatureUtilsMixin
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.
Yup - basically have to add versioning everywhere
Motivation:
We need a script to upgrade preprod/testnet to
v1.4.0
. This upgrade upgrades ALL core contracts, in order to bring versioning on-chain. It also encompasses our internal audit fixes.Core:
Pods:
Permissions:
Strategies
Modifications:
Adds
v1.4.0
upgrade script. Similar to original upgrade script since we add versioning to all contracts.Removes
v1.2.0
upgrade script.Result:
Completed deploy script