• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Which masternodes voted and what exactly voted on various proposals (v2)

xkcd said:
The code snippet posted by @demo doesn't work, it is missing a file ../jsall2.html and is in desperate need of re-factoring. I will have closer look and see if I can't do something with it...
Click to expand...
You are right. I will search for the jsall2.html in my computer, and send it to you.
 
Last edited:
xkcd said:
The code snippet posted by @demo doesn't work, it is missing a file ../jsall2.html and is in desperate need of re-factoring. I will have closer look and see if I can't do something with it...
Click to expand...
Ok.. I upload the file. Unzip it, and put it in the same directory with the script and dash-cli. Follow the instructions in the previous thread that was locked.

You should also substitute all the lines in the script ...
./dash-cli -datadir=/home/src/.dashcore-0.12.2.3
...with the appropriate datadir.

Report here if something went wrong.

I encourage everyone to run the script, because for decentralization reasons, the results should be cross checked.
 

Attachments

  • jsall2.html.zip
    54.1 KB · Views: 228
Last edited:
Thanks for attaching that zip, the script now runs to completion, though when I view the file called the_results_dashd_29-07-2018.html it does not show the proposals just the masternodes and the votehash. Regardless, I have written my own script to export the voting data and loaded to Oracle for number crunching, initial results look OK, but I need to play around with it to find the MNs that voted in exactly the same manner.
 
xkcd said:
Thanks for attaching that zip, the script now runs to completion, though when I view the file called the_results_dashd_29-07-2018.html it does not show the proposals just the masternodes and the votehash. Regardless, I have written my own script to export the voting data and loaded to Oracle for number crunching, initial results look OK, but I need to play around with it to find the MNs that voted in exactly the same manner.
Click to expand...

You should have dash-qt / dash-d up and running and synchronized, in order for the script to run properly. The script does not depend only on dashd, it also receives some information from dashcentral .org (which is the active proposals, because I could not get this info from sentinel).

Finally the script produces some logs in the standard output. You may post them here, if you want me to debug them.

I will run the script in my system (Dash Core version v0.12.2.3 ), check whether it works properly, and post the results here. I hope the results to be identical in your system and in mine, otherwise something very strange may happen.
 
Last edited:
demo said:
I will run the script in my system (Dash Core version v0.12.2.3 ), check whether it works properly, and post the results here. I hope the results to be identical in your system and in mine, otherwise something very strange may happen.
Click to expand...

It works for me.

Distribution of MNOs revealed at 29-7-2018
The first operator includes all people who abstain. All the rest are identified by the way they vote.
1 operator(s) control(s) 002525 masternode(s)
1 operator(s) control(s) 000118 masternode(s)
1 operator(s) control(s) 000114 masternode(s)
1 operator(s) control(s) 000081 masternode(s)
1 operator(s) control(s) 000075 masternode(s)
1 operator(s) control(s) 000055 masternode(s)
1 operator(s) control(s) 000053 masternode(s)
2 operator(s) control(s) 000046 masternode(s)
2 operator(s) control(s) 000045 masternode(s)
1 operator(s) control(s) 000044 masternode(s)
1 operator(s) control(s) 000042 masternode(s)
1 operator(s) control(s) 000040 masternode(s)
1 operator(s) control(s) 000034 masternode(s)
1 operator(s) control(s) 000030 masternode(s)
3 operator(s) control(s) 000025 masternode(s)
1 operator(s) control(s) 000020 masternode(s)
3 operator(s) control(s) 000018 masternode(s)
3 operator(s) control(s) 000017 masternode(s)
3 operator(s) control(s) 000016 masternode(s)
3 operator(s) control(s) 000015 masternode(s)
2 operator(s) control(s) 000014 masternode(s)
4 operator(s) control(s) 000012 masternode(s)
7 operator(s) control(s) 000011 masternode(s)
5 operator(s) control(s) 000010 masternode(s)
6 operator(s) control(s) 000009 masternode(s)
9 operator(s) control(s) 000008 masternode(s)
13 operator(s) control(s) 000007 masternode(s)
8 operator(s) control(s) 000006 masternode(s)
20 operator(s) control(s) 000005 masternode(s)
27 operator(s) control(s) 000004 masternode(s)
37 operator(s) control(s) 000003 masternode(s)
66 operator(s) control(s) 000002 masternode(s)
248 operator(s) control(s) 000001 masternode(s)

