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.
Guys I'm a bit worried about all these varying results we're seeing posted here. It currently has all the accuracy of a vote managed by a random number generator!
Forgetting all those fancy ./dashd commands for a moment, if I simply do a "masternode list votes" in my client (which has been upgraded to .23) and copy/paste the results into a spreadsheet, using the "Find All" function in Excel's "Find and Replace" I get the following:
YEA = 240
NAY = 14
ABSTAIN = 2289
Which totals to 2543
Which is pretty close to the 2546 masternodes currently showing on dashninja.pl
Soooo....someone needs to do a check whether the 680+ YEA's being noted in other postings is even remotely correct or there's a bug in either that calculation or the results I'm getting from a straight "masternode list votes" command inside the console of the .23 client.
Evan explain a bit earlier about this.
Did your daemon was always running (without stop) since the beginning of the vote?