 Show Posts
|
|
Pages: [1]
|
.........
Before voting myself I'd like to see more discussion about this. Pros and cons vs current proposition.
The original proposal to introduce allocations from the block rewards were to fund development work, and other projects. It was a much higher amount than the current proposals. However, the funding is not just short-term. Its for the life of the protocol. If any of the devs drop out, for whatever reason, the project can afford to keep funding development or maintenance. The voting is controlled by the MNs through democracy. They will use the wisdom of the crowd based on their own selfish goals of making the network worth more. If development work or any other work not related to coding stops, the network is in danger of death by apathy. Maintaining development keeps momentum to towards mainstream adoption. Dash has to keep up a fast pace to catch-up with Bitcoins lead. If development slows down because people need to find other work to pay bills, bitcoin will keep extending its lead. Full time development on multiple fronts, paid for by the protocol, enables the project to keep reducing the gap Bitcoin has built-up. Handing over voting controls to MNs also removes central control. At 10%, I think that is on the low side for what the project aims to achieve - chasing after a $3bn giant, from $14m base. Good points. For this to be effective it is crucial that the community always insist in the perfectioning of this Decentralized Governance System, especially regarding funding, so that it won't ever turn into a DASH's foible. |
|
|
|
I am getting this here:
./dashd masternode list votes | grep -c NAY
12
./dashd masternode list votes | grep -c YEA
200
./dashd masternode list votes | grep -c ABSTAIN
2296
can you retry on next block ? Sure (these results from my hotwallet - putty)  http://oi62.tinypic.com/123y0hv.jpgIs it correct? (I hope there are no sensitive info left) |
|
|
|
|
I am getting this here:
./dashd masternode list votes | grep -c NAY
12
./dashd masternode list votes | grep -c YEA
200
./dashd masternode list votes | grep -c ABSTAIN
2296
|
|
|
|
I get different results:
YEA: 606
NAY: 5
ABSTAIN: 1872
Interesting. How are you checking results. dashd masternode list votes | grep -c YEA dashd masternode list votes | grep -c NAY dashd masternode list votes | grep -c ABSTAIN EDIT: My daemon wasn't updated. Your results were correct. Let me get this straight. 51% Yea is required to pass. However, 1872 Abstain? That means no pass. Or, are we saying 1872 have yet to vote because vote starts with default set to abstain? Or, are we saying 51% yea votes vs. nay votes, ignoring abstainers? Sorry, only got one brain cell, and its thinking about the one thing it likes to think about most. "Voting will begin immediately and be open for 2 weeks. We will consider the vote successful if at any time we have 51% of the masternodes support." https://dashtalk.org/threads/vote-self-sustainable-decentralized-governance-by-blockchain.4825So it means ABSTAIN counts as NAY. Relax, Evan words are not carved in stone. We are in the firsts steps of a huge change in crypto. we need to experiment, learn and change if necessary. My opinion is that the ABSTAIN don't count. Not for yes or for no. btw. welcome  Abstain shouldn't count for yay or nay but they shouldn't be ignored from the count either. The successful vote should require 51% of total nodes voting yay. If you only look for 51% support from nodes that actually vote, what happens if only a total of 500 nodes vote and 51% of those 500 are yay? Heck, what if only 10 nodes voted on something and 6 of those 10 voted yes? Only looking for 51% of the total votes that are either yay or nay isn't a fair system. Projects should be important enough to require an overall majority approval. If you cannot gain an overall majority, the project is not worth funding. Very correct. IF the community is PRO the change they must MANIFEST that clearly. There must be 51% YEA votes: ABSTAIN means no clear manifestation of YEA, ergo it must count as NAY. These rules (no matter what are the rules) should be agreed previously to all the votes, and the community must have some STANDARD rules, in order to avoid confusion/misunderstandings. That's our first time, as it is normal that we will eventually err and learn... it's drinking and learning... |
|
|
|
....
Hey Voter, Welcome. What a great first post for someone new around here  You're welcome  Not really new... I just don't like the BTCtalk at all  But as I've felt it was necessary, I answered the questions. Voting rules are VERY important, and must be SET without a doubt to voters previously to voting begins... Oh, BTW, congratulations for the 5K pages!!  I love DASH! |
|
|
|
I get different results:
YEA: 606
NAY: 5
ABSTAIN: 1872
Interesting. How are you checking results. dashd masternode list votes | grep -c YEA dashd masternode list votes | grep -c NAY dashd masternode list votes | grep -c ABSTAIN EDIT: My daemon wasn't updated. Your results were correct. Let me get this straight. 51% Yea is required to pass. However, 1872 Abstain? That means no pass. Or, are we saying 1872 have yet to vote because vote starts with default set to abstain? Or, are we saying 51% yea votes vs. nay votes, ignoring abstainers? Sorry, only got one brain cell, and its thinking about the one thing it likes to think about most. "Voting will begin immediately and be open for 2 weeks. We will consider the vote successful if at any time we have 51% of the masternodes support." https://dashtalk.org/threads/vote-self-sustainable-decentralized-governance-by-blockchain.4825So it means ABSTAIN counts as NAY. |
|
|
|
|
