Author

Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 2211. (Read 9723926 times)

legendary
Activity: 1288
Merit: 1000
Let's compare..

lebubar@118:~$ date ; ./SeeVotes.sh
Thu May  7 17:53:55 UTC 2015
YEA 681
NAY 14
ABSTAIN 1811

Edit:
The two method give different result :

lebubar@148:~$ ./dashd masternode list votes | grep -c YEA
681
lebubar@148:~$ ./dashd masternode list votes YEA | wc -l
683



newbie
Activity: 36
Merit: 0
I get this from a daemon updated an synced for a couple of hours:

NAY - 1
YEA - 47
ABSTAIN - 2452

I'm on v23 but it's a normal daemon. Does it need to be a masternode (hot/cold) wallet to get the correct results?

I was getting weird results on one of my daemons, then I restarted it and get:

./dashd masternode list votes YEA | wc -l
664

./dashd masternode list votes NAY | wc -l
16

./dashd masternode list votes ABS | wc -l
1834

Maybe there's a bug? Try restarting your client and see if it shows the correct votes

My YEA count is at 660 and ABSTAIN is at 1831 at block 264992.

I have also noticed that the YEA count will occasionally decrease. Why would that happen? I've seen it a few times now.
legendary
Activity: 1052
Merit: 1004
PS. Votes don't sync when you open your client. So to watch the progress of the vote you must have had a client open before the vote started (any v11.2 would work), then update to v11.2.23 to see the correct count.

That's it. It is a clean install.

Thanks!

EDIT:

After updating one of the hot nodes to v23 the came as

NAY - 14
YEA - 671
ABSTAIN - 1819

legendary
Activity: 2548
Merit: 1245
i think the results may vary a bit due to masternodes perhaps updating to .23 ?
(active masternodes has dropped to 2497 too, indicating some are indeed most likely updating)
legendary
Activity: 1288
Merit: 1000
I get this from a daemon updated an synced for a couple of hours:

NAY - 1
YEA - 47
ABSTAIN - 2452

I'm on v23 but it's a normal daemon. Does it need to be a masternode (hot/cold) wallet to get the correct results?

I was getting weird results on one of my daemons, then I restarted it and get:

./dashd masternode list votes YEA | wc -l
664

./dashd masternode list votes NAY | wc -l
16

./dashd masternode list votes ABS | wc -l
1834

Maybe there's a bug? Try restarting your client and see if it shows the correct votes

PS. Votes don't sync when you open your client. So to watch the progress of the vote you must have had a client open before the vote started (any v11.2 would work), then update to v11.2.23 to see the correct count.

On a freshly restarted MN hot daemon I got this (some small difference):
lebubar@108:~$ ./dashd masternode list votes | grep -c YEA
663
lebubar@108:~$ ./dashd masternode list votes | grep -c NAY
14
lebubar@108:~$ ./dashd masternode list votes | grep -c ABST
1830

Edit : Lol it's changing quickly, I think people are voting... (671 YEA now)
newbie
Activity: 36
Merit: 0
I get this from a daemon updated an synced for a couple of hours:

NAY - 1
YEA - 47
ABSTAIN - 2452

I'm on v23 but it's a normal daemon. Does it need to be a masternode (hot/cold) wallet to get the correct results?

I was getting weird results on one of my daemons, then I restarted it and get:

./dashd masternode list votes YEA | wc -l
664

./dashd masternode list votes NAY | wc -l
16

./dashd masternode list votes ABS | wc -l
1834

Maybe there's a bug? Try restarting your client and see if it shows the correct votes

My YEA count is at 660 and ABSTAIN is at 1831 at block 264992.
legendary
Activity: 1288
Merit: 1000
So my masternodes are all in separate wallets (i know, i need to take the time to combine). Is there a way I can use the vote-many command or do I have to open each one of them up? Also, do I vote from the cold wallet or the masternode itself?

I think you should take time now to make a masternode.conf file with the correct information from your nodes.
This way you will be able to vote with any wallet.  Wink
Later you only need to consolidate your private keys in one wallet and use the masternode.conf file already created.


In your current situation it's my understanding that you need to vote from the cold wallet (real masternode)

I made the vote on the hot wallet. And it work just fine.
legendary
Activity: 1176
Merit: 1036
Dash Developer
I get this from a daemon updated an synced for a couple of hours:

NAY - 1
YEA - 47
ABSTAIN - 2452

I'm on v23 but it's a normal daemon. Does it need to be a masternode (hot/cold) wallet to get the correct results?

I was getting weird results on one of my daemons, then I restarted it and get:

./dashd masternode list votes YEA | wc -l
664

./dashd masternode list votes NAY | wc -l
16

./dashd masternode list votes ABS | wc -l
1834

Maybe there's a bug? Try restarting your client and see if it shows the correct votes

PS. Votes don't sync when you open your client. So to watch the progress of the vote you must have had a client open before the vote started (any v11.2 would work), then update to v11.2.23 to see the correct count.
legendary
Activity: 1176
Merit: 1000
next thing must be the reputation system. and internal market like BitShares. common you can copy it faster guys.
legendary
Activity: 1052
Merit: 1004
I get this from a daemon updated an synced for a couple of hours:

NAY - 1
YEA - 47
ABSTAIN - 2452

I'm on v23 but it's a normal daemon. Does it need to be a masternode (hot/cold) wallet to get the correct results?
legendary
Activity: 1442
Merit: 1018
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.jpg

Is it correct?

(I hope there are no sensitive info left)

You're on v22 not v23
newbie
Activity: 7
Merit: 0
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.jpg

http://oi62.tinypic.com/123y0hv.jpg

Is it correct?

(I hope there are no sensitive info left)
legendary
Activity: 1456
Merit: 1000
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 ?

Looks like two weeks is about right.

Trouble is, we need voter to keep posting ongoing results to keep momentum for those that have missed the initial notification.

This highlights an issue about those with nodes who don't use any regular communication channels or are on holiday, in hospital, tied to a bed, etc.

Maybe we need an alert system in place that gets flagged to MN holders.

However, I wouldn't go so far as having masternodes being labelled as having voted or not, or which way they did vote. Or having MN holders emailed.
legendary
Activity: 2548
Merit: 1245
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 ?
Are you sure you are on .23??

To vote .22 is OK, to see the result correctly you must be on .23

yes, make sure your server (hot wallet) is updated to .23 before doing this ...... my results come from .23 through PUTTY
legendary
Activity: 1052
Merit: 1004
I get this from a daemon updated an synced for a couple of hours:

NAY - 1
YEA - 47
ABSTAIN - 2452
legendary
Activity: 1288
Merit: 1000
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 ?
Are you sure you are on .23??

To vote .22 is OK, to see the result correctly you must be on .23
legendary
Activity: 2548
Merit: 1245
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 ?
newbie
Activity: 7
Merit: 0
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
legendary
Activity: 2548
Merit: 1245
i wonder how many of us voted under the influence of alcohol ... and yes a nice little red wine is also alcohol  Tongue
legendary
Activity: 1442
Merit: 1018


10 % ?? masternode vote nay
Sorry that I find too much.


Just think of all that funded development you can just port over to your clone.
Sorry I would take your criticisms more seriously if you were contributing to the code not just cloning.

And you won't say it's too much if you come up with something amazing that requires funding and said funding gets approved.

To compete in the global leagues without having to give in to seed funding it's a drop in the ocean.



Is just my opinion. And our code also has differences. e.g. QT Paperwallet, 5 min BlockTime, static reward.

lol, pretty awesome features. What did it take you, a few minutes to change a few variables around? Please.
Jump to: