aboutsummaryrefslogtreecommitdiff
path: root/doc/tor.md
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2015-11-11 15:08:38 +0100
committerWladimir J. van der Laan <laanwj@gmail.com>2015-11-12 18:08:50 +0100
commit58ef0ffa9ef9c6ecd383040edbd5c5b6e0a63fef (patch)
tree9899998dbde3d1da4a6910f5f8f33a240769f60a /doc/tor.md
parent68ccdc4696cceade91ff0a78bd011a8437f15e8f (diff)
doc: update docs for Tor listening
- add new data directory files for 0.12 to doc/files.md - mention torcontrol in doc/tor.md
Diffstat (limited to 'doc/tor.md')
-rw-r--r--doc/tor.md17
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/tor.md b/doc/tor.md
index 594897f896..1d35a658bc 100644
--- a/doc/tor.md
+++ b/doc/tor.md
@@ -87,3 +87,20 @@ 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
+
+3. Automatically listen on Tor
+--------------------------------
+
+Starting with Tor version 0.2.7.1 it is possible, through Tor's control socket
+API, to create and destroy 'ephemeral' hidden services programmatically.
+Bitcoin Core has been updated to make use of this.
+
+This means that if Tor is running (and proper authorization is available),
+Bitcoin Core automatically creates a hidden service to listen on, without
+manual configuration. This will positively affect the number of available
+.onion nodes.
+
+This new feature is enabled by default if Bitcoin Core is listening, and
+a connection to Tor can be made. It can be configured with the `-listenonion`,
+`-torcontrol` and `-torpassword` settings. To show verbose debugging
+information, pass `-debug=tor`.