Have a look at the below attached file (best viewed with firefox browser). If there is an MNO that didnt vote the way the below file reveals, please say it. Because in that case something very serious (in terms of sychnronization of the dash network) may happen.
 

Attachments

  • the_results_dashd_29-07-2018.html.zip
    385 KB · Views: 215
Last edited:
demo said:
Distribution of MNOs revealed at 30-6-2018
The first operator includes all people who abstain. All the rest are identified by the way they vote.
1 operator(s) control(s) 002456 masternode(s)
1 operator(s) control(s) 000111 masternode(s)
Click to expand...
demo said:
Distribution of MNOs revealed at 29-7-2018
The first operator includes all people who abstain. All the rest are identified by the way they vote.
1 operator(s) control(s) 002525 masternode(s)
1 operator(s) control(s) 000118 masternode(s)
Click to expand...

Is the one who controlled 111 Masternodes at 30-6-2018, the same who controls 118 Masternodes now? This will be the subject of my next script (if the agents allow me, of course :p;)). A hash in his IP addresses, and some other similarities may help me in the investigation. Although my mnowatch site has been shut down, I still have in my computer the full record of all the votes since I started taking these statistics.

 
Last edited:
Thanks for posting, my output was corrupted as mentioned earlier, happy to discuss further on Discord, on in PM.
I am very interested in the distribution of DASH amongst holders in the network, I was hoping to find that the bear market would help redistrubute the coin to new players, but it may be having a centralising effect instead.
  • Looking at June and July, we had 499 individuals that hold 5 MNs or less, in July that number is 406. Meaning those that had 5 MNs or less 93 people have sold up and left.
  • Looking at the top now, number of operators holding 50 MN or more in June are 4 for a total of 318 MNs between them, in July, we have 5 operators with 496 MNs between them.
  • June unqiue MNOs are 576, in July number of unique operatos are 483.
The above three observations over the past month tell me we are further centralising the currency and the poor price peformance reflects that too.
 
xkcd said:
  • Looking at June and July, we had 499 individuals that hold 5 MNs or less, in July that number is 406. Meaning those that had 5 MNs or less 93 people have sold up and left.
  • Looking at the top now, number of operators holding 50 MN or more in June are 4 for a total of 318 MNs between them, in July, we have 5 operators with 496 MNs between them.
  • June unqiue MNOs are 576, in July number of unique operatos are 483.
Click to expand...
It's worth noting that we have 2525 MN's without votes it can be any number of unique MNOs from 1 to 2525 - you can't say definitely based only on voting.
Also if any MNO moves its collateral(s) - voting history will be erased for corresponding MNs and these MNs will be added to these 2525 without votes - so again: you can't say is MN sold or just moved (basing just on voting pattern).
 
InhumanPerfection said:
It's worth noting that we have 2525 MN's without votes it can be any number of unique MNOs from 1 to 2525 - you can't say definitely based only on voting.
Also if any MNO moves its collateral(s) - voting history will be erased for corresponding MNs and these MNs will be added to these 2525 without votes - so again: you can't say is MN sold or just moved (basing just on voting pattern).
Click to expand...
We have the IPs of these 2525 inactive MNOs and a voting record that last 8 months (preserved in the backup of the mnowatch site I keep). So we know whether those 2525 are unique MNOs( or not) in case some of them voted at least once (if we run the appropriate script on the recorded voting data). For those who didnt vote at least once the past 8 months, they are very probably controlled by centralised authorities who keep them inactive and ready to vote in case the dash community decides against their interests.

Its in the benefit of all the MNOs that hold 1-5 masternodes to be aware of this data. Unfortunately nobody funds a project like that.Not even the cost of 2 dash for presenting these data online.:rolleyes:
 
