[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[ddink7]

I'm a little concerned that the entire MN network can reach 80%+ compliance with a protocol bump within 48 hours, but that 96 hours after an MN vote is initialized, we still have less than 50% participation...and the voting process is not that difficult (log into VPS, type "./dashd masternode vote yea" and log off VPS).

[xxxgoodgirls]

I'm a little concerned that the entire MN network can reach 80%+ compliance with a protocol bump within 48 hours, but that 96 hours after an MN vote is initialized, we still have less than 50% participation...and the voting process is not that difficult (log into VPS, type "./dashd masternode vote yea" and log off VPS).

What are we voting for? Should I update the client? I've been MIA for a while.

[splawik21]

I'm a little concerned that the entire MN network can reach 80%+ compliance with a protocol bump within 48 hours, but that 96 hours after an MN vote is initialized, we still have less than 50% participation...and the voting process is not that difficult (log into VPS, type "./dashd masternode vote yea" and log off VPS).

What are we voting for? Should I update the client? I've been MIA for a while.

https://dashtalk.org/threads/vote-self-sustainable-decentralized-governance-by-blockchain.4825/

update local wallet - no need for remote, start the node with command: masternode vote yea or nay, or masternode vote-many yea or nay

[salmion]

bump

I would urge everyone that owns a masternode to take the time and actually put a vote out
which will directly influence the % for NEA and YEA votes.

Its time to bring the number of masternode owners  not having voted yet down people !!

Read more about the voting proposal here :

Original voting proposal :

https://dashtalk.org/threads/vote-self-sustainable-decentralized-governance-by-blockchain.4825/

Update on original proposal :

https://dashtalk.org/threads/vote-self-sustainable-decentralized-governance-by-blockchain.4825/page-4#post-53665

How To Vote :

To vote, simply copy your masternode.conf into your dash directory, open the software then execute the command “masternode vote-many yea” or “masternode vote-many nay”.

To vote with a single masternode you can use the command “masternode vote yea” or “masternode vote nay”.

How to view the voting results so far :

https://dashtalk.org/threads/halle-berrys-masternode-info-tools.3036/ (check the exspected payment per masternode / day)

How to view the results of your own voting :

https://dashninja.pl/mndetails.html?mnpubkey=YROWNMASTERNODEPUBKEY

[coins101]

I'm a little concerned that the entire MN network can reach 80%+ compliance with a protocol bump within 48 hours, but that 96 hours after an MN vote is initialized, we still have less than 50% participation...and the voting process is not that difficult (log into VPS, type "./dashd masternode vote yea" and log off VPS).

The vote is open for 2 weeks.

If you look at the Etherum sale, most were sold at the last minute. People were (conjecture) waiting to see what was what.

Then there are those that don't keep up with the threads (or go MIA, see above).

Being on the wrong protocol means you can get bumped off the network, so I guess people check for some things.

Also, abstain basically = no. What's to say no voters can't be bothered to vote, because they have by default?

[spatula]

So I setup the masternode.conf file so that I could vote with my masternodes without turning on my cold wallets and that worked great. If I can authorize a "vote-many" command with the masternode.conf file (and no cold wallets) why cant the same setup work for the "start-many" command?

[eduffield]

So I setup the masternode.conf file so that I could vote with my masternodes without turning on my cold wallets and that worked great. If I can authorize a "vote-many" command with the masternode.conf file (and no cold wallets) why cant the same setup work for the "start-many" command?

start-many signs the actual 1000DRK keys, which then authorizes a secondary key for the masternodes to communicate with. When you use vote many, it's signing messages with that secondary key, so you don't need access to the cold wallet.

[spatula]

So I setup the masternode.conf file so that I could vote with my masternodes without turning on my cold wallets and that worked great. If I can authorize a "vote-many" command with the masternode.conf file (and no cold wallets) why cant the same setup work for the "start-many" command?

start-many signs the actual 1000DRK keys, which then authorizes a secondary key for the masternodes to communicate with. When you use vote many, it's signing messages with that secondary key, so you don't need access to the cold wallet.

Is that secondary key the "masternodeprivkey" value? If so, once it has been created, could it not also be used to authorize the the masternode running on the network? This would allow me to keep my cold wallet, cold.

[ddink7]

I'm a little concerned that the entire MN network can reach 80%+ compliance with a protocol bump within 48 hours, but that 96 hours after an MN vote is initialized, we still have less than 50% participation...and the voting process is not that difficult (log into VPS, type "./dashd masternode vote yea" and log off VPS).

The vote is open for 2 weeks.

If you look at the Etherum sale, most were sold at the last minute. People were (conjecture) waiting to see what was what.

Then there are those that don't keep up with the threads (or go MIA, see above).

Being on the wrong protocol means you can get bumped off the network, so I guess people check for some things.

Also, abstain basically = no. What's to say no voters can't be bothered to vote, because they have by default?

It's true that abstain is a "soft" no, but all abstentions become irrelevant once the preset quorum is reached (in this case, 50%+1). I doubt abstention is presently being used as a negative voting strategy, since a "hard" no would be durable no matter how many people had voted. At this point, abstentions look like apathy.

P.S. I'm wondering of Otoh's 25% of the MN network has voted or not. If not, it could indicate that he is reluctant to overly influence the project (unlike what some detractors have said) in which case it implies that only 25% of the network is not participating.

[tungfa]

Voting status: Yea: 72.09%   Nay: 0.15%   Abstain: 28.06%
http://178.254.18.153/~pub/Darkcoin/masternode_payments_stats.html

Yeas:
1872
https://dashpay.io/binaries/current-vote.txt

[Jestah]

...
My ideas about "so many people haven't voted yet":
1. Some people want to feel like "the only decision maker" - to vote in last moment - so even with small amount of their MNs "determine the whole result by themselves".
...

Number 6: Voting apathy,complacency and lack of understanding of how to cast the vote.

Suggest having voting button on the top of the wallet that casts a Yea or Nay to make it as lemon squeezy as possible.
(highlights on detection of masternode status)

Bingo!!!   This should be as easy, along with all other functionality, as possible.    

[reflexmk]

I'm a little concerned that the entire MN network can reach 80%+ compliance with a protocol bump within 48 hours, but that 96 hours after an MN vote is initialized, we still have less than 50% participation...and the voting process is not that difficult (log into VPS, type "./dashd masternode vote yea" and log off VPS).

The vote is open for 2 weeks.

If you look at the Etherum sale, most were sold at the last minute. People were (conjecture) waiting to see what was what.

Then there are those that don't keep up with the threads (or go MIA, see above).

Being on the wrong protocol means you can get bumped off the network, so I guess people check for some things.

Also, abstain basically = no. What's to say no voters can't be bothered to vote, because they have by default?

It's true that abstain is a "soft" no, but all abstentions become irrelevant once the preset quorum is reached (in this case, 50%+1). I doubt abstention is presently being used as a negative voting strategy, since a "hard" no would be durable no matter how many people had voted. At this point, abstentions look like apathy.

P.S. I'm wondering of Otoh's 25% of the MN network has voted or not. If not, it could indicate that he is reluctant to overly influence the project (unlike what some detractors have said) in which case it implies that only 25% of the network is not participating.

And just like that, vote jumped from 48 to 72, thanks for asking

[wozzek23]

I'm a little concerned that the entire MN network can reach 80%+ compliance with a protocol bump within 48 hours, but that 96 hours after an MN vote is initialized, we still have less than 50% participation...and the voting process is not that difficult (log into VPS, type "./dashd masternode vote yea" and log off VPS).

The vote is open for 2 weeks.

If you look at the Etherum sale, most were sold at the last minute. People were (conjecture) waiting to see what was what.

Then there are those that don't keep up with the threads (or go MIA, see above).

Being on the wrong protocol means you can get bumped off the network, so I guess people check for some things.

Also, abstain basically = no. What's to say no voters can't be bothered to vote, because they have by default?

It's true that abstain is a "soft" no, but all abstentions become irrelevant once the preset quorum is reached (in this case, 50%+1). I doubt abstention is presently being used as a negative voting strategy, since a "hard" no would be durable no matter how many people had voted. At this point, abstentions look like apathy.

P.S. I'm wondering of Otoh's 25% of the MN network has voted or not. If not, it could indicate that he is reluctant to overly influence the project (unlike what some detractors have said) in which case it implies that only 25% of the network is not participating.

And just like that, vote jumped from 48 to 72, thanks for asking

If Otoh with his 600++ MNs just voted, you have your answer.

[Minotaur26]

Voting status: Yea: 72.09%   Nay: 0.15%   Abstain: 28.06%
http://178.254.18.153/~pub/Darkcoin/masternode_payments_stats.html

Yeas:
1872
https://dashpay.io/binaries/current-vote.txt

Great! This must be the first blockchain based voting process for a decentralized organization. I think this method will be used more in the future for many applications not only cryptocurrencies.

[AzzAz]

Ok so we can talk about something else now :-)

[salmion]

Ok so we can talk about something else now :-)

Hopefully with this out the way we can talk about the Dash Space Station proposal

And well done to all who made the right choice!

It is quite a thing..

When is the two weeks up? When does the dash decentralised governance voted in party start?

[Sapereaude]

Ok so we can talk about something else now :-)

Hopefully with this out the way we can talk about the Dash Space Station proposal

I call shotgun.

[aleix]

Voting status: Yea: 72.09%   Nay: 0.15%   Abstain: 28.06%
http://178.254.18.153/~pub/Darkcoin/masternode_payments_stats.html

Yeas:
1872
https://dashpay.io/binaries/current-vote.txt

History in the making (again) 

[TaoOfSaatoshi]

Voting status: Yea: 72.09%   Nay: 0.15%   Abstain: 28.06%
http://178.254.18.153/~pub/Darkcoin/masternode_payments_stats.html

Yeas:
1872
https://dashpay.io/binaries/current-vote.txt

History in the making (again) 

I'm sure we'll be making a lot of history along our journey!

Glad to see the DGBB's been passed. Now to see how it works in practice, and make adjustments if need be.

[salmion]

Ok so we can talk about something else now :-)

Hopefully with this out the way we can talk about the Dash Space Station proposal

I call shotgun.