j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMÄ<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=22.msg192#msg192">Quote from: BitcoinFX on February 01, 2010, 10:08:54 PM</a></div><div class="quote">"Your application (using socks5 on port xxxx) is giving Tor only an IP address. Applications that do DNS resolves themselves may leak information. Consider<br/>using Socks4A (e.g. via polipo or socat) instead."</div>Bitcoin is using ip-adresses, not hostnames, so there's no need for dns. Tor thinks that since bitcoin is trying to connect to an ip without looking it up through tors internal dns, it's using a regular dns.<br/><br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=22.msg192#msg192">Quote from: BitcoinFX on February 01, 2010, 10:08:54 PM</a></div><div class="quote">However, I still get occasional warnings for these ports 8333 (expected Bitcoin 'default') and 6667 (which if i'm not mistaken is an IRC port !?)</div>Bitcoin is using port 8333, even though it's relaying it through tor on port 9050.. <img alt="Tongue" border="0" src="/static/img/emoticons/tongue.gif"/><br/>6667 is irc, bitcoin uses an irc-server to distribute the nodelist. (If you know the ip of another computer running bitcoin, you can specify the -connect option to avoid using the nodelist).<br/><br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=22.msg192#msg192">Quote from: BitcoinFX on February 01, 2010, 10:08:54 PM</a></div><div class="quote">However, Bitcoin <i>must</i> try to connect with all nodes to check its not missing any blocks !<br/></div>No, it's enough if you're just connected to one single node, as long as it's got a copy of the longest block-chain.</div> text/html
https://whatsonchain.com/tx/7ffdffd018dbd12d1f0977b5d5311a63e295a7d8e63b8e0c5b47b936377f1cb7