diff options
author | MarcoFalke <falke.marco@gmail.com> | 2020-07-10 15:21:25 +0200 |
---|---|---|
committer | MarcoFalke <falke.marco@gmail.com> | 2020-07-12 07:15:42 +0200 |
commit | faa3d2eee1cc52b76f6eda8271691fdbff1baaa7 (patch) | |
tree | 5ae39897c08470785672c3e46fb0bd504729149a | |
parent | 4db44acf2d5d3b40943c94b3960f42838255b7ad (diff) |
doc: Remove release notes of backports
-rw-r--r-- | doc/release-notes-19219.md | 23 |
1 files changed, 0 insertions, 23 deletions
diff --git a/doc/release-notes-19219.md b/doc/release-notes-19219.md deleted file mode 100644 index b5ee885ddc..0000000000 --- a/doc/release-notes-19219.md +++ /dev/null @@ -1,23 +0,0 @@ -#### Changes regarding misbehaving peers - -Peers that misbehave (e.g. send us invalid blocks) are now referred to as -discouraged nodes in log output, as they're not (and weren't) strictly banned: -incoming connections are still allowed from them, but they're preferred for -eviction. - -Furthermore, a few additional changes are introduced to how discouraged -addresses are treated: - -- Discouraging an address does not time out automatically after 24 hours - (or the `-bantime` setting). Depending on traffic from other peers, - discouragement may time out at an indeterminate time. - -- Discouragement is not persisted over restarts. - -- There is no method to list discouraged addresses. They are not returned by - the `listbanned` RPC. That RPC also no longer reports the `ban_reason` - field, as `"manually added"` is the only remaining option. - -- Discouragement cannot be removed with the `setban remove` RPC command. - If you need to remove a discouragement, you can remove all discouragements by - stop-starting your node. |