diff options
| author | Jon Atack <jon@atack.com> | 2021-07-30 09:41:39 +0200 |
|---|---|---|
| committer | Jon Atack <jon@atack.com> | 2021-08-03 12:12:47 +0200 |
| commit | 49d503aefa74f11e5d93432987fa3775ed82c979 (patch) | |
| tree | b5de9e14b30a816e2bf6f6415713f49056812d1f /doc/tor.md | |
| parent | 75ea9ecf11bfeb120c58dc6c62539021a94ef97c (diff) | |
| download | bitcoin-49d503aefa74f11e5d93432987fa3775ed82c979.tar.xz | |
doc: update -addrinfo in release-notes.md and tor.md
Diffstat (limited to 'doc/tor.md')
| -rw-r--r-- | doc/tor.md | 7 |
1 files changed, 3 insertions, 4 deletions
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 |