summaryrefslogtreecommitdiff
path: root/91/f5f0506ab767ff61edbaf1bd3aaf9c42f3a13b
blob: deab107abada7135fcc88096b67174ac27d2d6c1 (plain)
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
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
Return-Path: <el33th4x0r@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 86AAE9D
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 14 Oct 2015 18:39:29 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qg0-f47.google.com (mail-qg0-f47.google.com
	[209.85.192.47])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C2BC31BE
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 14 Oct 2015 18:39:28 +0000 (UTC)
Received: by qgx61 with SMTP id 61so50957055qgx.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 14 Oct 2015 11:39:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=yPf1Ti8Ag2UWMbFToOMpMozGr0pSYiv5F6kXhKuw9o8=;
	b=jnav2GGVwi0piZR4MdDJvGfBusz24niAEaNvS++jUgMmh36JSXmiSA31oRafUHUIHk
	oNUoBH2Emqw4F1p8ldK6QfFHcmOh6i65oN+NskI1DHFJ8SBa2ISZwHaa9VthDBqUUzdS
	PvXieQHcBIWKIsvJBrFuTXw49yqvCQ8B8cw3LjHU6NYBxWZ21MwKW1FD1ak9CzXeoJ2w
	ZtYQgBIT2tJKWgvRPtRKv1+ZPRBEWaIgusAR8rYZC74G0yLSgskiqjdq91zmz+XVXqKL
	t3eea2/SWWaXAbajbFg/nLbci1WhupIme/AwSDwNGrbFU+oo1Nf4eLUg8FT116v2gt93
	w5eQ==
X-Received: by 10.141.28.2 with SMTP id f2mr6297668qhe.59.1444847968069; Wed,
	14 Oct 2015 11:39:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.81.149 with HTTP; Wed, 14 Oct 2015 11:39:08 -0700 (PDT)
In-Reply-To: <20151014182055.GC23875@mcelrath.org>
References: <CAPkFh0viwmkUvjo4Qj50TNnkA5kG3z-3dLGExjkmDacE4E49Ow@mail.gmail.com>
	<20151014182055.GC23875@mcelrath.org>
From: =?UTF-8?Q?Emin_G=C3=BCn_Sirer?= <el33th4x0r@gmail.com>
Date: Wed, 14 Oct 2015 14:39:08 -0400
Message-ID: <CAPkFh0uQjTijLdG=eicaotKYvPEcKqNZhqC5BmY45pYcRyhALQ@mail.gmail.com>
To: Bob McElrath <bob@mcelrath.org>
Content-Type: multipart/alternative; boundary=001a11423974e431bf052214e111
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: bitcoin-dev@lists.linuxfoundation.org, Ittay Eyal <ittay.eyal@cornell.edu>
Subject: Re: [bitcoin-dev] Bitcoin-NG whitepaper.
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2015 18:39:29 -0000

--001a11423974e431bf052214e111
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

>So it seems to me that all I need to do is figure out who the current
leader is,
>and DDoS him off the network to shut Bitcoin-NG down.

Good point. If NG is layered on top of Bitcoin, we'd retain all of Bitcoin
as is. This would confer all the benefits of Bitcoin's retrospective
blocks, as well as add the ability to mint microblocks with low latency in
between. And despite the phrase "the leader," the actual leader in NG is a
key, not a specific node. That makes it possible to deter DDoS attacks by
dynamically migrating where in the network the leader is operating in
response to an attack. Finally, DDoS attacks against miners are already
possible, but they seem rare, and I suspect it's at least partly because of
the success of Matt Corallo's high speed bitcoin relay network. Similar
defenses can apply here.

- egs



On Wed, Oct 14, 2015 at 2:20 PM, Bob McElrath <bob@mcelrath.org> wrote:

> So it seems to me that all I need to do is figure out who the current
> leader is,
> and DDoS him off the network to shut Bitcoin-NG down.
>
> This is a significant advantage to bitcoin's ex-post-facto blocks: no one
> knows
> where the next one will come from.  The only way to shut the network down
> is to
> shut all nodes down.
>
> Emin G=C3=BCn Sirer via bitcoin-dev [bitcoin-dev@lists.linuxfoundation.or=
g]
> wrote:
> > Hi everyone,
> >
> > We just released the whitepaper describing Bitcoin-NG, a new technique
> for
> > addressing some of the scalability challenges faced by Bitcoin.
> Surprisingly,
> > Bitcoin-NG can simultaneously increase throughput while reducing
> latency, and
> > do so without impacting Bitcoin's open architecture or changing its tru=
st
> > model. This post illustrates the core technique:
> >      http://hackingdistributed.com/2015/10/14/bitcoin-ng/
> > while the whitepaper has all the nitty gritty details:
> >      http://arxiv.org/abs/1510.02037
> >
> > Fitting NG on top of the current Bitcoin blockchain is future work that
> we
> > think is quite possible. NG is compatible with both Bitcoin as is, as
> well as
> > Blockstream-like sidechains, and we currently are not planning to compe=
te
> > commercially with either technology -- we see NG as being complementary
> to both
> > efforts. This is pure science, published and shared with the community =
to
> > advance the state of blockchains and to help them reach throughputs and
> > latencies required of cutting edge fintech applications. Perhaps it can
> be
> > adopted, or perhaps it can provide the spark of inspiration for someone
> else to
> > come up with even better solutions.
> >
> > We would be delighted to hear your feedback.
> > - Ittay Eyal and E. G=C3=BCn Sirer.
> >
> > !DSPAM:561e98cd301391127216946!
>
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
> >
> > !DSPAM:561e98cd301391127216946!
>
> --
> Cheers, Bob McElrath
>
> "For every complex problem, there is a solution that is simple, neat, and
> wrong."
>     -- H. L. Mencken
>
>

