-
Notifications
You must be signed in to change notification settings - Fork 99
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
Meta SNIP for security council actions (part of the meta snip on security) #94
Conversation
SNIPS/snip-template copy.md
Outdated
|
||
- an L1 multisig | ||
- Add a timelock to Starknet core contracts on L1 + the ability for the security council's multisig to bypass it (for phase 1) | ||
- Add a pausable function only callable by the security council's multisig (for phase 2) |
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.
this approach doesn't fully make sense. Pausing should be an immediate action and going through a SC takes too long. A better approach is: give the pause button to a centralized entity, i.e. starkware foundation, and have the SC have the ability to unpause and revoke such permission if the foundation misbehaves. This is how it is implemented in OP Mainnet. It makes sense to do so since pausing is a reversible action
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 agree
Changing this SNIP to become all actions encompassed by the Security Council |
Closing this PR in favor of #93 since we merged all Security Council SNIPs into one |
Drafting the meta SNIP for Security Council as part of the Fête du SNIP
Part of Elias'PR