Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMV<div class="post">&gt; Can nodes on the network tell from which and or to which bitcoin <br/>&gt; address coins are being sent? Do blocks contain a history of where <br/>&gt; bitcoins have been transfered to and from?<br/><br/>Bitcoins are sent to and from bitcoin addresses, which are essentially random numbers with no identifying information.<br/><br/>When you send to an IP address, the transaction is still written to a bitcoin address.&nbsp; The IP address is only used to connect to the recipient's computer to request a fresh bitcoin address, give the transaction directly to the recipient and get a confirmation. <br/><br/>Blocks contain a history of the bitcoin addresses that a coin has been transferred to.&nbsp; If the identities of the people using the bitcoin addresses are not known and each address is used only once, then this information only reveals that some unknown person transferred some amount to someone else.<br/><br/>The possibility to be anonymous or pseudonymous relies on you not revealing any identifying information about yourself in connection with the bitcoin addresses you use.&nbsp; If you post your bitcoin address on the web, then you're associating that address and any transactions with it with the name you posted under.&nbsp; If you posted under a handle that you haven't associated with your real identity, then you're still pseudonymous.<br/><br/>For greater privacy, it's best to use bitcoin addresses only once.&nbsp; You can change addresses as often as you want using Options-&gt;Change Your Address.&nbsp; Transfers by IP address automatically use a new bitcoin address each time.<br/><br/>&gt; Can nodes tell which bitcoin addresses belong to which IP addresses?<br/><br/>No.<br/><br/>&gt; Is there a command line option to enable the sock proxy the first<br/>&gt; time that bitcoin starts?<br/><br/>In the next release (version 0.2), the command line to run it through a proxy from the first time is:<br/>bitcoin -proxy=127.0.0.1:9050<br/><br/>The problem for TOR is that the IRC server which Bitcoin uses to initially discover other nodes bans the TOR exit nodes, as all IRC servers do.&nbsp; If you've already connected once before then you're already seeded, but for the first time, you'd need to provide the address of a node as such:<br/>bitcoin -proxy=127.0.0.1:9050 -addnode=&lt;someipaddress&gt;<br/><br/>If someone running a node with a static IP address that can accept incoming connections could post their IP to use for -addnode, that would be great.<br/><br/>&gt; What happens if you send bitcoins to an IP address that has multiple<br/>&gt; clients connected through network address translation (NAT)?<br/><br/>Whichever one you've set your NAT to forward port 8333 to will receive it.&nbsp; If your router can change the port number when it forwards, you could allow more than one client to receive.&nbsp; For instance, if port 8334 forwards to a computer's port 8333, then senders could send to "x.x.x.x:8334" <br/><br/>If your NAT can't translate port numbers, there currently isn't a command line option to change the incoming port that bitcoin binds to, but I'll look into it.<br/></div> text/html