Distribution of masternodes according the voting hash.
(see
here for explanation)
Code:
curl -s https://demodun.github.io/mnowatch/the_results_dashd_24-02-2018.html| cut -f22 -d"<"|cut -f2 -d">"|grep -v [a-z]|grep -v [A-Z]| grep ^[0-9]|grep -v "-"|sort|uniq -c|sed -e s/'^ '/000/g|sed -s s/'000 '/000000/g|sed -e s/'000 '/00000/g|sed -s s/'000 '/0000/g|sort -r|cut -f1 -d" "|uniq -c
1 0002221
1 0000062
1 0000053
1 0000041
1 0000040
2 0000035
1 0000027
1 0000023
1 0000018
3 0000017
1 0000014
1 0000013
1 0000012
2 0000011
2 0000010
2 0000009
5 0000008
3 0000007
8 0000006
12 0000005
12 0000004
22 0000003
63 0000002
1647 0000001
There is a huge increase of unique masternodes (from
645 to 1647!)
Either it is true, or they adapted to my code in order to hide themselves.
Obviously the votehash is not enough, in order to spot the operators having multiple masternodes.
The R&D continues.
(
dandelion?)
P.S.
You may also be interested in some other queries
[1] ,
[2] that you can execute in the provided html data.
