Re: TOR and I2P

OK thanks riX.

So, once Bitcoin has connected to at least one node then the -connect option will eliminate the 6667 warnings.

Is Bitcoin using any kind of ‘peer exchange’ or DHT because this still does not seem to prevent the constant Tor ‘exit’ warnings and therefore Tor’s requirement to try a new ‘exit’ node for connection. (which is problematic ! For Tor anyway, not Bitcoin Wink ) This is really what I meant by “However, Bitcoin must try to connect with all nodes to check its not missing any blocks ?” I just communicated it incorrectly.

I2P would seem to be a much easier solution to implement to increase a Bitcoins users anonymity.
http://forum.i2p2.de/viewtopic.php?t=3946&sid=213e3cd998db98c4511675ecbba17af4

I’m also testing JonDonym http://anonymous-proxy-servers.net/ (only the paid services support socks !) However, they do accept paysafecards which can currently be brought in exchange for Bitcoins. 🙂

When using proxy port 9050, it will only make one attempt to connect to IRC, then give up, since it knows it will probably always fail because IRC servers ban all the TOR exit nodes.  If you’re using another port, it would assume it might be a regular old normal proxy and would keep retrying IRC at longer and longer intervals.  You should not use Polipo or Privoxy as those are http filters and caches that would corrupt Bitcoin’s messages if they make any changes.  Bitcoin might be trying to overcome it by reconnecting.  You should use port 9050.

As riX says, the “is giving Tor only an IP address. Apps that do DNS…” warnings are nothing to worry about.  Bitcoin doesn’t use DNS at all in proxy mode.

Since Bitcoin can’t get through to IRC through Tor, it doesn’t know which nodes are currently online, so it has to try all the recently seen nodes.  It tries to conserve connection attempts as much as possible, but also people want it to connect quickly when they start it up and reconnect quickly if disconnected.  It uses an algorithm where it tries an IP less and less frequently the longer ago it was successful connected.  For example, for a node it saw 24 hours ago, it would wait 5 hours between connection attempts.  Once it has at least 2 connections, it won’t try anything over a week old, and 5 connections it won’t try anything over 24 hours old.

6,493 total views, 3 views today

https://bitcointalk.org/index.php?topic=22.msg223#msg223