You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently a DAO I'm a part of had a proposal to execute a vesting contract. The prop was published and was about to pass when it was discovered that there was an error in the JSON messaging. We had re-vote turned off because we want the ability execute early if we get majority vote, but doesn't let us change in this circumstance where an issue was found. It was decided to let it pass and leave it permanently open for execution. It was accidentally executed. Fortunately the mistake proved to not be that big of an issue, but it could have been.
I propose a feature whereby a DAO upon discovering an error with a prop can post a new prop to self-veto the prop with the error effectively closing it and making it such that it can't be executed.
The text was updated successfully, but these errors were encountered:
Recently a DAO I'm a part of had a proposal to execute a vesting contract. The prop was published and was about to pass when it was discovered that there was an error in the JSON messaging. We had re-vote turned off because we want the ability execute early if we get majority vote, but doesn't let us change in this circumstance where an issue was found. It was decided to let it pass and leave it permanently open for execution. It was accidentally executed. Fortunately the mistake proved to not be that big of an issue, but it could have been.
I propose a feature whereby a DAO upon discovering an error with a prop can post a new prop to self-veto the prop with the error effectively closing it and making it such that it can't be executed.
The text was updated successfully, but these errors were encountered: