aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohn Newbery <john@johnnewbery.com>2019-03-14 15:39:27 -0400
committerJohn Newbery <john@johnnewbery.com>2019-03-14 15:45:46 -0400
commita7563633d25a99bb3ef170aaaeccacf44990f2d9 (patch)
treedcc5dded96c601bde9f511a99edf99c25bcbdc21
parentda14d909849a42ac4b9f0f6908c2dd00d600dc2b (diff)
[docs] document BIP 61 deprecation
-rw-r--r--doc/release-notes.md17
1 files changed, 10 insertions, 7 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index 16146288da..a528a232af 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -78,13 +78,6 @@ Configuration option changes
documentation](https://github.com/bitcoin/bitcoin/blob/master/doc/zmq.md#usage)
for details.
-- The `enablebip61` option (introduced in Bitcoin Core 0.17.0) is
- used to toggle sending of BIP 61 reject messages. Reject messages have no use
- case on the P2P network and are only logged for debugging by most network
- nodes. The option will now by default be off for improved privacy and security
- as well as reduced upload usage. The option can explicitly be turned on for
- local-network debugging purposes.
-
- The `rpcallowip` option can no longer be used to automatically listen
on all network interfaces. Instead, the `rpcbind` parameter must also
be used to specify the IP addresses to listen on. Listening for RPC
@@ -181,6 +174,16 @@ Deprecated or removed RPCs
continue using `generate` in this version, restart bitcoind with the
`-deprecatedrpc=generate` configuration option.
+Deprecated P2P messages
+-----------------------
+
+- BIP 61 reject messages are now deprecated. Reject messages have no use
+ case on the P2P network and are only logged for debugging by most network
+ nodes. Furthermore, they increase bandwidth and can be harmful for privacy
+ and security. It has been possible to disable BIP 61 messages since v0.17
+ with the `-enablebip61=0` option. BIP 61 messages will be disabled by default
+ in a future version, before being removed entirely.
+
New RPCs
--------