Last edited:
Well it looks like the Demo user has got himself banned, so I will be posting the voting data for this month. I have also taken some time to re-factor slightly his code and I will post it here for you so that others can run it too. When I ran it i noticed that i needed to install zip and bc. if your system is missing these programs you can get them the usual `sudo apt install zip bc` way no issues. Also, the script assumes you have a working dash-cli in your PATH, so prior to running be sure to add it to your PATH for most people that will look something like `PATH=$PATH:$HOME/.dashcore;export PATH` check by running `which dash-cli` should not give an error.

The file the_results_dashd_30-08-2018.html will take a time to render after you apply a filter or sort on a column, be patient and if prompted allow the javascript to continue running.


Distribution of MNOs revealed at 30-08-2018
The first operator includes all people who did not vote. All the rest are group by the way they uniquely voted.
1 operator(s) control(s) 002514 masternode(s)
1 operator(s) control(s) 000114 masternode(s)
1 operator(s) control(s) 000091 masternode(s)
1 operator(s) control(s) 000081 masternode(s)
1 operator(s) control(s) 000076 masternode(s)
2 operator(s) control(s) 000070 masternode(s)
1 operator(s) control(s) 000056 masternode(s)
1 operator(s) control(s) 000049 masternode(s)
1 operator(s) control(s) 000047 masternode(s)
2 operator(s) control(s) 000045 masternode(s)
1 operator(s) control(s) 000037 masternode(s)
1 operator(s) control(s) 000035 masternode(s)
1 operator(s) control(s) 000032 masternode(s)
2 operator(s) control(s) 000030 masternode(s)
1 operator(s) control(s) 000029 masternode(s)
2 operator(s) control(s) 000028 masternode(s)
2 operator(s) control(s) 000027 masternode(s)
1 operator(s) control(s) 000025 masternode(s)
3 operator(s) control(s) 000023 masternode(s)
2 operator(s) control(s) 000020 masternode(s)
1 operator(s) control(s) 000019 masternode(s)
2 operator(s) control(s) 000018 masternode(s)
2 operator(s) control(s) 000017 masternode(s)
2 operator(s) control(s) 000016 masternode(s)
2 operator(s) control(s) 000015 masternode(s)
3 operator(s) control(s) 000014 masternode(s)
2 operator(s) control(s) 000013 masternode(s)
4 operator(s) control(s) 000012 masternode(s)
6 operator(s) control(s) 000011 masternode(s)
8 operator(s) control(s) 000010 masternode(s)
5 operator(s) control(s) 000009 masternode(s)
7 operator(s) control(s) 000008 masternode(s)
11 operator(s) control(s) 000007 masternode(s)
9 operator(s) control(s) 000006 masternode(s)
23 operator(s) control(s) 000005 masternode(s)
20 operator(s) control(s) 000004 masternode(s)
27 operator(s) control(s) 000003 masternode(s)
62 operator(s) control(s) 000002 masternode(s)
202 operator(s) control(s) 000001 masternode(s)
 

Attachments

  • mnowatch.zip
    50.1 KB · Views: 235
  • the_results_dashd_30-08-2018.zip
    423.4 KB · Views: 257
Last edited:
Having a look at the distrbution numbers more closely and comparing to previous months, I get the below table. Data in the cells is the number of Operators, top row is number of masternodes.
Code: 
Number of Mastenodes
         1     1-5     >=50   No Votes   Uniquely Voted
--------------------------------------------------------
June     304   499     4      2456       576
July     248   398     6      2525       483
August   196   332     5      2631       442

This does seem to suggest a drop off in participation and reduction in the diversity of the DASH ecosystem, again likely due to the bear market and weak hands being shaken out.
 
Using same script I uploaded from 2 posts back, I am presenting the voting data from the September budget and vote distribution by MNO. When viewing the attached file the_results_dashd_29-09-2018.html be sure to be patient as the javascript takes a long time to refresh, just give it time and the page will update.