--001a11423974e431bf052214e111
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">&gt;So it seems to me that all I need to do is figure out =
who the current leader is,<div>&gt;and DDoS him off the network to shut Bit=
coin-NG down.</div><div><br></div><div>Good point. If NG is layered on top =
of Bitcoin, we&#39;d retain all of Bitcoin as is. This would confer all the=
 benefits of Bitcoin&#39;s retrospective blocks, as well as add the ability=
 to mint microblocks with low latency in between. And despite the phrase &q=
uot;the leader,&quot; the actual leader in NG is a key, not a specific node=
. That makes it possible to deter DDoS attacks by dynamically migrating whe=
re in the network the leader is operating in response to an attack. Finally=
, DDoS attacks against miners are already possible, but they seem rare, and=
 I suspect it&#39;s at least partly because of the success of Matt Corallo&=
#39;s high speed bitcoin relay network. Similar defenses can apply here.</d=
iv><div><br></div><div>- egs</div><div><br></div><div><br></div></div><div =
class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Oct 14, 2015 a=
t 2:20 PM, Bob McElrath <span dir=3D"ltr">&lt;<a href=3D"mailto:bob@mcelrat=
h.org" target=3D"_blank">bob@mcelrath.org</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">So it seems to me that all I need to do is figure ou=
t who the current leader is,<br>
and DDoS him off the network to shut Bitcoin-NG down.<br>
<br>
This is a significant advantage to bitcoin&#39;s ex-post-facto blocks: no o=
ne knows<br>
where the next one will come from.=C2=A0 The only way to shut the network d=
own is to<br>
shut all nodes down.<br>
<div><div class=3D"h5"><br>
Emin G=C3=BCn Sirer via bitcoin-dev [<a href=3D"mailto:bitcoin-dev@lists.li=
nuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>] wrote:<br>
&gt; Hi everyone,<br>
&gt;<br>
&gt; We just released the whitepaper describing Bitcoin-NG, a new technique=
 for<br>
&gt; addressing some of the scalability challenges faced by Bitcoin. Surpri=
singly,<br>
&gt; Bitcoin-NG can simultaneously increase throughput while reducing laten=
cy, and<br>
&gt; do so without impacting Bitcoin&#39;s open architecture or changing it=
s trust<br>
&gt; model. This post illustrates the core technique:<br>
&gt; =C2=A0 =C2=A0 =C2=A0<a href=3D"http://hackingdistributed.com/2015/10/1=
4/bitcoin-ng/" rel=3D"noreferrer" target=3D"_blank">http://hackingdistribut=
ed.com/2015/10/14/bitcoin-ng/</a><br>
&gt; while the whitepaper has all the nitty gritty details:<br>
&gt; =C2=A0 =C2=A0 =C2=A0<a href=3D"http://arxiv.org/abs/1510.02037" rel=3D=
"noreferrer" target=3D"_blank">http://arxiv.org/abs/1510.02037</a><br>
&gt;<br>
&gt; Fitting NG on top of the current Bitcoin blockchain is future work tha=
t we<br>
&gt; think is quite possible. NG is compatible with both Bitcoin as is, as =
well as<br>
&gt; Blockstream-like sidechains, and we currently are not planning to comp=
ete<br>
&gt; commercially with either technology -- we see NG as being complementar=
y to both<br>
&gt; efforts. This is pure science, published and shared with the community=
 to<br>
&gt; advance the state of blockchains and to help them reach throughputs an=
d<br>
&gt; latencies required of cutting edge fintech applications. Perhaps it ca=
n be<br>
&gt; adopted, or perhaps it can provide the spark of inspiration for someon=
e else to<br>
&gt; come up with even better solutions.<br>
&gt;<br>
&gt; We would be delighted to hear your feedback.=C2=A0<br>
&gt; - Ittay Eyal and E. G=C3=BCn Sirer.<br>
&gt;<br>
</div></div>&gt; !DSPAM:561e98cd301391127216946!<br>
<span class=3D""><br>
&gt; _______________________________________________<br>
&gt; bitcoin-dev mailing list<br>
&gt; <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@l=
ists.linuxfoundation.org</a><br>
&gt; <a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-=
dev" rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org=
/mailman/listinfo/bitcoin-dev</a><br>
&gt;<br>
&gt;<br>
</span>&gt; !DSPAM:561e98cd301391127216946!<br>
<br>
--<br>
Cheers, Bob McElrath<br>
<br>
&quot;For every complex problem, there is a solution that is simple, neat, =
and wrong.&quot;<br>
=C2=A0 =C2=A0 -- H. L. Mencken<br>
<br>
</blockquote></div><br></div>

--001a11423974e431bf052214e111--