-
Notifications
You must be signed in to change notification settings - Fork 373
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
Timelock Authorizer V2 #2221
Comments
(fwiw we did now about these things, the Certora review simply highlighted how hard they make it to understand the system). We also want some small features, such as a dedicated permission for canceling (for the emergency subdao), and improve event support for granters/revokers/etc. |
Can we close this now, after the last TimelockAuthorizer deployment? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Address issues found during the Certora audit, namely the difficulty of distinguishing between "grant/revoke" permissions and "regular" permissions, leading to potentially dangerous (and unrecoverable) situations, especially if the root account were compromised
The text was updated successfully, but these errors were encountered: