Re: [Bitcoin-development] Tor and Bitcoin

2013-07-30 Thread Mike Hearn
Various ideas are possible: * Use the Tor SOCKS proxy in such a way that it creates a guaranteed independent circuit to a different exit node each time you connect. This gets you back to the slightly stronger clearnet heuristic of if I saw a bunch of peers announce my tx, then it's probably

Re: [Bitcoin-development] Tor and Bitcoin

2013-07-30 Thread Jeff Garzik
On Tue, Jul 30, 2013 at 8:41 AM, Mike Hearn m...@plan99.net wrote: * Talk the Tor protocol directly and have the app explicitly pick its own diverse set of exit nodes, one per p2p connection. This is likely to be complicated. Last time I looked Tor doesn't provide any kind of library or API.

Re: [Bitcoin-development] Tor and Bitcoin

2013-07-30 Thread Bazyli Zygan
Apparently that won't help. That's just embeding the existing tor code and rerouting internal Cocoa internet communication via tors proxy. What guys need is bigger configurability in tor itself. I can understand that. It's doable tough. Gosh, why a day has only 24h? :) /b grabhive.com

Re: [Bitcoin-development] Tor and Bitcoin

2013-07-30 Thread Wendell
Thank you Peter. Does this advice apply equally to both full and SPV nodes? At this point I'm merely curious, since we don't have the option to run bitcoinj over Tor right now anyway. -wendell grabhive.com | twitter.com/grabhive | gpg: 6C0C9411 On Jul 30, 2013, at 8:30 PM, Peter Todd wrote:

Re: [Bitcoin-development] Tor and Bitcoin

2013-07-30 Thread Peter Todd
On Tue, Jul 30, 2013 at 09:36:50PM +0200, Wendell wrote: Thank you Peter. Does this advice apply equally to both full and SPV nodes? At this point I'm merely curious, since we don't have the option to run bitcoinj over Tor right now anyway. Yes, although remember that in general SPV nodes