-
Notifications
You must be signed in to change notification settings - Fork 935
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
Transaction guard #224
Comments
I am very much in favor of this. With this one could for example, always require a certain key to be part of the signatures when the value to be sent is above a certain limit. Regarding the security risks. They are at the same level as a wrong/malicious module. |
Add a transaction guard to can impose additional constraints for executing a transaction.
E.g. Safe configuration changes need to be announced beforehand or no delegate calls are allowed.
Open questions
The text was updated successfully, but these errors were encountered: