Skip to content
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

Feature Proposal: Minimum Execution Delay #43

Open
ebrightfield opened this issue May 22, 2023 · 0 comments
Open

Feature Proposal: Minimum Execution Delay #43

ebrightfield opened this issue May 22, 2023 · 0 comments

Comments

@ebrightfield
Copy link

Problem:
Currently, a multisig proposal can be created, approved, and executed on very short time horizons. This means that at least in theory, an upgrade proposal to a program or some such sensitive operation could occur in a sufficiently short time horizon that interested parties have no time to notice, examine, and determine whether they want to remain involved in the protocol in question.

Solution:
Adding a (optional) minimum execution delay field to a transaction proposal could allow for enforcing a minimum time delay from the time of proposal to time of execution. This enhances the ability for Squads to add veracity to the claim that they will be trustworthy stewards of programs under their control.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant