diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2015-11-10 17:40:36 +0100 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2015-11-12 17:58:15 +0100 |
| commit | 68ccdc4696cceade91ff0a78bd011a8437f15e8f (patch) | |
| tree | 398ed09497aace66016f249171acab0d55df9ea3 /doc/release-notes.md | |
| parent | 09c1ae1c01076f64fe0654f371200668306e5e18 (diff) | |
doc: Mention Tor listening in release notes
Diffstat (limited to 'doc/release-notes.md')
| -rw-r--r-- | doc/release-notes.md | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md index fd034743e6..3d10a07912 100644 --- a/doc/release-notes.md +++ b/doc/release-notes.md @@ -151,6 +151,23 @@ mining with the getblocktemplate protocol to a pool: this will affect you at the pool operator's discretion, which must be no later than BIP65 achieving its 951/1001 status. +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`. + 0.12.0 Change log ================= |