aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorW. J. van der Laan <laanwj@protonmail.com>2021-05-05 15:51:23 +0200
committerW. J. van der Laan <laanwj@protonmail.com>2021-05-05 15:52:00 +0200
commit23109cc5485b9ab51cf1b6e655ead2e472ce0005 (patch)
tree1554b6b31293e475353c417feeb531b19e7e7e89 /doc
parent75b3a32f033b609d3b0b1b921469f9c78952005a (diff)
parent65f30e4c21e94b775853392b7e0de5c7fd3de488 (diff)
downloadbitcoin-23109cc5485b9ab51cf1b6e655ead2e472ce0005.tar.xz
Merge bitcoin/bitcoin#21753: doc: add -addrinfo to tor docs
65f30e4c21e94b775853392b7e0de5c7fd3de488 doc: add -addrinfo troubleshooting section to tor.md (Jon Atack) Pull request description: Follow-up to #21595. ACKs for top commit: jarolrod: ACK 65f30e4c21e94b775853392b7e0de5c7fd3de488 practicalswift: ACK 65f30e4c21e94b775853392b7e0de5c7fd3de488 0xB10C: ACK 65f30e4c21e94b775853392b7e0de5c7fd3de488 theStack: ACK 65f30e4c21e94b775853392b7e0de5c7fd3de488 Tree-SHA512: d17fa007106b8f877d2632c99273c663a24f025febe52faec9b197c561df808fd6a92bb27992ccbf5c3cc0d82058a8c4b82a2f1b99325f0ddfdac5ef703ac7d7
Diffstat (limited to 'doc')
-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