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
|
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 72ACB259
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 9 Nov 2015 18:33:49 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qg0-f49.google.com (mail-qg0-f49.google.com
[209.85.192.49])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 3CC92142
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 9 Nov 2015 18:33:48 +0000 (UTC)
Received: by qgad10 with SMTP id d10so151091513qga.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 09 Nov 2015 10:33:47 -0800 (PST)
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=eIvcLHti1pBMz4alyA8BHwEPMEdDHCXHDziKvZnRckA=;
b=Ojf9p5lkgsbEpbkhXPcgh8vSxt9dcUTTrCcdEPfeVoSW9t/brLIDD2pg7v9IH09vtj
ZO4Oij10wVIIuhm4ROOYa9wRykxHgSxvWKUZ06SOBpuBMa46kaMAokOXDaPrIW2WuLBa
IeYeBlJcrW3Jv9E0V3RdpA+xvU3LPvS76Gg8FGYfomD755NxMwSIRjxdKjhsT7F+LEz8
WMe5Pb+5smuhxBnRX8PZ1l3HsUiGiYybVylAJB3DC/hZltltryTtblp6elnoFT3ku34o
Yt+pDDBHJMTYUJqDQ1JbO+uAmQMJpYBe+qoj6l4x/k9yfcJoI7EbXKWjbeBbBpNtmMTh
RYuA==
X-Received: by 10.141.23.20 with SMTP id z20mr33411798qhd.52.1447094027446;
Mon, 09 Nov 2015 10:33:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.19.132 with HTTP; Mon, 9 Nov 2015 10:33:27 -0800 (PST)
In-Reply-To: <CAPkFh0viwmkUvjo4Qj50TNnkA5kG3z-3dLGExjkmDacE4E49Ow@mail.gmail.com>
References: <CAPkFh0viwmkUvjo4Qj50TNnkA5kG3z-3dLGExjkmDacE4E49Ow@mail.gmail.com>
From: =?UTF-8?Q?Emin_G=C3=BCn_Sirer?= <el33th4x0r@gmail.com>
Date: Mon, 9 Nov 2015 13:33:27 -0500
Message-ID: <CAPkFh0vQ=c+r1e+UBpCL0B-nbytzvUW3x=5Chuo=8-Ywdfcr_A@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=001a11423c807671be05241fd53a
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
X-Mailman-Approved-At: Mon, 09 Nov 2015 19:03:01 +0000
Cc: 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: Mon, 09 Nov 2015 18:33:49 -0000
--001a11423c807671be05241fd53a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Hi everyone,
Thanks to everyone for a very friendly and scientifically-oriented
discussion. We have collated all the issues that have been raised related
to NG, and placed them in context, here:
http://hackingdistributed.com/2015/11/09/bitcoin-ng-followup/
Overall, NG has a unique insight: turning the block creation process upside
down can provide many benefits. Most notably, throughput can go as high as
the network will allow, providing scalability benefits that increase as the
network improves. There are many other side benefits, including fast
confirmations that are stronger than 0-conf in Core, and come much more
quickly than Core's 1-confirmations. And there are ancillary benefits as
well, such as resilience to fluctuations in mining power, and healthier
incentives for participants to ferry transactions. We believe that a fresh
new permission-less blockchain protocol, designed today, would end up
looking more like NG than Core. Of course, if NG could possibly be layered
on top of Bitcoin, that would be the ultimate combination.
Many thanks for an interesting discussion, and as always, we're happy to
hear constructive suggestions and feedback,
- egs
On Wed, Oct 14, 2015 at 2:02 PM, Emin G=C3=BCn Sirer <el33th4x0r@gmail.com>
wrote:
> Hi everyone,
>
> We just released the whitepaper describing Bitcoin-NG, a new technique fo=
r
> 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 trust 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 w=
e
> think is quite possible. NG is compatible with both Bitcoin as is, as wel=
l
> as Blockstream-like sidechains, and we currently are not planning to
> compete 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 solutio=
ns.
>
> We would be delighted to hear your feedback.
> - Ittay Eyal and E. G=C3=BCn Sirer.
>
>
--001a11423c807671be05241fd53a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi everyone,<div><br></div><div><span style=3D"font-size:1=
2.8px">Thanks to everyone for a very friendly and scientifically-oriented d=
iscussion. We have collated all the issues that have been raised related to=
NG, and placed them in context, here:</span><br></div><div><div style=3D"f=
ont-size:12.8px">=C2=A0 =C2=A0=C2=A0<a href=3D"http://hackingdistributed.co=
m/2015/11/09/bitcoin-ng-followup/" target=3D"_blank">http://hackingdistribu=
ted.com/2015/11/09/bitcoin-ng-followup/</a></div></div><div style=3D"font-s=
ize:12.8px"><br></div><div style=3D"font-size:12.8px">Overall, NG has a uni=
que insight: turning the block creation process upside down can provide man=
y benefits. Most notably, throughput can go as high as the network will all=
ow, providing scalability benefits that increase as the network improves. T=
here are many other side benefits, including fast confirmations that are st=
ronger than 0-conf in Core, and come much more quickly than Core's 1-co=
nfirmations. And there are ancillary benefits as well, such as resilience t=
o fluctuations in mining power, and healthier incentives for participants t=
o ferry transactions. We believe that a fresh new permission-less blockchai=
n protocol, designed today, would end up looking more like NG than Core. Of=
course, i<span style=3D"font-size:12.8px">f NG could possibly be layered o=
n top of Bitcoin, that would be the ultimate combination.</span></div><div =
style=3D"font-size:12.8px"><br>Many thanks for an interesting discussion, a=
nd as always, we're happy to hear constructive suggestions and feedback=
,<br></div><div style=3D"font-size:12.8px">- egs</div><div style=3D"font-si=
ze:12.8px"><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Wed, Oct 14, 2015 at 2:02 PM, Emin G=C3=BCn Sirer <span dir=3D=
"ltr"><<a href=3D"mailto:el33th4x0r@gmail.com" target=3D"_blank">el33th4=
x0r@gmail.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
dir=3D"ltr">Hi everyone,<div><br></div><div>We just released the whitepaper=
describing Bitcoin-NG, a new technique for addressing some of the scalabil=
ity challenges faced by Bitcoin. Surprisingly, Bitcoin-NG can simultaneousl=
y increase throughput while reducing latency, and do so without impacting B=
itcoin's open architecture or changing its trust model. This post illus=
trates the core technique:</div><div>=C2=A0 =C2=A0 =C2=A0<a href=3D"http://=
hackingdistributed.com/2015/10/14/bitcoin-ng/" target=3D"_blank">http://hac=
kingdistributed.com/2015/10/14/bitcoin-ng/</a></div><div>while the whitepap=
er has all the nitty gritty details:</div><div>=C2=A0 =C2=A0 =C2=A0<a href=
=3D"http://arxiv.org/abs/1510.02037" target=3D"_blank">http://arxiv.org/abs=
/1510.02037</a></div><div><br></div><div>Fitting NG on top of the current B=
itcoin blockchain is future work that we think is quite possible. NG is com=
patible with both Bitcoin as is, as well as Blockstream-like sidechains, an=
d we currently are not planning to compete commercially with either technol=
ogy -- we see NG as being complementary to both efforts. This is pure scien=
ce, published and shared with the community to advance the state of blockch=
ains and to help them reach throughputs and latencies required of cutting e=
dge fintech applications. Perhaps it can be adopted, or perhaps it can prov=
ide the spark of inspiration for someone else to come up with even better s=
olutions.</div><div><br></div><div>We would be delighted to hear your feedb=
ack.=C2=A0</div><div>- Ittay Eyal and E. G=C3=BCn Sirer.</div><div><br></di=
v></div>
</blockquote></div><br></div>
--001a11423c807671be05241fd53a--
|