Distribution of MNOs revealed at 29-09-2018
The first operator includes all people who did not vote. All the rest are grouped by the way they uniquely voted.
1 operator(s) control(s) 002818 masternode(s)
1 operator(s) control(s) 000135 masternode(s)
1 operator(s) control(s) 000081 masternode(s)
1 operator(s) control(s) 000076 masternode(s)
2 operator(s) control(s) 000067 masternode(s)
1 operator(s) control(s) 000052 masternode(s)
1 operator(s) control(s) 000048 masternode(s)
1 operator(s) control(s) 000047 masternode(s)
2 operator(s) control(s) 000045 masternode(s)
1 operator(s) control(s) 000039 masternode(s)
1 operator(s) control(s) 000037 masternode(s)
1 operator(s) control(s) 000034 masternode(s)
1 operator(s) control(s) 000031 masternode(s)
2 operator(s) control(s) 000030 masternode(s)
1 operator(s) control(s) 000029 masternode(s)
1 operator(s) control(s) 000027 masternode(s)
1 operator(s) control(s) 000025 masternode(s)
2 operator(s) control(s) 000024 masternode(s)
1 operator(s) control(s) 000023 masternode(s)
1 operator(s) control(s) 000021 masternode(s)
1 operator(s) control(s) 000020 masternode(s)
1 operator(s) control(s) 000019 masternode(s)
1 operator(s) control(s) 000018 masternode(s)
1 operator(s) control(s) 000017 masternode(s)
1 operator(s) control(s) 000016 masternode(s)
2 operator(s) control(s) 000015 masternode(s)
3 operator(s) control(s) 000014 masternode(s)
3 operator(s) control(s) 000013 masternode(s)
5 operator(s) control(s) 000012 masternode(s)
3 operator(s) control(s) 000011 masternode(s)
8 operator(s) control(s) 000010 masternode(s)
4 operator(s) control(s) 000009 masternode(s)
7 operator(s) control(s) 000008 masternode(s)
13 operator(s) control(s) 000007 masternode(s)
9 operator(s) control(s) 000006 masternode(s)
17 operator(s) control(s) 000005 masternode(s)
20 operator(s) control(s) 000004 masternode(s)
31 operator(s) control(s) 000003 masternode(s)
55 operator(s) control(s) 000002 masternode(s)
183 operator(s) control(s) 000001 masternode(s)

Summary of the changes over the last few months.

Code: 
Number of Masternodes
           1     1-5    >=50   Not Voted  Uniquely Voted
--------------------------------------------------------
June      304   499     4      2456       576
July      248   398     6      2525       483
August    196   332     5      2631       442
September 183   306     6      2818       391
 

Attachments

  • the_results_dashd_29-09-2018.zip
    423.1 KB · Views: 285
xkcd said:
Using same script I uploaded from 2 posts back, I am presenting the voting data from the September budget and vote distribution by MNO. When viewing the attached file the_results_dashd_29-09-2018.html be sure to be patient as the javascript takes a long time to refresh, just give it time and the page will update.

Distribution of MNOs revealed at 29-09-2018
The first operator includes all people who did not vote. All the rest are grouped by the way they uniquely voted.
1 operator(s) control(s) 002818 masternode(s)
1 operator(s) control(s) 000135 masternode(s)
1 operator(s) control(s) 000081 masternode(s)
1 operator(s) control(s) 000076 masternode(s)
2 operator(s) control(s) 000067 masternode(s)
1 operator(s) control(s) 000052 masternode(s)
1 operator(s) control(s) 000048 masternode(s)
1 operator(s) control(s) 000047 masternode(s)
2 operator(s) control(s) 000045 masternode(s)
1 operator(s) control(s) 000039 masternode(s)
1 operator(s) control(s) 000037 masternode(s)
1 operator(s) control(s) 000034 masternode(s)
1 operator(s) control(s) 000031 masternode(s)
2 operator(s) control(s) 000030 masternode(s)
1 operator(s) control(s) 000029 masternode(s)
1 operator(s) control(s) 000027 masternode(s)
1 operator(s) control(s) 000025 masternode(s)
2 operator(s) control(s) 000024 masternode(s)
1 operator(s) control(s) 000023 masternode(s)
1 operator(s) control(s) 000021 masternode(s)
1 operator(s) control(s) 000020 masternode(s)
1 operator(s) control(s) 000019 masternode(s)
1 operator(s) control(s) 000018 masternode(s)
1 operator(s) control(s) 000017 masternode(s)
1 operator(s) control(s) 000016 masternode(s)
2 operator(s) control(s) 000015 masternode(s)
3 operator(s) control(s) 000014 masternode(s)
3 operator(s) control(s) 000013 masternode(s)
5 operator(s) control(s) 000012 masternode(s)
3 operator(s) control(s) 000011 masternode(s)
8 operator(s) control(s) 000010 masternode(s)
4 operator(s) control(s) 000009 masternode(s)
7 operator(s) control(s) 000008 masternode(s)
13 operator(s) control(s) 000007 masternode(s)
9 operator(s) control(s) 000006 masternode(s)
17 operator(s) control(s) 000005 masternode(s)
20 operator(s) control(s) 000004 masternode(s)
31 operator(s) control(s) 000003 masternode(s)
55 operator(s) control(s) 000002 masternode(s)
183 operator(s) control(s) 000001 masternode(s)

