Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1QpDO7-00015f-1s for bitcoin-development@lists.sourceforge.net; Fri, 05 Aug 2011 05:56:03 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.47 as permitted sender) client-ip=209.85.213.47; envelope-from=witchspace81@gmail.com; helo=mail-yw0-f47.google.com; Received: from mail-yw0-f47.google.com ([209.85.213.47]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1QpDO6-0007yJ-B5 for bitcoin-development@lists.sourceforge.net; Fri, 05 Aug 2011 05:56:03 +0000 Received: by ywe9 with SMTP id 9so2001131ywe.34 for ; Thu, 04 Aug 2011 22:55:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.114.2 with SMTP id m2mr2869519ybc.3.1312523756857; Thu, 04 Aug 2011 22:55:56 -0700 (PDT) Received: by 10.150.52.5 with HTTP; Thu, 4 Aug 2011 22:55:56 -0700 (PDT) In-Reply-To: References: <201108041038.47396.luke@dashjr.org> Date: Fri, 5 Aug 2011 05:55:56 +0000 Message-ID: From: John Smith To: Gavin Andresen Content-Type: multipart/alternative; boundary=000e0cd48bc649697f04a9bbc013 X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (witchspace81[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (witchspace81[at]gmail.com) 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1QpDO6-0007yJ-B5 Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Blitcoin? (Black Hat 2011) X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2011 05:56:03 -0000 --000e0cd48bc649697f04a9bbc013 Content-Type: text/plain; charset=ISO-8859-1 > 3) The recipient re-broadcasts transactions (is Theymos right here?), > allowing both the sender and recipient to be found > Hm this would potentially allow getting the IP for any recipient Bitcoin address, given that a client with the private key connects to the network once in a while. Send them a transaction that is guaranteed to not be written into a block by a miner, then monitor who rebroadcasts it over a few days/weeks. I guess this could also be used to find out who has the stolen coins. JS --000e0cd48bc649697f04a9bbc013 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
3) The recipient re-broadcasts transactions (is Theym= os right here?), allowing both the sender and recipient to be found

Hm this would potentially allow getting t= he IP for any recipient Bitcoin address, given that a client with the priva= te key connects to the network once in a while.

Send them a transac= tion that is guaranteed to not be written into a block by a miner, then mon= itor who rebroadcasts it over a few days/weeks.

I guess this could also be used to find out who has the stolen coins.
JS

--000e0cd48bc649697f04a9bbc013--