aboutsummaryrefslogtreecommitdiff
path: root/doc/tor.md
diff options
context:
space:
mode:
authorJon Atack <jon@atack.com>2021-04-22 12:17:42 +0200
committerJon Atack <jon@atack.com>2021-04-22 13:00:21 +0200
commit65f30e4c21e94b775853392b7e0de5c7fd3de488 (patch)
tree89a11641d4cee50334fdffda89133a98a00703c1 /doc/tor.md
parente7776e20ed0ddf41d15b3d2df87a92ea6666226c (diff)
downloadbitcoin-65f30e4c21e94b775853392b7e0de5c7fd3de488.tar.xz
doc: add -addrinfo troubleshooting section to tor.md
Diffstat (limited to 'doc/tor.md')
-rw-r--r--doc/tor.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/tor.md b/doc/tor.md
index e38ada5bd6..2640a6109b 100644
--- a/doc/tor.md
+++ b/doc/tor.md
@@ -15,6 +15,10 @@ 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 current and future Tor releases that support Tor v3 only.
## 1. Run Bitcoin Core behind a Tor proxy