Summary of the changes over the last few months.

Code: 
Number of Masternodes
           1     1-5    >=50   Not Voted  Uniquely Voted
--------------------------------------------------------
June      304   499     4      2456       576
July      248   398     6      2525       483
August    196   332     5      2631       442
September 183   306     6      2818       391
Click to expand...


I ran the script in my dashd, during the three days period that the payment occurs, but the results and the distribution were not identical to yours.
I was wondering, what is the reason of this incompatibility?
 
Last edited:
Using same script I uploaded from 3 posts back, I am presenting the voting data from the October budget and vote distribution by MNO. When viewing the attached file the_results_dashd_30-10-2018.html be sure to be patient as the javascript takes a long time to refresh, just give it time and the page will update.

Distribution of MNOs revealed at 30-10-2018
The first operator includes all people who did not vote. All the rest are grouped by the way they uniquely voted.
1 operator(s) control(s) 002994 masternode(s)
1 operator(s) control(s) 000097 masternode(s)
1 operator(s) control(s) 000088 masternode(s)
1 operator(s) control(s) 000082 masternode(s)
1 operator(s) control(s) 000067 masternode(s)
1 operator(s) control(s) 000052 masternode(s)
1 operator(s) control(s) 000048 masternode(s)
1 operator(s) control(s) 000047 masternode(s)
1 operator(s) control(s) 000045 masternode(s)
2 operator(s) control(s) 000040 masternode(s)
1 operator(s) control(s) 000038 masternode(s)
1 operator(s) control(s) 000034 masternode(s)
1 operator(s) control(s) 000030 masternode(s)
1 operator(s) control(s) 000029 masternode(s)
1 operator(s) control(s) 000025 masternode(s)
1 operator(s) control(s) 000024 masternode(s)
1 operator(s) control(s) 000023 masternode(s)
2 operator(s) control(s) 000021 masternode(s)
1 operator(s) control(s) 000019 masternode(s)
1 operator(s) control(s) 000018 masternode(s)
1 operator(s) control(s) 000017 masternode(s)
2 operator(s) control(s) 000016 masternode(s)
2 operator(s) control(s) 000015 masternode(s)
4 operator(s) control(s) 000014 masternode(s)
2 operator(s) control(s) 000013 masternode(s)
6 operator(s) control(s) 000012 masternode(s)
4 operator(s) control(s) 000011 masternode(s)
9 operator(s) control(s) 000010 masternode(s)
6 operator(s) control(s) 000009 masternode(s)
8 operator(s) control(s) 000008 masternode(s)
12 operator(s) control(s) 000007 masternode(s)
10 operator(s) control(s) 000006 masternode(s)
15 operator(s) control(s) 000005 masternode(s)
23 operator(s) control(s) 000004 masternode(s)
32 operator(s) control(s) 000003 masternode(s)
57 operator(s) control(s) 000002 masternode(s)
157 operator(s) control(s) 000001 masternode(s)

