diff options
author | Jon Atack <jon@atack.com> | 2020-10-15 12:00:56 +0200 |
---|---|---|
committer | Jon Atack <jon@atack.com> | 2020-12-16 22:58:10 +0100 |
commit | e1765d8b04fe1fb775f3750e0fa59f13a58eb176 (patch) | |
tree | 2b38297dbffd9607e336e5ca90637882342207c9 | |
parent | e3b474c548668b653a4868c7be67e09f58e2382f (diff) | |
download | bitcoin-e1765d8b04fe1fb775f3750e0fa59f13a58eb176.tar.xz |
doc: update tor.md address examples from onion v2 to v3
-rw-r--r-- | doc/tor.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/tor.md b/doc/tor.md index 12b5f70245..8fe87bdde6 100644 --- a/doc/tor.md +++ b/doc/tor.md @@ -72,7 +72,7 @@ should be equal to binding address and port for inbound Tor connections (127.0.0 In a typical situation, where you're only reachable via Tor, this should suffice: - ./bitcoind -proxy=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -listen + ./bitcoind -proxy=127.0.0.1:9050 -externalip=7zvj7a2imdgkdbg4f2dryd5rgtrn7upivr5eeij4cicjh65pooxeshid.onion -listen (obviously, replace the .onion address with your own). It should be noted that you still listen on all devices and another node could establish a clearnet connection, when knowing @@ -90,7 +90,7 @@ and open port 8333 on your firewall (or use -upnp). If you only want to use Tor to reach .onion addresses, but not use it as a proxy for normal IPv4/IPv6 communication, use: - ./bitcoind -onion=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -discover + ./bitcoind -onion=127.0.0.1:9050 -externalip=7zvj7a2imdgkdbg4f2dryd5rgtrn7upivr5eeij4cicjh65pooxeshid.onion -discover ## 3. Automatically listen on Tor |