What is “Vote Execution Delay”?
The period of time after a vote passes before the vote can be executed.
For instance, if there is a Vote Execution Delay of 24 hours and a vote passes at 11:00 am on Monday, it cannot be executed until 11:00 am Tuesday.
An important factor of Execution Delay is that the people who vote yes on a proposal have their tokens locked until the end of the execution delay.
Rage Quitting*
In Dandelion Voting Instances, and it gives people time to exit our TE Commons if they disagree with a decision to change parameters, before the Parameters are changed. Specific to Dandelion Voting this parameter is also referred to as the *"Rage Quit Period".
For instance, if a Dandelion Voting instance is used to change the Exit Tribute from 5% to 30%, many people may want to sell their tokens before the proposal is executed. But the people that voted to raise the Exit Tribute to 30% would not be able to sell their tokens, because their tokens would be locked until the Vote Execution Delay is up.
Disputable Voting
In Disputable Voting there is no “Rage Quit” Mechanism. This is because with the launch of the Augmented Bonding Curve (ABC) participants can leave at any point and tokens will be redeemed based on the “Sell Curve” of the ABC.
So what do we need to talk about in this post?
Why is this important? In the case of Disputable Voting should there be a delay even if the outcome cannot be changed? What information should we use to decide the Vote Execution Delay?