<p>The concept of <code>banscore</code> is mostly historical at this point in time. The original concept was that minor misconfiguration or implementation wouldn't cause the whole network to disconnect itself instantly from one another. Small violations would just be counted towards their ban score, with large violations (like sending invalid block data) resulting in immediate maximum score. </p>

<p>Today most events which will cause an increase in ban score are going to reach 100 either instantly or very quickly, so it serves almost no purpose. You, as a node operator, get no value out of peers which are misbehaving, so there's no reason to change this value upwards. If the peer to peer logic was to be implemented today any protocol violation would just result in disconnection.</p>

CC BY-SA 4.0
2020-03-16T18:46:07.020Z
I had a look through code and I see now that many items ban immediately to 100 as you say with a few exceptions.  Thanks for your answer.
Scalextrix
CC BY-SA 4.0
2020-03-16T19:50:27.857Z
Originally lots of things were 1,10 etc- but any failure will eventually lead to banning, so there’s little point delaying.
Claris
CC BY-SA 4.0
2020-03-16T14:00:43.673Z
2020-03-16T14:00:43.673Z
Claris
<p>What was the thought behind a banscore threshold of 100?  Why is that default, why not lower or higher?</p>

<p>In what legitimate circumstances would a node operator change the banscore for their node?</p>

<banscore>
Why does the banscore default to 100?
Scalextrix
# Why does the banscore default to 100?

(Asked by: username_0 on 2020-03-15)

What was the thought behind a banscore threshold of 100? Why is that default, why not lower or higher?

In what legitimate circumstances would a node operator change the banscore for their node?

**Tags:** banscore


---

## 1 answers

### Answer by username_1 on 2020-03-16. Score: 4 | Accepted answer

The concept of `banscore` is mostly historical at this point in time. The original concept was that minor misconfiguration or implementation wouldn't cause the whole network to disconnect itself instantly from one another. Small violations would just be counted towards their ban score, with large violations (like sending invalid block data) resulting in immediate maximum score.

Today most events which will cause an increase in ban score are going to reach 100 either instantly or very quickly, so it serves almost no purpose. You, as a node operator, get no value out of peers which are misbehaving, so there's no reason to change this value upwards. If the peer to peer logic was to be implemented today any protocol violation would just result in disconnection.

> **Comments:**
> **username_0**: I had a look through code and I see now that many items ban immediately to 100 as you say with a few exceptions.  Thanks for your answer.  
> **username_1**: Originally lots of things were 1,10 etc- but any failure will eventually lead to banning, so there’s little point delaying.  

---

