aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2018-04-05 09:43:22 +0200
committerWladimir J. van der Laan <laanwj@gmail.com>2018-04-05 09:53:56 +0200
commit2b54155a459c235626fddc4495bb681b93d3dbc5 (patch)
tree42f499129091a510bc182e8aa11284353d158a0f
parentbd59c4395c504e7bddbce80048ed65a53fb26f67 (diff)
parenta5263fb5112bf1f9276c9db6cb6181d12ca905e6 (diff)
Merge #12877: doc: Use bitcoind in Tor documentation
a5263fb doc: Use bitcoind in Tor documentation (Indospace.io) Pull request description: Tree-SHA512: 9440bb4dc3d4e43332d7e10bbba2fc88ce74f69c17777f5448556d5b0d572e3095fc284c80ba5669e02fa64c5f2fc2b911cc53c33cb67c44334afc405f2b77ba
-rw-r--r--doc/tor.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/tor.md b/doc/tor.md
index a05979fca8..931c83abdd 100644
--- a/doc/tor.md
+++ b/doc/tor.md
@@ -31,7 +31,7 @@ outgoing connections be anonymized, but more is possible.
In a typical situation, this suffices to run behind a Tor proxy:
- ./bitcoin -proxy=127.0.0.1:9050
+ ./bitcoind -proxy=127.0.0.1:9050
2. Run a bitcoin hidden server
@@ -86,7 +86,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:
- ./bitcoin -onion=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -discover
+ ./bitcoind -onion=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -discover
3. Automatically listen on Tor
--------------------------------