1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <witchspace81@gmail.com>) id 1QpKBu-0007l6-BU
for bitcoin-development@lists.sourceforge.net;
Fri, 05 Aug 2011 13:11:54 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.160.175 as permitted sender)
client-ip=209.85.160.175; envelope-from=witchspace81@gmail.com;
helo=mail-gy0-f175.google.com;
Received: from mail-gy0-f175.google.com ([209.85.160.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1QpKBt-0007hv-MK
for bitcoin-development@lists.sourceforge.net;
Fri, 05 Aug 2011 13:11:54 +0000
Received: by gyg4 with SMTP id 4so1782253gyg.34
for <bitcoin-development@lists.sourceforge.net>;
Fri, 05 Aug 2011 06:11:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.8.10 with SMTP id 10mr3060605ybh.60.1312549908233; Fri, 05
Aug 2011 06:11:48 -0700 (PDT)
Received: by 10.150.52.5 with HTTP; Fri, 5 Aug 2011 06:11:48 -0700 (PDT)
In-Reply-To: <CALxbBHXbgDqZc1W+NJDbD78MP45U_oLkFVed5f3xWmJJGm=gCA@mail.gmail.com>
References: <CAJNQ0svWgFwZrra0gQFpxNLOPXk4RbKygeMUNPEA=k-Wqwa-ZA@mail.gmail.com>
<201108041038.47396.luke@dashjr.org>
<CABsx9T2tAeOp6RAb+Zb5zmzdSePZV90Uu=r4mzFc44d6ndbcnQ@mail.gmail.com>
<CAJNQ0stRrv4Yqf9ENszoXJE8+FpzwXZaGVDP=stZi27x4BRmmg@mail.gmail.com>
<CA+8xBpd0ud0Jn7Xxfw3C-WCH12WuB7k_W5x00Mj2EidemGoYpQ@mail.gmail.com>
<1312545697.19584.56.camel@mei>
<CALxbBHXbgDqZc1W+NJDbD78MP45U_oLkFVed5f3xWmJJGm=gCA@mail.gmail.com>
Date: Fri, 5 Aug 2011 13:11:48 +0000
Message-ID: <CAJNQ0ss3-AuTysZhi6KWcoXt=Om9QbvWEHFkvBXwdifXOBanCA@mail.gmail.com>
From: John Smith <witchspace81@gmail.com>
To: Christian Decker <decker.christian@gmail.com>
Content-Type: multipart/alternative; boundary=000e0cd2537c07bcd704a9c1d721
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: 1QpKBt-0007hv-MK
Cc: Bitcoin Development <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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 13:11:54 -0000
--000e0cd2537c07bcd704a9c1d721
Content-Type: text/plain; charset=ISO-8859-1
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
--000e0cd2537c07bcd704a9c1d721
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<br><br><div class=3D"gmail_quote">On Fri, Aug 5, 2011 at 12:58 PM, Christi=
an Decker <span dir=3D"ltr"><<a href=3D"mailto:decker.christian@gmail.co=
m">decker.christian@gmail.com</a>></span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex;">
While I do think that anonymity (or pseudonymity) is a nice feature, I don&=
#39;t think it deserves the full focus of the developers. The core of the p=
rotocol 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 g=
ood 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 n=
ever been a big advertising point from the "official" side of Bit=
coin, network analysis has been always known to break anonymity.<br>
</blockquote><div><br>Yes. Optionally layering Bitcoin over Tor/I2P is a mu=
ch better option than trying to replicate an onion network in Bitcoin itsel=
f. For one,=A0 traffic analysis is much more difficult if your onion routin=
g network contains multiple kinds of traffic. Also it would complicate the =
core algorithm and waste developer time. Doing anonymity *right* is very ha=
rd. So let's leave it to the Tor/I2P people that know what they're =
doing.<br>
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8=
ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>I see no need for action from the developer side.<br></blockquote><div>=
<br>Except the part about making the client/network more resistant against =
DDoS.<br><br>JS<br><br></div></div>
--000e0cd2537c07bcd704a9c1d721--
|
