diff options
| author | Jon Atack <jon@atack.com> | 2021-06-06 18:27:13 +0200 |
|---|---|---|
| committer | Jon Atack <jon@atack.com> | 2021-06-06 19:05:01 +0200 |
| commit | 49938eee9c338cd96e357a0dd51dcce934ceb212 (patch) | |
| tree | 5fa98fe233014f5a9742ec36c8237bca530607c9 | |
| parent | e033ca13794699cf4744e71647db75c583a9a600 (diff) | |
doc: update tor.md with removal of tor v2 support
| -rw-r--r-- | doc/tor.md | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/doc/tor.md b/doc/tor.md index 2640a6109b..7d134b64e0 100644 --- a/doc/tor.md +++ b/doc/tor.md @@ -5,6 +5,14 @@ It is possible to run Bitcoin Core as a Tor onion service, and connect to such s The following directions assume you have a Tor proxy running on port 9050. Many distributions default to having a SOCKS proxy listening on port 9050, but others may not. In particular, the Tor Browser Bundle defaults to listening on port 9150. See [Tor Project FAQ:TBBSocksPort](https://www.torproject.org/docs/faq.html.en#TBBSocksPort) for how to properly configure Tor. +## Compatibility + +- Starting with version 22.0, Bitcoin Core only supports Tor version 3 hidden + services (Tor v3). Tor v2 addresses are ignored by Bitcoin Core and neither + relayed nor stored. + +- Tor removed v2 support beginning with version 0.4.6. + ## How to see information about your Tor configuration via Bitcoin Core There are several ways to see your local onion address in Bitcoin Core: @@ -18,7 +26,7 @@ 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. +knows when upgrading to Bitcoin Core v22.0 and up that supports Tor v3 only. ## 1. Run Bitcoin Core behind a Tor proxy |