_ Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top up vote 1 down vote favorite I use Bitcoin Core v0.12.1 (64bit) for Windows as my desktop wallet for transactions on the regular web.I am just getting set up to use Tor.I would like to configure Bitcoin Core for use on Tor as well.When I opened Settings|Options|Network tabs I found a pre-checked marked box labeled "Allow incoming Connections" In addition to that I have checked marked the box labeled "Use Separate SOCKS5 proxy to reach peers via Tor hidden services" ProxyIP: 127.0.0.1 Port:9050.Is this all that I really need to do?I've been reading up on bitcoin.conf and the command line options.It all seems horribly complex.I'm just an average schmo not some power user.I wouldn't know which options to pick or what values to assign.I would appreciate any thoughts and suggestions on the subject.wallet bitcoin-core up vote 0 down vote Yes, following this guide should be all you need to do.

It sounds like you've already done that.Alternatively, I've found that it's cheap and easy to set up a TOR wifi access point that you can connect to, and then all network traffic is proxied over TOR.That way, neither your local computer nor your Bitcoin Core installation need any special configuration.Browse other questions tagged wallet bitcoin-core or ask your own question.It is possible to run Bitcoin as a Tor hidden service, and connect to such services.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 for how to properly configure Tor.The first step is running Bitcoin behind a Tor proxy.This will already make all outgoing connections be anonymized, but more is possible.In a typical situation, this suffices to run behind a Tor proxy: If you configure your Tor system accordingly, it is possible to make your node also reachable from the Tor network.

Add these lines to your /etc/tor/torrc (or equivalent config file): The directory can be different of course, but (both) port numbers should be equal to your bitcoind's P2P listen port (8333 by default).bitcoin calculator redditIn a typical situation, where you're only reachable via Tor, this should suffice: (obviously, replace the Onion address with your own).litecoin transaction fee rulesIt should be noted that you still listen on all devices and another node could establish a clearnet connection, when knowing your address.litecoin price expectationsTo mitigate this, additionally bind the address of your Tor proxy: If you don't care too much about hiding your node, and want to be reachable on IPv4 as well, use discover instead: 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: 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 authentication has been configured), Bitcoin Core automatically creates a hidden service to listen on.This will positively affect the number of available .onion nodes.This new feature is enabled by default if Bitcoin Core is listening (-listen), and requires a Tor connection to work.It can be explicitly disabled with -listenonion=0 and, if not disabled, configured using the -torcontrol and -torpassword settings.To show verbose debugging information, pass -debug=tor.Connecting to Tor's control socket API requires one of two authentication methods to be configured.For cookie authentication the user running bitcoind must have write access to the CookieAuthFile specified in Tor configuration.

In some cases this is preconfigured and the creation of a hidden service is automatic.If permission problems are seen with -debug=tor they can be resolved by adding both the user running tor and the user running bitcoind to the same group and setting permissions appropriately.On Debian-based systems the user running bitcoind can be added to the debian-tor group, which has the appropriate permissions.An alternative authentication method is the use of the -torpassword flag and a hash-password which can be enabled and specified in Tor configuration.If you are not using TOR, you're Bitcoin activity is PUBLIC and being tracked by 2 groups: those who want to control you (govts, banks, police, etc), and those who want to steal from you (thieves, competition, ex-spouse, etc).Here is a simple guide to using Tor for beginners.(self.Bitcoin)submitted by First download and install Tor browser bundle.Use the tor browser for ALL browsing, not only for things you want kept private.

This makes life harder for the spies.For Wallets: IF A WALLET DOES NOT SUPPORT TOR CONNECTIONS DO NOT USE IT.Prefer online wallets that use .onion sites as your activity cannot be logged by the exit nodes.Do not use blockchain.info mixer.It provides anonymity only against beginners and is expensive.Goto settings in your wallet, then network Enter SOCKS5 and under proxy enter 127.0.0.1 and port 9150.Note that the default port for Tor is usually 9050.For the browser bundle use 9150.You must start Tor Browser Bundle before opening the wallet for it to work.I would stay away from thin wallets as they have privacy problems (a big subject I don't have space for here).If you really want to use them, you MUST use Tor or you are publicly declaring the details of ALL your transactions.You are publicly declaring all your addresses (present and future) and tying them to your IP.Electurm, suspiciously, does not let you change the network settings until you have already connected to the internet (which kind of defeats the purpose).

To get around this you can force it to connect the first time through tor by running your Tor Browser first, then using a program like proxychains to open Electrum: proxychains electrum EDIT: I forgot to add that you should add: socks5 127.0.0.1 9150 to the bottom of: gedit /etc/proxychains.conf Under the heading: # defaults set to "tor" If you're not using a root terminal, use sudo before gedit.You can also open nautilus as root and update the file in GUI.That's a very basic start for those who don't use Tor and consequently have publicized all their Bitcoin transactions.Sorry but I don't use anything Microsoft or Apple as they are very enthusiastic NSA cheerleaders.Google is also a cheerleader, so be aware.Hopefully someone else can add instructions for Windoze users who don't have the time or desire to switch.If I have forgotten anything, please comment.EDIT: For the more advanced readers, please note that this is a beginners guide.It is not a blanket solution for all privacy and security issues.