-
Notifications
You must be signed in to change notification settings - Fork 5
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
Create proposal for guardCM and CM setTargetSelectors on guardCM and revoke CM's canceller role #89
Conversation
const values = new Array(2).fill(0); | ||
const callDatas = [ | ||
// CM is always able to schedule pause() and disableToken(token) function calls via the timelock | ||
// When the new owner address are known, add the CM.swapOwner method |
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.
Not sure about this one. The CM itself can't perform actions on itself after setting a guard. The timelock is able to change / swap owners via the governance vote.
const callDatas = [ | ||
// CM is always able to schedule pause() and disableToken(token) function calls via the timelock | ||
// When the new owner address are known, add the CM.swapOwner method | ||
guardCM.interface.encodeFunctionData("setTargetSelectors", [[treasuryAddress, treasuryAddress],[0x3f4ba83a, 0x23e27a64], [true, true]]), |
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 about ServiceManager pause function?
Create proposal