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
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
|
Return-Path: <gsanders87@gmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138])
by lists.linuxfoundation.org (Postfix) with ESMTP id 59051C002C
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 21 Apr 2022 14:16:38 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp1.osuosl.org (Postfix) with ESMTP id 47F1983F4F
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 21 Apr 2022 14:16:38 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001,
HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: smtp1.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=gmail.com
Received: from smtp1.osuosl.org ([127.0.0.1])
by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id BrhTc12zvl7Y
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 21 Apr 2022 14:16:36 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-yw1-x1129.google.com (mail-yw1-x1129.google.com
[IPv6:2607:f8b0:4864:20::1129])
by smtp1.osuosl.org (Postfix) with ESMTPS id 91F178343B
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 21 Apr 2022 14:16:36 +0000 (UTC)
Received: by mail-yw1-x1129.google.com with SMTP id
00721157ae682-2f19fdba41fso53613817b3.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 21 Apr 2022 07:16:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to
:cc; bh=qMyYRrtBwAnJ33siXqHpFTTmkLmjUpyKjgMl0DN0pP8=;
b=JhtvkqS4EXLE7XMXIuAAcCE/m4AJ7o7C0qP+pDe7SZe8ueci1eZvxVJchN10plb48Q
o26cJRMiAZHiR+iSLTkvukvQYdkwb0qKSLIArqiaVgcGWFrCT3GGYHuyi4/y37ZCMHZR
I8AI1x6qS4YImy80e44n8/ibnKMWO6FJYvRG+Ni2Uj/noj0loxv7IDrE+ZH1NS0+g2fs
9iUF7gGhPPUKc1cW+ewawNcm2tnmxY9R9eGhZV2a9B0vTLM6QulKIjEhGGp7U39g5QnQ
YJjKepcsWDo/6RgDYR+c8/qQFQvj1ZKmhoYAr29UXS/TkS24e0t0vEvSOwjt/gbrhrUH
4S7A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to:cc;
bh=qMyYRrtBwAnJ33siXqHpFTTmkLmjUpyKjgMl0DN0pP8=;
b=ZfHgbYnkKBoQ2NtlF82OS3KQYFJ/tTULoZr9goMV8N45ziWwtuQNriWv7nBU7ccpVp
CqKLBaSdpxejq5+daJlqNILjA0jnv3HnW6PJS1BFQ4Hat+ecnDdcY6d4kI0twQJUMlWp
2TYxDwGr7qM0sNCaInfluaK1UgioNjCtB2kGAnkRSYp7Pb14QJqe/EIewmiUHBz5NE0k
s4EsE4KqMEBPP6vDIX41S/9uqo9lD4dHvU33PrinfPXB+h+MBOS2eKJ52ye6ljctNaXU
Nn2dp1bAf66OxAH0YwM5Y/s0HJMAgbZF7ZIAYzz4F2oZu+QLKDRJYCXFYSnRxyqE27j1
p4Yw==
X-Gm-Message-State: AOAM533nfW4LbWYF8MEFuANKMGRfLt/bpenlPiVQXwUNWWPvzeigGYuK
k3JULZ+Oial0FZ2LI8ub1imJwnQBGCJV+e9yO8TfNMRa
X-Google-Smtp-Source: ABdhPJyj8YXeNxRQ3WH+fYkhHB20InzVktPiKY6HJhUkyMms/VmV6qZ51W3nBxWKThw/tu1e5z6/oISAQ9kGyn7evIg=
X-Received: by 2002:a81:4887:0:b0:2ec:2d47:71e4 with SMTP id
v129-20020a814887000000b002ec2d4771e4mr24854158ywa.466.1650550595430; Thu, 21
Apr 2022 07:16:35 -0700 (PDT)
MIME-Version: 1.0
References: <CAD5xwhjVS4Y4e3qDWzJfva+0hiKpe8-WqmX_kUHrpfXmG5sMXw@mail.gmail.com>
<uUzpB7Sapu5q3qxF7voLmwRIJfLPGCwcelhFVR8BClM7HBi9n86zj1A6SeYBdKZXOGL-8C049G1mEURDkyNMhksyPMfjIMPJXHoidOydAT8=@protonmail.com>
<_7t2rDK--RA323BHOtnqyvAne1ghGx3OW-8GczHqbCGdgEnQVKg0eY8CHaDXlfEMuNtj1Y2OBedvrNZfNmPRfOzQ5irBb0IEtxFY_QKpTTY=@protonmail.com>
In-Reply-To: <_7t2rDK--RA323BHOtnqyvAne1ghGx3OW-8GczHqbCGdgEnQVKg0eY8CHaDXlfEMuNtj1Y2OBedvrNZfNmPRfOzQ5irBb0IEtxFY_QKpTTY=@protonmail.com>
From: Greg Sanders <gsanders87@gmail.com>
Date: Thu, 21 Apr 2022 10:16:24 -0400
Message-ID: <CAB3F3Dv-ncpwomb93g23VyDGW-xfAo_Zrszsgo0bh+H_e7tiDg@mail.gmail.com>
To: alicexbt <alicexbt@protonmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000ecae5c05dd2ac12d"
Subject: Re: [bitcoin-dev] 7 Theses on a next step for BIP-119
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
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: Thu, 21 Apr 2022 14:16:38 -0000
--000000000000ecae5c05dd2ac12d
Content-Type: text/plain; charset="UTF-8"
Ironically assumptions of bad faith are going to kill any proposal,
resulting in the status quo.
Let's keep the assumption of good faith, unless you are actually accusing
people of being a NSA-adjacent asset.
On Thu, Apr 21, 2022 at 10:08 AM alicexbt via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> There are a number of individuals who have stated opposition to attempting
> to activate a CTV soft fork in the near term:
>
> https://gist.github.com/michaelfolkson/352a503f4f9fc5de89af528d86a1b718
>
>
> sheshek found some issues with the list and some of them are not really an
> opposition for CTV. Others do not have any technical details to consider.
>
> The saddest thing is that if Jeremy's soft fork activation attempt causes
> the uncertainty, confusion and disruption I fear it could it will make
> future soft forks that do have community consensus orders of magnitude
> harder to pull off.
>
>
>
> Calling CTV an attack on bitcoin or doing personal attacks on Jeremy and
> other developers on social media that support CTV won't help. Developers
> should be free to propose improvements and write code. Users can decide if
> they want to run this code. Just because someone is opposing a change and
> prefers status quo does not mean it is better for Bitcoin. Attackers have
> used such things in past for many open source projects.
>
> Example: Someone signed up on the Tor Project mailing list and then
> participated in discussions to advocate against the removal of malicious
> servers
>
> https://nitter.net/campuscodi/status/1466748897003544579
>
>
> dev/fd0
>
> Sent with ProtonMail <https://protonmail.com/> secure email.
>
> ------- Original Message -------
> On Wednesday, April 20th, 2022 at 6:54 PM, Michael Folkson via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> > The client has a Speedy trial release similar to Taproots with
> parameters proposed to be....
>
> As I've said before I was hoping we'd avoid this exercise. Best case, it
> wastes the time of people who could be working on all sorts of valuable
> projects for the ecosystem. Worst case, we take a Russian roulette style
> gamble with a chain split.
>
> But here's a summary of the basic facts:
>
> The latest Bitcoin Core release candidate (23.0) does not contain any new
> soft fork code, either CTV code or any new activation code. Running Bitcoin
> Core 23.0 out the box will not signal for any new soft fork and will not
> enforce any new soft fork rules (CTV or otherwise). Of course it will
> continue to enforce Taproot rules as Taproot activated last year.
>
> There are a number of individuals who have stated opposition to attempting
> to activate a CTV soft fork in the near term:
>
> https://gist.github.com/michaelfolkson/352a503f4f9fc5de89af528d86a1b718
>
> Most of those individuals haven't logged their opposition on Jeremy's site:
> https://utxos.org/signals/
>
> Hence their views haven't been included or discussed in Jeremy's latest
> blog post.
>
> Chain split risk
>
> I can't predict how many full nodes and miners will run Jeremy's client
> attempting to activate CTV. One would expect that many will continue to run
> versions of Bitcoin Core that will not enforce CTV rules and will not
> activate it. But whether Jeremy's client will be a majority, significant
> minority, insignificant minority of full nodes and miners would be
> speculation on my part. (Personally I highly doubt those running Jeremy's
> client will be a majority which leaves a significant minority and
> insignificant minority as the most likely options).
>
> Jeremy's client is intending to use Speedy Trial presumably with similar
> parameters to that used for Taproot. That would mean seeking 90 percent of
> miners to signal for this CTV soft fork activation attempt.
>
> Assuming 90 percent of miners don't signal for it in one of the Speedy
> Trial windows then the activation attempt will have failed and it will be
> back in Jeremy's court whether he tries again with a different activation
> attempt.
>
> Assuming 90 percent of miners do signal for it (unlikely in my opinion but
> presumably still a possibility) then the CTV soft fork could activate
> unless full nodes resist it. This resistance would most likely be in the
> form of a UASF style client which rejects blocks that apply the CTV rules
> and/or includes transactions that don't meet the CTV rules post activation.
> We would now be in chain split territory with two different assets and
> blockchains like we had with BTC and BCH.
>
> If I oppose this activation attempt and the associated chain split risk
> what should I do?
>
> Firstly, you can register your opposition to this soft fork activation
> attempt on Jeremy's site: https://utxos.org/signals/
>
> It seems Jeremy will continue this activation attempt regardless but it
> will be useful for others to see clearly that this a contentious soft fork
> activation attempt and act accordingly. So far only 3 individuals'
> opposition is registered on his site.
>
> Secondly, if it is looking like 90 percent (or whatever percentage Jeremy
> uses) of miners are going to signal for a CTV soft fork then you can
> consider joining a UASF style effort to resist the soft fork activation
> attempt. I will certainly seek to participate and will continue to inform
> this list of efforts in this direction.
>
> The saddest thing is that if Jeremy's soft fork activation attempt causes
> the uncertainty, confusion and disruption I fear it could it will make
> future soft forks that do have community consensus orders of magnitude
> harder to pull off. There are a number of soft fork proposals that I'm
> personally excited about (enabling covenants, eltoo, Simplicity, CISA etc)
> that long term we might get with a sensible approach to only activating
> soft forks that have community consensus. But the more uncertainty,
> confusion and disruption we create over contentious soft forks the more
> dangerous any soft fork of any form will appear. The primary focus will
> need to be resisting soft forks that don't have community consensus and
> ensuring Bitcoin doesn't splinter into a large number of different
> assets/blockchains with different combinations of soft forks active.
>
> So if you oppose this soft fork activation attempt please voice your
> opposition, run full node software that doesn't include CTV and CTV
> activation code such as Bitcoin Core and if/when necessary and available
> run full node software that proactively rejects application of the CTV
> rules.
>
> --
> Michael Folkson
> Email: michaelfolkson at protonmail.com
> Keybase: michaelfolkson
> PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3
>
> ------- Original Message -------
> On Tuesday, April 19th, 2022 at 18:31, Jeremy Rubin via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> Devs,
>
> In advance of the CTV meeting today, I wanted to share what my next step
> is in advocating for CTV, as well as 7 theses for why I believe it to be
> the right course of action to take at this time.
>
> Please see the post at
> https://rubin.io/bitcoin/2022/04/17/next-steps-bip119/.
>
> As always, open to hear any and all feedback,
>
> Jeremy
>
>
> archived at:
> https://web.archive.org/web/20220419172825/https://rubin.io/bitcoin/2022/04/17/next-steps-bip119/
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--000000000000ecae5c05dd2ac12d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Ironically assumptions of bad faith are going to kill any =
proposal, resulting in the status quo.<div><br></div><div>Let's keep th=
e assumption of good faith, unless you are actually accusing people of bein=
g a NSA-adjacent asset.</div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Thu, Apr 21, 2022 at 10:08 AM alicexbt via=
bitcoin-dev <<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">b=
itcoin-dev@lists.linuxfoundation.org</a>> wrote:<br></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
rgb(204,204,204);padding-left:1ex"><div style=3D"font-family:arial;font-si=
ze:14px"><blockquote type=3D"cite" style=3D"padding:0px 0px 0px 1rem;margin=
:0px;border-left:4px solid rgb(229,229,229);font-family:Arial,"Helveti=
ca Neue",Helvetica,sans-serif;background-color:rgb(255,255,255)"><span=
style=3D"font-family:arial">There are a number of individuals who have sta=
ted opposition to attempting to activate a CTV soft fork in the near term:<=
/span><div style=3D"font-family:arial"><br></div><div><span style=3D"font-f=
amily:arial"><a href=3D"https://gist.github.com/michaelfolkson/352a503f4f9f=
c5de89af528d86a1b718" rel=3D"noreferrer nofollow noopener" style=3D"color:r=
gb(101,126,228)" target=3D"_blank">https://gist.github.com/michaelfolkson/3=
52a503f4f9fc5de89af528d86a1b718</a>=C2=A0</span></div></blockquote><div><sp=
an style=3D"font-family:arial"><br></span></div><div><span style=3D"font-fa=
mily:arial">sheshek found some issues with the list and some of them are no=
t really an opposition for CTV. Others do not have any technical details to=
consider.</span></div><div><span style=3D"font-family:arial"><br></span></=
div><div><span style=3D"font-family:arial"><blockquote type=3D"cite" style=
=3D"padding:0px 0px 0px 1rem;margin:0px;border-left:4px solid rgb(229,229,2=
29);font-family:Arial,"Helvetica Neue",Helvetica,sans-serif;backg=
round-color:rgb(255,255,255)"><span style=3D"font-family:arial">The saddest=
thing is that if Jeremy's soft fork activation attempt causes the unce=
rtainty, confusion and disruption I fear it could it will make future soft =
forks that do have community consensus orders of magnitude harder to pull o=
ff.<span>=C2=A0</span></span></blockquote><br></span></div><div><span style=
=3D"font-family:arial"><br></span></div><div><span style=3D"font-family:ari=
al">Calling CTV an attack on bitcoin or doing personal attacks on Jeremy an=
d other developers on social media that support CTV won't help. Develop=
ers should be free to propose improvements and write code. Users can decide=
if they want to run this code. Just because someone is opposing a change a=
nd prefers status quo does not mean it is better for Bitcoin. Attackers hav=
e used such things in past for many open source projects.</span></div><div>=
<span style=3D"font-family:arial"><br></span></div><div><span style=3D"font=
-family:arial">Example:=C2=A0<span>Someone signed up on the Tor Project mai=
ling list and then participated in discussions to advocate against the remo=
val of malicious servers</span></span></div><div><span style=3D"font-family=
:arial"><br></span></div><div><span style=3D"font-family:arial"><span><a re=
l=3D"noreferrer nofollow noopener" href=3D"https://nitter.net/campuscodi/st=
atus/1466748897003544579" target=3D"_blank">https://nitter.net/campuscodi/s=
tatus/1466748897003544579</a></span></span></div><div><span style=3D"font-f=
amily:arial"><br></span></div><div><br></div><div>dev/fd0</div><div><br></d=
iv></div>
<div style=3D"font-family:arial;font-size:14px">
<div>
</div>
<div>
Sent with <a href=3D"https://protonmail.com/" rel=3D"noopener noref=
errer" target=3D"_blank">ProtonMail</a> secure email.
</div>
</div>
<div style=3D"font-family:arial;font-size:14px"><br></div><div>
------- Original Message -------<br>
On Wednesday, April 20th, 2022 at 6:54 PM, Michael Folkson via bitc=
oin-dev <<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=
=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br><br>
<blockquote type=3D"cite">
<div style=3D"font-family:arial;font-size:14px">> The client=
has a Speedy trial release similar to Taproots with parameters proposed to=
be....</div><div style=3D"font-family:arial;font-size:14px"><br></div><div=
style=3D"font-family:arial;font-size:14px">As I've said before I was h=
oping we'd avoid this exercise. Best case, it wastes the time of people=
who could be working on all sorts of valuable projects for the ecosystem. =
Worst case, we take a Russian roulette style gamble with a chain split.=C2=
=A0</div><div style=3D"font-family:arial;font-size:14px"><br></div><div sty=
le=3D"font-family:arial;font-size:14px">But here's a summary of the bas=
ic facts:</div><div style=3D"font-family:arial;font-size:14px"><br></div><d=
iv style=3D"font-family:arial;font-size:14px">The latest Bitcoin Core relea=
se candidate (23.0) does not contain any new soft fork code, either CTV cod=
e or any new activation code. Running Bitcoin Core 23.0 out the box will no=
t signal for any new soft fork and will not enforce any new soft fork rules=
(CTV or otherwise). Of course it will continue to enforce Taproot rules as=
Taproot activated last year.</div><div style=3D"font-family:arial;font-siz=
e:14px"><br></div><div style=3D"font-family:arial;font-size:14px">There are=
a number of individuals who have stated opposition to attempting to activa=
te a CTV soft fork in the near term:</div><div style=3D"font-family:arial;f=
ont-size:14px"><br></div><div style=3D"font-family:arial;font-size:14px"><a=
href=3D"https://gist.github.com/michaelfolkson/352a503f4f9fc5de89af528d86a=
1b718" rel=3D"noreferrer nofollow noopener" target=3D"_blank">https://gist.=
github.com/michaelfolkson/352a503f4f9fc5de89af528d86a1b718</a>=C2=A0</div><=
div style=3D"font-family:arial;font-size:14px"><br></div><div style=3D"font=
-family:arial;font-size:14px">Most of those individuals haven't logged =
their opposition on Jeremy's site:</div><div style=3D"font-family:arial=
;font-size:14px"><a href=3D"https://utxos.org/signals/" rel=3D"noreferrer n=
ofollow noopener" target=3D"_blank">https://utxos.org/signals/</a></div><di=
v style=3D"font-family:arial;font-size:14px"><br></div><div style=3D"font-f=
amily:arial;font-size:14px">Hence their views haven't been included or =
discussed in Jeremy's latest blog post.</div><div style=3D"font-family:=
arial;font-size:14px"><br></div><div style=3D"font-family:arial;font-size:1=
4px">Chain split risk</div><div style=3D"font-family:arial;font-size:14px">=
<br></div><div style=3D"font-family:arial;font-size:14px">I can't predi=
ct how many full nodes and miners will run Jeremy's client attempting t=
o activate CTV. One would expect that many will continue to run versions of=
Bitcoin Core that will not enforce CTV rules and will not activate it. But=
whether Jeremy's client will be a majority, significant minority, insi=
gnificant minority of full nodes and miners would be speculation on my part=
. (Personally I highly doubt those running Jeremy's client will be a ma=
jority which leaves a significant minority and insignificant minority as th=
e most likely options).</div><div style=3D"font-family:arial;font-size:14px=
"><br></div><div style=3D"font-family:arial;font-size:14px">Jeremy's cl=
ient is intending to use Speedy Trial presumably with similar parameters to=
that used for Taproot. That would mean seeking 90 percent of miners to sig=
nal for this CTV soft fork activation attempt.=C2=A0</div><div style=3D"fon=
t-family:arial;font-size:14px"><br></div><div style=3D"font-family:arial;fo=
nt-size:14px">Assuming 90 percent of miners don't signal for it in one =
of the Speedy Trial windows then the activation attempt will have failed an=
d it will be back in Jeremy's court whether he tries again with a diffe=
rent activation attempt.</div><div style=3D"font-family:arial;font-size:14p=
x"><br></div><div style=3D"font-family:arial;font-size:14px">Assuming 90 pe=
rcent of miners do signal for it (unlikely in my opinion but presumably sti=
ll a possibility) then the CTV soft fork could activate unless full nodes r=
esist it. This resistance would most likely be in the form of a UASF style =
client which rejects blocks that apply the CTV rules and/or includes transa=
ctions that don't meet the CTV rules post activation. We would now be i=
n chain split territory with two different assets and blockchains like we h=
ad with BTC and BCH.</div><div style=3D"font-family:arial;font-size:14px"><=
br></div><div style=3D"font-family:arial;font-size:14px">If I oppose this a=
ctivation attempt and the associated chain split risk what should I do?</di=
v><div style=3D"font-family:arial;font-size:14px"><br></div><div style=3D"f=
ont-family:arial;font-size:14px">Firstly, you can register your opposition =
to this soft fork activation attempt on Jeremy's site:=C2=A0<span><a hr=
ef=3D"https://utxos.org/signals/" rel=3D"noreferrer nofollow noopener" targ=
et=3D"_blank">https://utxos.org/signals/</a></span></div><div style=3D"font=
-family:arial;font-size:14px"><br></div><div style=3D"font-family:arial;fon=
t-size:14px">It seems Jeremy will continue this activation attempt regardle=
ss but it will be useful for others to see clearly that this a contentious =
soft fork activation attempt and act accordingly. So far only 3 individuals=
' opposition is registered on his site.</div><div style=3D"font-family:=
arial;font-size:14px"><br></div><div style=3D"font-family:arial;font-size:1=
4px">Secondly, if it is looking like 90 percent (or whatever percentage Jer=
emy uses) of miners are going to signal for a CTV soft fork then you can co=
nsider joining a UASF style effort to resist the soft fork activation attem=
pt. I will certainly seek to participate and will continue to inform this l=
ist of efforts in this direction.=C2=A0</div><div style=3D"font-family:aria=
l;font-size:14px"><br></div><div style=3D"font-family:arial;font-size:14px"=
>The saddest thing is that if Jeremy's soft fork activation attempt cau=
ses the uncertainty, confusion and disruption I fear it could it will make =
future soft forks that do have community consensus orders of magnitude hard=
er to pull off. There are a number of soft fork proposals that I'm pers=
onally excited about (enabling covenants, eltoo, Simplicity, CISA etc) that=
long term we might get with a sensible approach to only activating soft fo=
rks that have community consensus. But the more uncertainty, confusion and =
disruption we create over contentious soft forks the more dangerous any sof=
t fork of any form will appear. The primary focus will need to be resisting=
soft forks that don't have community consensus and ensuring Bitcoin do=
esn't splinter into a large number of different assets/blockchains with=
different combinations of soft forks active.</div><div style=3D"font-famil=
y:arial;font-size:14px"><br></div><div style=3D"font-family:arial;font-size=
:14px">So if you oppose this soft fork activation attempt please voice your=
opposition, run full node software that doesn't include CTV and CTV ac=
tivation code such as Bitcoin Core and if/when necessary and available run =
full node software that proactively rejects application of the CTV rules.</=
div><div style=3D"font-family:arial;font-size:14px"><br></div>
<div style=3D"font-family:arial;font-size:14px">
<div>
<div style=3D"font-family:arial;font-size:14px"><span style=3D"colo=
r:rgb(38,42,51);font-style:normal;font-weight:400;letter-spacing:normal;tex=
t-indent:0px;text-transform:none;white-space:pre-wrap;word-spacing:0px;back=
ground-color:rgb(255,255,255);float:none;display:inline"><span style=3D"fon=
t-family:SFMono-Regular,Consolas,"Liberation Mono",Menlo,monospac=
e,monospace"><span style=3D"font-size:14px">--<br>Michael Folkson<br>Email:=
michaelfolkson at </span></span></span><a rel=3D"noreferrer nofollow noope=
ner" style=3D"line-height:normal;text-decoration:underline;font-family:SFMo=
no-Regular,Consolas,"Liberation Mono",Menlo,monospace,monospace;f=
ont-size:14px;font-style:normal;font-weight:400;letter-spacing:normal;text-=
indent:0px;text-transform:none;white-space:pre-wrap;word-spacing:0px" href=
=3D"http://protonmail.com/" target=3D"_blank">protonmail.com</a><span style=
=3D"color:rgb(38,42,51);font-style:normal;font-weight:400;letter-spacing:no=
rmal;text-indent:0px;text-transform:none;white-space:pre-wrap;word-spacing:=
0px;background-color:rgb(255,255,255);float:none;display:inline"><span styl=
e=3D"font-family:SFMono-Regular,Consolas,"Liberation Mono",Menlo,=
monospace,monospace"><span style=3D"font-size:14px"> </span></span></span><=
br></div><div style=3D"font-family:arial;font-size:14px"><span style=3D"col=
or:rgb(38,42,51);font-style:normal;font-weight:400;letter-spacing:normal;te=
xt-indent:0px;text-transform:none;white-space:pre-wrap;word-spacing:0px;bac=
kground-color:rgb(255,255,255);float:none;display:inline"><span style=3D"fo=
nt-family:SFMono-Regular,Consolas,"Liberation Mono",Menlo,monospa=
ce,monospace"><span style=3D"font-size:14px">Keybase: michaelfolkson<br>PGP=
: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3</span></span></span><br=
></div>
</div>
<div>
</div>
</div>
<div style=3D"font-family:arial;font-size:14px"><br></div><div>
------- Original Message -------<br>
On Tuesday, April 19th, 2022 at 18:31, Jeremy Rubin via bitcoin-dev=
<<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_bl=
ank">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br><br>
<blockquote type=3D"cite">
<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-fam=
ily:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">Devs,</div=
><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-ser=
if;font-size:small;color:rgb(0,0,0)"><br></div><div class=3D"gmail_default"=
style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(=
0,0,0)">In advance of the CTV meeting today, I wanted to share what my next=
step is in advocating for CTV, as well as 7 theses for why I believe it to=
be the right course of action to take at this time.</div><div class=3D"gma=
il_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:small=
;color:rgb(0,0,0)"><br></div><div class=3D"gmail_default" style=3D"font-fam=
ily:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">Please see=
the post at <a rel=3D"noreferrer nofollow noopener" href=3D"https://rubin.=
io/bitcoin/2022/04/17/next-steps-bip119/" target=3D"_blank">https://rubin.i=
o/bitcoin/2022/04/17/next-steps-bip119/</a>.<br></div><div class=3D"gmail_d=
efault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;col=
or:rgb(0,0,0)"><br></div><div class=3D"gmail_default" style=3D"font-family:=
arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">As always, ope=
n to hear any and all feedback,</div><div><br></div><div class=3D"gmail_def=
ault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color=
:rgb(0,0,0)">Jeremy</div><div><div dir=3D"ltr"><div dir=3D"ltr"><br></div><=
div dir=3D"ltr"><br></div><div dir=3D"ltr"><div class=3D"gmail_default" sty=
le=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,=
0)">archived at: <a rel=3D"noreferrer nofollow noopener" href=3D"https://we=
b.archive.org/web/20220419172825/https://rubin.io/bitcoin/2022/04/17/next-s=
teps-bip119/" target=3D"_blank">https://web.archive.org/web/20220419172825/=
https://rubin.io/bitcoin/2022/04/17/next-steps-bip119/</a></div><br></div><=
/div></div></div>
</blockquote><br>
</div>
</blockquote><br>
</div>_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>
--000000000000ecae5c05dd2ac12d--
|