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
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
|
Return-Path: <tensiam@hotmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 9C80B3790
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 31 Jul 2019 14:53:28 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from EUR01-DB5-obe.outbound.protection.outlook.com
(mail-oln040092064036.outbound.protection.outlook.com [40.92.64.36])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 92D938A0
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 31 Jul 2019 14:53:27 +0000 (UTC)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
b=m/u8q8ArYJwEeuhkCkn11Vz2R60mqkKnVM7+4LY2HW2nRd3WrOCk6Oym1x7530y1cXGztY2yqZ/B310NTtZ0Ivae53AD1sC5E+UHQ87YAJYPmjF8Zn5uiNveNyW98yHlRYCOJf0b9JmC9KFDAaCI9L/XHUBXRRzukHhIpvpmCKSxX9Wtohx8abYDho/ThS3/6kHutugi44QLWvbv8VZDsdFMxUlwUrd3QObBWK55zjkgSdFbFb7nRAhnERAE4FfunL0eREpBHxEDCWcDTBwdu/61daB91KLL3IALgcr3tZuIAKnVVQ7skB6Gq9Cq4gYdIgJ5AXCZGXe5pJtA7SX02Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
s=arcselector9901;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=6uuZ2baCCdReM48m33OEZi62Dw0B7QqG/A2SYwGUBgg=;
b=JAJyYNZUWu7LwsQ9y1Min/Ozsu2Twli38mWXHrOMaH4zcp2Lv8VedXEEcRP4WAKPplyYhwL5Bj0ELmQ+FiyA5gS6J8wJ0fs/1liUKD8pJlbfpbDdoC+XG+cnBtxED1KpTjWfa6Ka10YpUZXWId2JjOuOojzKPmIAjiz68a7XrQxAlHK6+sqKymPCZaczp+vTbtj5riHdVSBl7M5W/L3EwArSJ82/0eCuwRGJdLBU2LRLlMpM8w3vTm5rr8eigVK7qYcyE5999VPEt99M446Zr9lwanZeW5mY6gsNgWxKt1miCtEszg0hzDRd/19b+tPtaDbrUhIzFhgBE6K5oSW2/w==
ARC-Authentication-Results: i=1; mx.microsoft.com
1;spf=none;dmarc=none;dkim=none;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com;
s=selector1;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=6uuZ2baCCdReM48m33OEZi62Dw0B7QqG/A2SYwGUBgg=;
b=KmFKun1jPxSeDqd1MV04eA81leA1MNEgTj+lHV2KJc2iqJW/AlL3lzWj7v2mRsvCwVO/1pL89hkXcJAu2Uol6k5JIda0TxoMAYSN8QbGWcvQz88MGWgaMFoX7aWArwcCaYiU1qzcwGXOruvrjGXNJGyHpE7OKRDKu4fvnNVYeRMPlzWPVF/H5BffCvjf8iK6qzQXO07JsZd4pAWJ6g0DP2I+7BEa7UVf/fryV/u/ePIBLCxyvhCEMR9Ght0U2moSM2X/Lgm1zxWV1gRVkkRMU+FYRA5Nf/E6N4g8AZqnM82CpmmSJ8rAERVtZSUv6hYkAUeKDnBewkRECHEGcQmQ2A==
Received: from HE1EUR01FT038.eop-EUR01.prod.protection.outlook.com
(10.152.0.54) by HE1EUR01HT183.eop-EUR01.prod.protection.outlook.com
(10.152.1.161) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2136.14;
Wed, 31 Jul 2019 14:53:25 +0000
Received: from DB6PR10MB1832.EURPRD10.PROD.OUTLOOK.COM (10.152.0.53) by
HE1EUR01FT038.mail.protection.outlook.com (10.152.1.93) with Microsoft
SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id
15.20.2136.14 via Frontend Transport; Wed, 31 Jul 2019 14:53:25 +0000
Received: from DB6PR10MB1832.EURPRD10.PROD.OUTLOOK.COM
([fe80::cc12:47f0:aa33:6b70]) by
DB6PR10MB1832.EURPRD10.PROD.OUTLOOK.COM
([fe80::cc12:47f0:aa33:6b70%3]) with mapi id 15.20.2115.005;
Wed, 31 Jul 2019 14:53:25 +0000
From: "Kenshiro []" <tensiam@hotmail.com>
To: Alistair Mann <al@pectw.net>, Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Thread-Topic: [bitcoin-dev] Add a moving checkpoint to the Bitcoin protocol
Thread-Index: AQHVR5sdyaW9NUkjL067/8euo+yr/KbkwSWAgAAJxaeAAAS0tw==
Date: Wed, 31 Jul 2019 14:53:25 +0000
Message-ID: <DB6PR10MB183271245AAE84FB9AC96474A6DF0@DB6PR10MB1832.EURPRD10.PROD.OUTLOOK.COM>
References: <DB6PR10MB1832329BC8D151DC18F1E6CEA6DF0@DB6PR10MB1832.EURPRD10.PROD.OUTLOOK.COM>,
<28454621.Lge63Ifvux@dprfs-d5766>,
<DB6PR10MB1832F1E966CD83BC662985BDA6DF0@DB6PR10MB1832.EURPRD10.PROD.OUTLOOK.COM>
In-Reply-To: <DB6PR10MB1832F1E966CD83BC662985BDA6DF0@DB6PR10MB1832.EURPRD10.PROD.OUTLOOK.COM>
Accept-Language: en-US, es-ES
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:8D9A6F0B07AD1BD363E5DEC95F82267BB9B0E56D03E6E637D52D31535394A851;
UpperCasedChecksum:8D38187F8CECF0216551484304F1DA359EA3EAB0BE337DDB8DA5D23228AD3E6A;
SizeAsReceived:6948; Count:42
x-tmn: [Cfd2Us8sYdo7rrfiLtjTWgp4uHIGPhWr]
x-ms-publictraffictype: Email
x-incomingheadercount: 42
x-eopattributedmessage: 0
x-microsoft-antispam: BCL:0; PCL:0;
RULEID:(2390118)(5050001)(7020095)(20181119110)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031323274)(2017031324274)(2017031322404)(1601125500)(1603101475)(1701031045);
SRVR:HE1EUR01HT183;
x-ms-traffictypediagnostic: HE1EUR01HT183:
x-microsoft-antispam-message-info: Sxd+gOaDAKEmwHpB7lvMu1q+Gthko8oRlh3VfRTGiAILiBPc+om0kCfVxafCo5PJdSC9qTRmxXD7/cERfJtzk03n0BEkFnhDZlSPgZCbCBgOz81PbYcQIf4gsPV7AEK+lOvrmy7uR1DxCdHPLejRJ4ZDetaKOYfX9hah0I94HHluIIy1NinMvxPrA2pLSJKX
Content-Type: multipart/alternative;
boundary="_000_DB6PR10MB183271245AAE84FB9AC96474A6DF0DB6PR10MB1832EURP_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: bf74db77-b88b-45ae-c22e-08d715c6d738
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Jul 2019 14:53:25.3804 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR01HT183
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE 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: Wed, 31 Jul 2019 18:20:06 +0000
Subject: Re: [bitcoin-dev] Add a moving checkpoint to the Bitcoin protocol
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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, 31 Jul 2019 14:53:28 -0000
--_000_DB6PR10MB183271245AAE84FB9AC96474A6DF0DB6PR10MB1832EURP_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
P.S.: To be clearer, in this example I set an N value of 144 blocks, which =
is approximately 24 hours.
________________________________
From: Kenshiro [] <tensiam@hotmail.com>
Sent: Wednesday, July 31, 2019 16:40
To: Alistair Mann <al@pectw.net>; Bitcoin Protocol Discussion <bitcoin-dev@=
lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Add a moving checkpoint to the Bitcoin protocol
>>> How would a (potentially, state-sponsored) netsplit lasting longer than=
N be
handled?
It would be detected by the community much before reaching the reorg limit =
of N blocks (it's 24 hours) so nodes could stop until the netsplit is fixed=
.
In the extreme case no one notice the network split during more than N bloc=
ks (24 hours) and there are 2 permanent forks longer than N, nodes from one=
branch could delete their local history so they would join the other branc=
h.
Regards,
________________________________
From: Alistair Mann <al@pectw.net>
Sent: Wednesday, July 31, 2019 15:59
To: Kenshiro [] <tensiam@hotmail.com>; Bitcoin Protocol Discussion <bitcoin=
-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Add a moving checkpoint to the Bitcoin protocol
On Wednesday 31 Jul 2019 12:28:58 Kenshiro [] via bitcoin-dev wrote:
> I would like to propose that a "moving checkpoint" is added to the Bitcoi=
n
> protocol. It's a very simple rule already implemented in NXT coin:
>
> - A node will ignore any new block under nodeBlockHeight - N, so the
> blockchain becomes truly immutable after N blocks, even during a 51% atta=
ck
> which thanks to the moving checkpoint can't rewrite history older than th=
e
> last N blocks.
How would a (potentially, state-sponsored) netsplit lasting longer than N b=
e
handled?
--
Alistair Mann
--_000_DB6PR10MB183271245AAE84FB9AC96474A6DF0DB6PR10MB1832EURP_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
color: rgb(0, 0, 0);">
P.S.: To be clearer, in this example I set an N value of 144 blocks, which =
is approximately 24 hours.</div>
<div>
<div id=3D"appendonsend"></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<br>
</div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" co=
lor=3D"#000000" style=3D"font-size:11pt"><b>From:</b> Kenshiro [] <tensi=
am@hotmail.com><br>
<b>Sent:</b> Wednesday, July 31, 2019 16:40<br>
<b>To:</b> Alistair Mann <al@pectw.net>; Bitcoin Protocol Discussion =
<bitcoin-dev@lists.linuxfoundation.org><br>
<b>Subject:</b> Re: [bitcoin-dev] Add a moving checkpoint to the Bitcoin pr=
otocol</font>
<div> </div>
</div>
<div dir=3D"ltr">
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
>>> <span>How would a (potentially, state-sponsored) netsplit=
lasting longer than N be
<br>
</span><span>handled? </span></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<span><br>
</span></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<span>It would be detected by the community much before reaching the reorg =
limit of N blocks (it's 24 hours) so nodes could stop until the netsplit is=
fixed. </span></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<span><br>
</span></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<span>In the extreme case no one notice the network split during more than =
N blocks (24 hours) and there are 2 permanent forks longer than N, n</span>=
odes from one branch could delete their local history so they would join th=
e other branch.</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<br>
</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
Regards,</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<br>
</div>
<div>
<div id=3D"x_appendonsend"></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<br>
</div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"x_divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" =
color=3D"#000000" style=3D"font-size:11pt"><b>From:</b> Alistair Mann <a=
l@pectw.net><br>
<b>Sent:</b> Wednesday, July 31, 2019 15:59<br>
<b>To:</b> Kenshiro [] <tensiam@hotmail.com>; Bitcoin Protocol Discus=
sion <bitcoin-dev@lists.linuxfoundation.org><br>
<b>Subject:</b> Re: [bitcoin-dev] Add a moving checkpoint to the Bitcoin pr=
otocol</font>
<div> </div>
</div>
<div class=3D"x_BodyFragment"><font size=3D"2"><span style=3D"font-size:11p=
t">
<div class=3D"x_PlainText">On Wednesday 31 Jul 2019 12:28:58 Kenshiro [] vi=
a bitcoin-dev wrote:<br>
<br>
> I would like to propose that a "moving checkpoint" is added =
to the Bitcoin<br>
> protocol. It's a very simple rule already implemented in NXT coin:<br>
> <br>
> - A node will ignore any new block under nodeBlockHeight - N, so the<b=
r>
> blockchain becomes truly immutable after N blocks, even during a 51% a=
ttack<br>
> which thanks to the moving checkpoint can't rewrite history older than=
the<br>
> last N blocks.<br>
<br>
How would a (potentially, state-sponsored) netsplit lasting longer than N b=
e <br>
handled? <br>
-- <br>
Alistair Mann<br>
<br>
</div>
</span></font></div>
</div>
</div>
</div>
</body>
</html>
--_000_DB6PR10MB183271245AAE84FB9AC96474A6DF0DB6PR10MB1832EURP_--
|
