I don’t understand. Of course all 2.0 features have to be implemented, they cannot just leave a half baked code base behind, because BKS holders will then be fully aware of what to expect from the development of their code base. So I sincerely hope that all this will be finished before abandoning it.
Unfortunately this is not so easy, because we will have to think about a new decision rule to let a motion pass. Right now it is 5001 “yes” votes within 10,000 blocks. So what would we do with “non” votes? If we apply the same decision rule then “non” will be just the same as “no”.
Let’s assume we instead apply a score to each vote, “no” = -1, “non” = 0, “yes” = 1. Then we calculate the sum over all scores in the last 10,000 blocks and look if this is greater than 0 … The problem with this method is that a single shareholder could decide for his own voting simply by not making anyone aware of it, so it will get 9999 “non” votes and one “yes”.
So you would need to define “voting participation”, i.e. only consider the last blocks where no “non” votes were set. This however means that you can block a motion from passing by simply voting “non” instead of “no” such that the participation rule is violated.
Increasing the block span dynamically would be another approach, but also suffers from disadvantages and would be a very critical protocol change (because min age / block maturity depend on it by design).
Not so simple, but I am with you that this shouldn’t be given up that easily and I am sure that this can be solved in some way.
