From: Andy Parkins <andyparkins@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Blitcoin? (Black Hat 2011)
Date: Fri, 5 Aug 2011 14:07:05 +0100 [thread overview]
Message-ID: <201108051407.06216.andyparkins@gmail.com> (raw)
In-Reply-To: <CABsx9T2tAeOp6RAb+Zb5zmzdSePZV90Uu=r4mzFc44d6ndbcnQ@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 800 bytes --]
On 2011 August 05 Friday, Gavin Andresen wrote:
> "As reported, I've got a BitCoin deanonymization mechanism. It's not
> complicated.
>
> Connect to every node in the cloud, discoverable via sweeping/IRC/get_peers
> messages. The first IP to consistently relay transactions for a given
> identity, is the given identity.
Transaction forwarding could be randomised slightly, by randomising the
outgoing relay order; and adding a random delay between each forward. Even
the massively connected monitor can't represent _all_ the connections on every
real node, so it would have no way of knowing whether it got any transaction
from the originator or because it got a fast path through the first N nodes to
receive it.
Andy
--
Dr Andy Parkins
andyparkins@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-08-05 13:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 10:56 [Bitcoin-development] Blitcoin? (Black Hat 2011) John Smith
2011-08-04 14:14 ` Matt Corallo
2011-08-04 14:38 ` Luke-Jr
2011-08-05 1:16 ` Gavin Andresen
2011-08-05 5:37 ` John Smith
2011-08-05 5:52 ` Jeff Garzik
2011-08-05 12:01 ` Joel Joonatan Kaartinen
2011-08-05 12:58 ` Christian Decker
2011-08-05 13:11 ` John Smith
2011-08-05 5:55 ` John Smith
2011-08-05 13:07 ` Andy Parkins [this message]
2011-08-05 13:19 ` John Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201108051407.06216.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox