diff options
| -rw-r--r-- | doc/release-notes.md | 4 | ||||
| -rw-r--r-- | doc/tor.md | 7 |
2 files changed, 7 insertions, 4 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md index cf9edd9b08..81e6f36dbf 100644 --- a/doc/release-notes.md +++ b/doc/release-notes.md @@ -77,6 +77,10 @@ Tools and Utilities - Update `-getinfo` to return data in a user-friendly format that also reduces vertical space. (#21832) +- CLI `-addrinfo` now returns a single field for the number of `onion` addresses + known to the node instead of separate `torv2` and `torv3` fields, as support + for Tor V2 addresses was removed from Bitcoin Core in 22.0. (#22544) + Wallet ------ diff --git a/doc/tor.md b/doc/tor.md index 7d134b64e0..a1a64bfe6f 100644 --- a/doc/tor.md +++ b/doc/tor.md @@ -23,10 +23,9 @@ There are several ways to see your local onion address in Bitcoin Core: You may set the `-debug=tor` config logging option to have additional information in the debug log about your Tor configuration. -CLI `-addrinfo` returns the number of addresses known to your node per network -type, including Tor v2 and v3. This is useful to see how many onion addresses -are known to your node for `-onlynet=onion` and how many Tor v3 addresses it -knows when upgrading to Bitcoin Core v22.0 and up that supports Tor v3 only. +CLI `-addrinfo` returns the number of addresses known to your node per +network. This can be useful to see how many onion peers your node knows, +e.g. for `-onlynet=onion`. ## 1. Run Bitcoin Core behind a Tor proxy |