Bitcoin Forum

Bitcoin => Bitcoin Technical Support => Topic started by: danuel on November 18, 2012, 10:58:39 AM



Title: Running bitcoin through TOR
Post by: danuel on November 18, 2012, 10:58:39 AM
sorry to be digging up the topic.
I am using TAILS (Debian + TOR + USB) and I'm having a little problem (or not).
To synchronize with the bitcoinApp takes a lot of time and only have about 3-5 active connections.

Is there any way to speed up the synchronization process bitcoinApp?


Title: Re: Running bitcoin through TOR
Post by: picobit on November 18, 2012, 12:54:48 PM
You can't, syncing is based on I/O speeds and CPU, not your network, but you may want to connect to some onion addressed bitcoin nodes, you read about that on the wiki
'

Your harddisk is likely to be the limitation - or your USB stick if that is where the database ends up.  And they can be sloooow.


Title: Re: Running bitcoin through TOR
Post by: kjj on November 18, 2012, 02:43:54 PM
Set up a RAM disk, copy your current blockchain files to that, start bitcoin using that for the data directory.  Wait for it to catch up, then shut down.  Copy the blockchain files back to your USB stick, start bitcoin from the normal data directory.

Starting from absolutely nothing, you can get the full chain in a few hours using tmpfs, assuming you can connect to a decent node for the IBD.


Title: Re: Running bitcoin through TOR
Post by: J-Norm on November 22, 2012, 10:34:56 PM
If you are using tails then the stock bitcoin client is probably not ideal. I would use electrum instead. There are some concerns that whoever is running the electrum server you connect to will be able to corralate your addresses to one wallet, so you want to take that into account regarding being anonymous.

I think there may be a way to tell it to use different servers for each address but I don't know how,

A blockchain.info account is also a good way to go, just store the uri with a good password on your encrypted persistence volume. If you don't want to be tie your addresses create a different blockchain.info account for each address, you can use "custom send" to make sure change always goes back to the same address.