Quote from: tammuz on September 06, 2017, 03:07:30 PM

Quote from: crypto_patriot on September 06, 2017, 01:10:44 PM

debug.log is SPECIFIC to your wallet. Ban scores and misbehaving peers are SPECIFIC to how peers/other masternodes are behaving with YOU.

To see the ban scores of all nodes (except yours) and how they are scored with their activity with the DAS Explorer IP specifically (154.16.7.191), see:
http://das.thecryptochat.net/network.php

"In every tree, there's a few bad apples." Wink

A month ago, 500 was a high ban score. Recently I saw 5,000,000 which was killing my debug.log. (5mil = minimum 50k entries in debug log!) Others also in the 1-2 mil score range. WTF?

Thank you for detailed reply!
What this "ban score" means? How this number calculated?

Since DAS is a Dash fork which is a fork of Litecoin which is a fork of Bitcoin, I tend to do all my information/debugging research with ALL of these cryptos to help better understand the background ops of the qt as well as masternode/node features and communication. The BEST answer I found regarding the calc of ban scores is here:
https://bitcoin.stackexchange.com/questions/44214/what-increases-a-nodes-banscore

Keep in mind that this is a unique calc done by each user on the network for their peers. Each IPs ban score, if not 0, can be different depending on how it communicates with you. For example, node 1 can have a ban score of 1000 with node 2 but node 1 may have a ban score of 100 with node 3 and a ban score of 0 with node4 with no communication or reason to increase ban. It depends on whether or not if there is communication between the nodes as peers and the accuracy and validity of the information shared and confirmed/disregarded. HIGH ban scores can also be an indicator of an attempted network attack, but it is usually non-maligned, unintentional issues with the misbehaving node that needs correcting (updated core, updated blockchain, port/network errors, etc). Basically, banning allows you to ignore the node for a certain amount of time (and decrease misbehaving entries in the debug.log!) and hopefully the issue gets corrected. (No way to communicate directly since anonymous peer-to-peer).

Some sort of masternode chat using the public key (address) as the user name would be awesome. Still anon but can share issues. SO many things can be done with DAS, which Dash and it's community are already doing, and other things unique and new.

Also, minor problems might have a ban value=1, where more serious issues=100 (50,000 log entries x 100 misbehaving value = 5mil ban score for example)
You can search for and find these entries in your debug.log. Search: "misbehaving" to see the offending IP:port and from>to score.

Hope this helps you as much as it helped me.

Regards,

c_p

DAS Donations: D6MUrL4Repv9NrynL3Ue1gFDwnYhBTbam2