Vote Execution Delay and what it means

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?

1 Like

Smart contracts cannot verify human conditions. The need for humans to verify illicit activity and or safe activity is always a process apart from computable agreements. The responsibility to settle disputes or “catch” bad actions or actors has to be a process controlled by humans. There are several steps in conflict resolution to solve the problem. One method is to utilize vote execution delay as a tool.

Conflict resolution is conceptualized as the methods and processes involved in facilitating the peaceful ending of conflict and retribution. The time involved from which a bad action was committed and solved and the amount of voters involved to settle the dispute can be delayed for due course to properly settle said dispute fairly and objectively.

How long is too long?
If the problem is clearly resolved quickly does the problem still need to be subjected to due process

Can there be a set minimum time for the delay mechanism?
What should that look like?

This will also be based on how many blocks are confirmed by the network to represent the time not actual days or weeks. So the dependency on the network and its block approval time will always be a heavier hand in managing time allocated. Having a delay in general to properly resolve an issue through a voting process based on the token weight of said voter to execute resolution already creates unknown stipulation

How many tokens are a minimum for resolution or max needed?

How many votes does the conflict need?

Can a few token holders be responsible for settling disputes or does this create a hierarchy of conflict managers?

A self appointed court of the few acting in stead governing outcomes. Should the token holders voting constantly change?

Should there be a voting carousel?

This is a ride by the way and everyone needs tokens to enjoy the trip. It was always a challenge for myself at the carnival on what to use my tickets for.? How to properly manage them so I could ride everything I wanted to and play carnie games. I loved trying to out hustle the carnies but unfortunately I ended up just spending too much money trying to prove a point…… What should we do?

1 Like