We are looking at different stats. Maybe you can help me rectify them as I don't want to spread misinformation. The data I am gathering is based on the debug.log from one of my masternodes that has been running since well before the spork activation.
Everytime a masternode is punished we see an entry like this:
2019-06-13 08:40:50 CDeterministicMNList: PoSePunish -- punished MN cfb62e8bcd113017553d4d69c0f033fe57eca40e5dd5d6b77f336df8b2377da5, penalty 0->3257 (max=4936)
If you count those up (e.g.
$ grep "PoSePunish" ~/.dashcore/debug.log | wc -l) you get: 1,755
But, I only want to count the number of unique masternodes punished, not the total number of punishments, so I have a python script to de-dupe based on masternode ID, and the unique count is: 1,178
Everytime a masternode is banned we see an entry like this:
2019-06-13 08:06:38 CDeterministicMNList: PoSePunish -- banned MN 1729b477c347852397a21f17e2df9b6a032998ec50a7b85f9892ebf7599028f1 at height 1086358
Again, a raw count gives: 452, but the unique count is actually: 442. The difference can potentially be explained by the number of masternodes revived because some of them may have been banned multiple times.
$ grep -i revive ~/.dashcore/debug.log | wc -l
159
Why do you think our information differs? I trust the debug.log more that the links you provided only because I'm looking directly at the debug.log and I'm not sure how those other sites are doing their calculations, but there is perhaps an error in my analysis. The number of active masternodes does seem to match the chart you provided:
[email protected]:~$ dash-cli masternode list addr | wc -l
4715
-2 = 4713 (don't count the curly brace lines in the JSON output)
Since I'm counting cumulative bans, the line is monotonic increasing which may be a little deceptive. But, the curve is tapering which is a good sign (once it's flat, no more bans are occurring). Interested to hear your feedback.
Rick