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
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
|
Return-Path: <contact@taoeffect.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 2E8648EE
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 12 Jul 2017 19:42:52 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from homiemail-a3.g.dreamhost.com (homie.mail.dreamhost.com
[208.97.132.208])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0CEAF3CF
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 12 Jul 2017 19:42:50 +0000 (UTC)
Received: from homiemail-a3.g.dreamhost.com (localhost [127.0.0.1])
by homiemail-a3.g.dreamhost.com (Postfix) with ESMTP id 8BB2828408C;
Wed, 12 Jul 2017 12:42:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=taoeffect.com; h=
content-type:mime-version:subject:from:in-reply-to:date:cc
:message-id:references:to; s=taoeffect.com; bh=auwzuZE1Bcv2ueXiy
zSDxbc4UEg=; b=CEnhMsXxS3sSJy0+O1try90zKPhhFqGOxa4ZImYzauuOW+X+C
1I2RJpZpXE5bIOENOAoBF+Qa1s/pLz9281/E9k5TIfAi3jvFbhgfpY2Jqj/A5m2H
Pmwwh05Ot/odaEICSoBFeRIubf7VGxCaXu6bW+WPGcUWHFy2LBGsR91dwA=
Received: from [192.168.42.67] (184-23-252-118.fiber.dynamic.sonic.net
[184.23.252.118])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
(Authenticated sender: contact@taoeffect.com)
by homiemail-a3.g.dreamhost.com (Postfix) with ESMTPSA id 699AA28406C;
Wed, 12 Jul 2017 12:42:50 -0700 (PDT)
Content-Type: multipart/signed;
boundary="Apple-Mail=_9CC3A83C-54B5-4A51-A706-61B42BFEB002";
protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Tao Effect <contact@taoeffect.com>
In-Reply-To: <CAGL6+mGEBhn3fjTN5APX3kQjEFjGsG_2LEL_LgXiPOP=xoAZuQ@mail.gmail.com>
Date: Wed, 12 Jul 2017 12:42:49 -0700
X-Mao-Original-Outgoing-Id: 521581369.144068-727b04fe2fc80d5e134338b5d618fb3b
Message-Id: <18A9E11A-07B2-48B4-B4E7-66A563A97A13@taoeffect.com>
References: <0119661e-a11a-6d4b-c9ec-fd510bd4f144@gmail.com>
<CAAS2fgRDVgdMYZo776iLwbm23aGNDWL85YgD=yF=M-0_vqJ5nQ@mail.gmail.com>
<1c1d06a9-2e9f-5b2d-42b7-d908ada4b09e@gmail.com>
<A030CDEA-CB0F-40BF-9404-6BD091537BE1@taoeffect.com>
<08078429-089f-9315-2f76-a08121c5378c@gmail.com>
<D30D8852-EFF4-4AB3-9B97-53D622A1440A@taoeffect.com>
<CAGL6+mHNMF9-v_6_ruvvhOenXCCsVhoG3aHkGvioOb-a9fokCQ@mail.gmail.com>
<26FE0468-7049-4BE0-948F-D5E40FE2CBAC@taoeffect.com>
<CAGL6+mGEBhn3fjTN5APX3kQjEFjGsG_2LEL_LgXiPOP=xoAZuQ@mail.gmail.com>
To: Chris Stewart <chris@suredbits.com>
X-Mailer: Apple Mail (2.3273)
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, 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, 12 Jul 2017 19:44:47 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Updating the Scaling Roadmap
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, 12 Jul 2017 19:42:52 -0000
--Apple-Mail=_9CC3A83C-54B5-4A51-A706-61B42BFEB002
Content-Type: multipart/alternative;
boundary="Apple-Mail=_535F0622-0BBD-47E9-AAB3-DBCA118AB4C4"
--Apple-Mail=_535F0622-0BBD-47E9-AAB3-DBCA118AB4C4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
> I think Paul has been pretty upfront about the risks of his model.
I think he has been rather misleading in his presentation of the risks.
He outlines them in a very technical manner, yes, but then goes on to =
promote them to lay people as if they're no big deal, which is =
completely misleading.
> By your account bitcoin is already insecure then -- it allows anyone =
can spend outputs that can be claimed by miners.
That is completely different.
It is disingenuous to say the two are remotely similar. The two =
situations have little-to-nothing in common.
In the present situation, anyone-can-spend outputs are used by probably =
less than 0.1% of users, and most software doesn't even allow for the =
possibility.
In Drivechain it's *encouraged-by-design*!
- Greg
--
Please do not email me anything that you are not comfortable also =
sharing with the NSA.
> On Jul 12, 2017, at 12:34 PM, Chris Stewart <chris@suredbits.com =
<mailto:chris@suredbits.com>> wrote:
>=20
> Hi Greg,
>=20
> The safest way to ensure everyone's protection to make sure *no one =
can do anything*. Then we will ALL be safe ;).
>=20
> >If so, please leave, you are compromising Bitcoin's security.
>=20
> Ok, let's calm down.
>=20
> >If I design a car that has a button that randomly causes the brakes =
to give out if pressed, is that a good idea? Can I justify pushing for =
such a "feature" just because it's "opt-in"?
>=20
> It would be more like "should we allow a car on the road if we know =
statistically that our brakes give out in every 1/100,000,000 cars"? =
There is security risks with everything in life -- we need to quantify =
the risk to see if it is worth taking. I think Paul has been pretty =
upfront about the risks of his model. I think you did a good job of =
demonstrating it in the email I cited too.
>=20
> >It is how *insecure* systems are designed.
>=20
> By your account bitcoin is already insecure then -- it allows anyone =
can spend outputs that can be claimed by miners.
>=20
> >Sure, happy to, as soon as I have it written up in detail.
>=20
> I look forward to this!
>=20
> -Chris
>=20
> On Wed, Jul 12, 2017 at 2:24 PM, Tao Effect <contact@taoeffect.com =
<mailto:contact@taoeffect.com>> wrote:
> Dear Chris,
>=20
>> I think this is an unfair characterization. You have to opt into =
using drivechains.
>=20
> I have heard this nonsense repeated countless times in order to =
justify adopting Drivechain.
>=20
> This is not how security works.
>=20
> A child can "opt-in" to using a loaded gun, but is it a good idea to =
make it easy for them to do that?
>=20
> No.
>=20
> This is effectively the same thing Drivechains is doing.
>=20
> It is a request to modify the Bitcoin protocol to make it easy for =
Bitcoin users to give their Bitcoins to miners.
>=20
> Does that sound like a good idea to anyone?
>=20
> If so, please leave, you are compromising Bitcoin's security.
>=20
> Security is about making it difficult to shoot yourself in the face.
>=20
> If I design a car that has a button that randomly causes the brakes to =
give out if pressed, is that a good idea? Can I justify pushing for such =
a "feature" just because it's "opt-in"?
>=20
> No. That is fallacy.
>=20
> It is not how secure systems are designed.
>=20
> It is how *insecure* systems are designed.
>=20
>> Care to share? I'm unaware if there is.
>=20
>=20
> Sure, happy to, as soon as I have it written up in detail.
>=20
> Kind regards,
> Greg Slepak
>=20
> --
> Please do not email me anything that you are not comfortable also =
sharing with the NSA.
>=20
>> On Jul 12, 2017, at 12:19 PM, Chris Stewart <chris@suredbits.com =
<mailto:chris@suredbits.com>> wrote:
>>=20
>> Hi Greg,
>>=20
>> >Here, you admit that the security of the sidechains allows miners to =
steal bitcoins, something they cannot do currently.
>>=20
>> If I put my coins in an anyone can spend output, a miner will take =
them. They can do this today. I suggest you try it if you don't believe =
me :-). You have to be more specific with contract types instead of =
generically talking about 'all contracts ever'.
>>=20
>> > Drivechain is an unmistakeable weakening of Bitcoin's security =
guarantees. This you have not denied.
>>=20
>> I think this is an unfair characterization. You have to opt into =
using drivechains. Other outputs such as P2PKH/Multisig etc are =
unaffected by a drivechain output. As Pieter Wuille stated earlier in =
this thread (and Paul has stated all along), drivechain outputs have a =
different security model than other contracts. Namely they are =
controlled by miners. I think we can all agree this is unfortunate, but =
it is the current reality we live in. I look forward to the day we can =
solve the 'ownership' problem so we can have trustless interoperable =
blockchains, but that day is not today.
>>=20
>> As a reminder, most users will not have to go through the drivechain =
withdrawal process. Most withdrawals will be done via atomic swaps.
>>=20
>> >There is no reason to weaken Bitcoin's security in such a dramatic =
fashion. Better options are being worked on, they just take time.
>>=20
>> Care to share? I'm unaware if there is.
>>=20
>> =
>https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-June/014600.=
html =
<https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-June/014600.=
html>
>>=20
>> Everyone should re-read this email though, this is something that =
could happen. Paul's design makes it so that if this occurs it is *VERY* =
obvious. I guess we can argue if there is any difference between an =
obvious robbery vs a hidden robbery, but I think if we have to pick one =
or the other the choice is clear to me. Other designs (that I'm aware =
of) for sidechains had attack vectors that weren't so obvious.
>>=20
>> -Chris
>>=20
>>=20
>>=20
>=20
>=20
--Apple-Mail=_535F0622-0BBD-47E9-AAB3-DBCA118AB4C4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=us-ascii
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"><meta http-equiv=3D"Content-Type" content=3D"text/html=
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D""><blockquote type=3D"cite" class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D""><div class=3D""><div class=3D"">I =
think Paul has been pretty upfront about the risks of his =
model.</div></div></div></div></blockquote><br class=3D""></div><div =
class=3D"">I think he has been rather misleading in his presentation of =
the risks.</div><div class=3D""><br class=3D""></div><div class=3D"">He =
outlines them in a very technical manner, yes, but then goes on to =
promote them to lay people as if they're no big deal, which is =
completely misleading.</div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div dir=3D"ltr" class=3D""><div class=3D"">By your account =
bitcoin is already insecure then -- it allows anyone can spend outputs =
that can be claimed by miners.</div></div></blockquote><div class=3D""><br=
class=3D""></div>That is completely different.<div class=3D""><br =
class=3D""></div><div class=3D"">It is disingenuous to say the two are =
remotely similar. The two situations have little-to-nothing in =
common.</div><div class=3D""><br class=3D""></div><div class=3D"">In the =
present situation, anyone-can-spend outputs are used by probably less =
than 0.1% of users, and most software doesn't even allow for the =
possibility.</div><div class=3D""><br class=3D""></div><div class=3D"">In =
Drivechain it's *encouraged-by-design*!<br class=3D""><div class=3D""><br =
class=3D""></div><div class=3D"">- Greg</div><div class=3D""><div =
class=3D"">
<span style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
line-height: normal; orphans: 2; widows: 2;" class=3D""><br =
class=3D"Apple-interchange-newline">--</span><br style=3D"color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal; orphans: 2; =
widows: 2;" class=3D""><span style=3D"color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal; orphans: 2; =
widows: 2;" class=3D"">Please do not email me anything that you are not =
comfortable also sharing</span><span style=3D"color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal; orphans: 2; =
widows: 2;" class=3D""> with the NSA.</span>
</div>
<br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Jul 12, 2017, at 12:34 PM, Chris Stewart <<a =
href=3D"mailto:chris@suredbits.com" class=3D"">chris@suredbits.com</a>>=
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D""><div class=3D""><div =
class=3D""><div class=3D"">Hi Greg,<br class=3D""><br class=3D"">The =
safest way to ensure everyone's protection to make sure *no one can do =
anything*. Then we will ALL be safe ;). <br class=3D""><br =
class=3D"">>If so, please leave, you are compromising Bitcoin's =
security.<br class=3D""><br class=3D""></div>Ok, let's calm down. <br =
class=3D""><br class=3D"">>If I design a car that has a button that =
randomly causes the brakes
to give out if pressed, is that a good idea? Can I justify pushing for=20=
such a "feature" just because it's "opt-in"?<br class=3D""><br =
class=3D"">It would be more like "should we allow a car on the=20
road if we know statistically that our brakes give out in every=20
1/100,000,000 cars"? There is security risks with everything in life --=20=
we need to quantify the risk to see if it is worth taking. I think Paul=20=
has been pretty upfront about the risks of his model. I think you did a =
good job of demonstrating it in the email I cited too.<br class=3D""><div =
class=3D""><br class=3D""></div></div>>It is how *insecure* systems =
are designed.<br class=3D""><br class=3D""></div>By your account bitcoin =
is already insecure then -- it allows anyone can spend outputs that can =
be claimed by miners.<br class=3D""><br class=3D"">>Sure, happy to, =
as soon as I have it written up in detail.<br class=3D""><br =
class=3D""></div><div class=3D"">I look forward to this! <br =
class=3D""></div><div class=3D""><br class=3D""></div>-Chris<br =
class=3D""></div><div class=3D"gmail_extra"><br class=3D""><div =
class=3D"gmail_quote">On Wed, Jul 12, 2017 at 2:24 PM, Tao Effect <span =
dir=3D"ltr" class=3D""><<a href=3D"mailto:contact@taoeffect.com" =
target=3D"_blank" class=3D"">contact@taoeffect.com</a>></span> =
wrote:<br class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
style=3D"word-wrap:break-word" class=3D"">Dear Chris,<span class=3D""><div=
class=3D""><br class=3D""></div><div class=3D""><blockquote type=3D"cite"=
class=3D""><div dir=3D"ltr" class=3D"">I think this is an unfair =
characterization. You have to opt into using =
drivechains.</div></blockquote><br class=3D""></div></span><div =
class=3D"">I have heard this nonsense repeated countless times in order =
to justify adopting Drivechain.</div><div class=3D""><br =
class=3D""></div><div class=3D"">This is not how security =
works.</div><div class=3D""><br class=3D""></div><div class=3D"">A child =
can "opt-in" to using a loaded gun, but is it a good idea to make it =
easy for them to do that?</div><div class=3D""><br class=3D""></div><div =
class=3D"">No.</div><div class=3D""><br class=3D""></div><div =
class=3D"">This is effectively the same thing Drivechains is =
doing.</div><div class=3D""><br class=3D""></div><div class=3D"">It is a =
request to modify the Bitcoin protocol to make it easy for Bitcoin users =
to give their Bitcoins to miners.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Does that sound like a good idea to =
anyone?</div><div class=3D""><br class=3D""></div><div class=3D"">If so, =
please leave, you are compromising Bitcoin's security.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Security is about making =
it difficult to shoot yourself in the face.</div><div class=3D""><br =
class=3D""></div><div class=3D"">If I design a car that has a button =
that randomly causes the brakes to give out if pressed, is that a good =
idea? Can I justify pushing for such a "feature" just because it's =
"opt-in"?</div><div class=3D""><br class=3D""></div><div class=3D"">No. =
That is fallacy.</div><div class=3D""><br class=3D""></div><div =
class=3D"">It is not how secure systems are designed.</div><div =
class=3D""><br class=3D""></div><div class=3D"">It is how *insecure* =
systems are designed.</div><span class=3D""><div class=3D""><br =
class=3D""></div><div class=3D""><blockquote type=3D"cite" class=3D""><div=
dir=3D"ltr" class=3D""><div class=3D""><div class=3D"">Care to share? =
I'm unaware if there is. </div></div></div></blockquote></div><div =
class=3D""><br class=3D""></div></span><div class=3D"">Sure, happy to, =
as soon as I have it written up in detail.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Kind regards,</div><div class=3D"">Greg =
Slepak</div><div class=3D""><span class=3D""><div class=3D"">
<span style=3D"font-family: Helvetica; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; font-variant-ligatures: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal;" class=3D""><br =
class=3D"m_3020035057494604851Apple-interchange-newline">--</span><br =
style=3D"font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; font-variant-ligatures: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal;" class=3D""><span =
style=3D"font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; font-variant-ligatures: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal;" class=3D"">Please =
do not email me anything that you are not comfortable also =
sharing</span><span style=3D"font-family: Helvetica; font-size: 14px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
font-variant-ligatures: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
line-height: normal;" class=3D""> with the NSA.</span>
</div>
<br class=3D""></span><span class=3D""><div class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Jul 12, 2017, at 12:19 PM, =
Chris Stewart <<a href=3D"mailto:chris@suredbits.com" target=3D"_blank"=
class=3D"">chris@suredbits.com</a>> wrote:</div><br =
class=3D"m_3020035057494604851Apple-interchange-newline"><div =
class=3D""><div dir=3D"ltr" class=3D""><div class=3D"">Hi Greg,<br =
class=3D""><br class=3D"">>Here, you admit that the security of the =
sidechains allows miners to steal bitcoins, something they cannot do =
currently.<br class=3D""><br class=3D""></div><div class=3D"">If I put =
my coins in an anyone can spend output, a miner will take them. They can =
do this today. I suggest you try it if you don't believe me :-). You =
have to be more specific with contract types instead of generically =
talking about 'all contracts ever'. <br class=3D""></div><div =
class=3D""><br class=3D"">> Drivechain is an unmistakeable weakening =
of Bitcoin's security guarantees. This you have not denied.<br =
class=3D""><br class=3D""></div>I think this is an unfair =
characterization. You have to opt into using drivechains. Other outputs =
such as P2PKH/Multisig etc are unaffected by a drivechain output. As =
Pieter Wuille stated earlier in this thread (and Paul has stated all =
along), drivechain outputs have a different security model than other =
contracts. Namely they are controlled by miners. I think we can all =
agree this is unfortunate, but it is the current reality we live in. I =
look forward to the day we can solve the 'ownership' problem so we can =
have trustless interoperable blockchains, but that day is not today.<br =
class=3D""><div class=3D""><div class=3D""><br class=3D""></div><div =
class=3D"">As a reminder, most users will not have to go through the =
drivechain withdrawal process. Most withdrawals will be done via atomic =
swaps. <br class=3D""><br class=3D"">>There is no reason to weaken =
Bitcoin's security in such a dramatic=20
fashion. Better options are being worked on, they just take time.<br =
class=3D""><br class=3D""></div><div class=3D"">Care to share? I'm =
unaware if there is. <br class=3D""><br class=3D"">><a =
href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-June/=
014600.html" target=3D"_blank" class=3D"">https://lists.<wbr =
class=3D"">linuxfoundation.org/pipermail/<wbr =
class=3D"">bitcoin-dev/2017-June/014600.<wbr class=3D"">html</a><br =
class=3D""><br class=3D""></div><div class=3D"">Everyone should re-read =
this email though, this is something that could happen. Paul's design =
makes it so that if this occurs it is *VERY* obvious. I guess we can =
argue if there is any difference between an obvious robbery vs a hidden =
robbery, but I think if we have to pick one or the other the choice is =
clear to me. Other designs (that I'm aware of) for sidechains had attack =
vectors that weren't so obvious.<br class=3D""><br class=3D""></div><div =
class=3D"">-Chris<br class=3D""></div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div></div></div><div =
class=3D"gmail_extra"><br class=3D""></div>
</div></blockquote></div><br =
class=3D""></span></div></div></blockquote></div><br class=3D""></div>
</div></blockquote></div><br class=3D""></div></div></body></html>=
--Apple-Mail=_535F0622-0BBD-47E9-AAB3-DBCA118AB4C4--
--Apple-Mail=_9CC3A83C-54B5-4A51-A706-61B42BFEB002
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJZZnu5AAoJEOxnICvpCVJHPcoQAJyjDc3o4L1PUvFcfNqjojak
hnEBZDTNCnHKNy8sVbnVQl5ZKlnvZ23LWYM9C5zQAr7M/wepaGs/2zGEidPiUT0K
kMmUgBY5Pq1Xxj8HD8gVJOAa9OpBh8z97BFd6JCKNpMx50GzWo1RQLIt8MfbW4I2
3GExg5R0wcCx4iELiqDUojf+N5J75CvXCeN3YUm+N9WJJyleSCj9iYJaNi1U/tKJ
MiAeH5acJizHAqJxNAsS5AuInPcR5chIEkjtpniCdZbcVH5ip6AwzzJfs8KKdPOl
gCZMLkTk2gQZ3xUXq17t5XTZhtqXTde63aRHSx+5526N8hlqd4r+64yy/MGlwS3T
5ATf/o4fIBMuziOLJohzrm5+u3s0ozg1/3bmAbWe674ZYvjJbJ4DopKiNx2Ickdz
EBz6dYdB6/L34HffFdUCt1XQeLraDdUl7Okr0Ojl9v0oKnAoNZkvj6TFCu4kNIEd
i1VudGKF5h2ztokS1knu+20BGZBojhRxrjqqcUrL4XRlLL1SB0IT3xUP8+4rx/60
3e6cHsQkzeX85+hboUT5c6U+0KOXM8E/FojdoczNGrHPJK+KKcADmS0+TnSRaX/g
myXcXYo9yD1UJkXGbZN5dWa4V0YImO097HHKkkp2xmVwGu6L3LdJEg9xF5VvGBpY
LVaealV4Y+LFOPDhDdq7
=jJM4
-----END PGP SIGNATURE-----
--Apple-Mail=_9CC3A83C-54B5-4A51-A706-61B42BFEB002--
|