From: John Smith <witchspace81@gmail•com>
To: Christian Decker <decker.christian@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Blitcoin? (Black Hat 2011)
Date: Fri, 5 Aug 2011 13:11:48 +0000 [thread overview]
Message-ID: <CAJNQ0ss3-AuTysZhi6KWcoXt=Om9QbvWEHFkvBXwdifXOBanCA@mail.gmail.com> (raw)
In-Reply-To: <CALxbBHXbgDqZc1W+NJDbD78MP45U_oLkFVed5f3xWmJJGm=gCA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]
On Fri, Aug 5, 2011 at 12:58 PM, Christian Decker <
decker.christian@gmail•com> wrote:
> While I do think that anonymity (or pseudonymity) is a nice feature, I
> don't think it deserves the full focus of the developers. The core of the
> protocol is about making transactions in a secure and fast way, not allowing
> everybody to be anonymous, whether they want to or not. TOR already is a
> good options for those that want to stay anonymous, and there is no need to
> pull support into the main client, if only a few will use it. I think very
> few of the developers actually claimed that Bitcoin is anonymous, and has
> never been a big advertising point from the "official" side of Bitcoin,
> network analysis has been always known to break anonymity.
>
Yes. Optionally layering Bitcoin over Tor/I2P is a much better option than
trying to replicate an onion network in Bitcoin itself. For one, traffic
analysis is much more difficult if your onion routing network contains
multiple kinds of traffic. Also it would complicate the core algorithm and
waste developer time. Doing anonymity *right* is very hard. So let's leave
it to the Tor/I2P people that know what they're doing.
>
> I see no need for action from the developer side.
>
Except the part about making the client/network more resistant against DDoS.
JS
[-- Attachment #2: Type: text/html, Size: 1761 bytes --]
next prev parent reply other threads:[~2011-08-05 13:11 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 [this message]
2011-08-05 5:55 ` John Smith
2011-08-05 13:07 ` Andy Parkins
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='CAJNQ0ss3-AuTysZhi6KWcoXt=Om9QbvWEHFkvBXwdifXOBanCA@mail.gmail.com' \
--to=witchspace81@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=decker.christian@gmail$(echo .)com \
/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