From: John Smith <witchspace81@gmail•com>
To: Andy Parkins <andyparkins@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Blitcoin? (Black Hat 2011)
Date: Fri, 5 Aug 2011 13:19:23 +0000 [thread overview]
Message-ID: <CAJNQ0stJeFx0X+vHZfx-3SHt3=0JAho_kqDU44mZM613YuUaSA@mail.gmail.com> (raw)
In-Reply-To: <201108051407.06216.andyparkins@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
On Fri, Aug 5, 2011 at 1:07 PM, Andy Parkins <andyparkins@gmail•com> wrote:
> On 2011 August 05 Friday, Gavin Andresen wrote:
>
> 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.
>
Right, while it doesn't warrant completely changing the transport protocol
to UDP or implementing onion routing, I'm all for simple timing and order
randomization changes if they can make attacks like this less effective.
JS
[-- Attachment #2: Type: text/html, Size: 1089 bytes --]
prev parent reply other threads:[~2011-08-05 13:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 10:56 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
2011-08-05 13:19 ` John Smith [this message]
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='CAJNQ0stJeFx0X+vHZfx-3SHt3=0JAho_kqDU44mZM613YuUaSA@mail.gmail.com' \
--to=witchspace81@gmail$(echo .)com \
--cc=andyparkins@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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