Summary of the changes over the last few months.


Code: 
Number of Masternodes
           1     1-5    >=50   Not Voted  Uniquely Voted
--------------------------------------------------------
June      304   499     4      2456       576
July      248   398     6      2525       483
August    196   332     5      2631       442
September 183   306     6      2818       391
October   157   284     5      2994       371
 

Attachments

  • the_results_dashd_30-10-2018.html.zip
    402.5 KB · Views: 265
2994 didnt vote!!!!! :confused::confused::confused::eek::eek::eek:
What shall we do to them? o_O
Tax them for not voiting? :rolleyes::p
Seize their voting rights for the next budget cycle? :rolleyes: :cool:

Lets post a special proposal in the next budget saying:
"Those who will not vote into this proposal they are considered deads, and they will be taxed":D
 
Last edited:
colofi said:
2994 didnt vote!!!!! :confused::confused::confused::eek::eek::eek:
What shall we do to them? o_O
Tax them for not voiting? :rolleyes::p
Seize their voting rights for the next budget cycle? :rolleyes: :cool:

Lets post a special proposal in the next budget saying:
"Those who will not vote into this proposal they are considered deads, and they will be taxed":D
Click to expand...

Not so fast! There are legitimate reasons why a masternode may not vote, the best one at the moment is the pooled services, eg Neptune DASH they said they do not vote with their Mastenodes. Also, if we force a masternode to vote they may chose to throw a 'donkey vote' and mindlessly vote for anything which could have the side effect of making the voting more random. One thing that may improve voter turn out is a nicer way to do it, and that is what @jeffh is working on with his Dash Nexus. Hopefully that site better engages MNOs to vote as they should.
 
xkcd said:
Not so fast! There are legitimate reasons why a masternode may not vote, the best one at the moment is the pooled services, eg Neptune DASH they said they do not vote with their Mastenodes. Also, if we force a masternode to vote they may chose to throw a 'donkey vote' and mindlessly vote for anything which could have the side effect of making the voting more random. One thing that may improve voter turn out is a nicer way to do it, and that is what @jeffh is working on with his Dash Nexus. Hopefully that site better engages MNOs to vote as they should.
Click to expand...

We should mark those who officialy declare that they do not vote at all (Neptune e.t.c) and then the 10% that is required for a proposal to pass, should be calculated when we exclude Neptune e.t.c from the total MN population.
 
Perhaps masternodes could send a signal that they are pooled nodes to exempt themselves from voting, I dunno. Seems like people would rather not leak any more information. it's a though one. :p
 
xkcd said:
Perhaps masternodes could send a signal that they are pooled nodes to exempt themselves from voting, I dunno. Seems like people would rather not leak any more information. it's a though one. :p
Click to expand...

Yes of course, but the ideal is for the shared masternodes to be able to vote too.

It is not very complicated to add voting capabilities in a shared Masternode. Just ask the MNshareholders to give a separate dash address, even empty. Then assign to that address the number of the shares. Then they could use this address to vote. The outcome of the vote is the vote of the shared MN.

And guess what, there is already code that can implement the above. This is EXACTLY the functionality of the dashboost project of @Pasta. Almost the same code can be used. In the code of dashboost, just disable the "add proposal" capability of dashboost, load the proposals from dashcentral (automaticaly or even manually) and launch the service.

There is also the alternative solution to get the shares information from the masternode pool operator, and automate this. It is not a big deal, especially in case the sharedmasternode pool servers have a JSON interface
 
I post some data from the banned mnowatch github site.
I am afraid some of them are not accurate, because initially the shellscript took into account not only the active proposals but also the zombies ones.
This bug was fixed in the_results_dashd_01-04-2018.html and after.
They are .gz files.
 

Attachments

  • the_results_dashd_31-03-2018.html.gz.zip
    556.5 KB · Views: 296
  • the_results_dashd_31-05-2018.html.gz.zip
    421.5 KB · Views: 324
  • the_results_dashd_31-12-2017.html.gz.zip
    432.4 KB · Views: 308
Last edited:
You must log in or register to reply here.
Back
Top