summaryrefslogtreecommitdiff
path: root/5c/cc643eac5863764a9a23f484dce0a129b61f71
blob: 6c4ab279283653c589436c11eb7e57220d27243c (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
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
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
Return-Path: <fresheneesz@gmail.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 3E260C0012
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu, 31 Mar 2022 15:34:50 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id 279A341E6A
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu, 31 Mar 2022 15:34:50 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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_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: smtp4.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=gmail.com
Received: from smtp4.osuosl.org ([127.0.0.1])
 by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id gADsmc3IuPZM
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu, 31 Mar 2022 15:34:46 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com
 [IPv6:2a00:1450:4864:20::52f])
 by smtp4.osuosl.org (Postfix) with ESMTPS id B9B4141E3E
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu, 31 Mar 2022 15:34:45 +0000 (UTC)
Received: by mail-ed1-x52f.google.com with SMTP id a17so28619401edm.9
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu, 31 Mar 2022 08:34:45 -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=kEitIDsU6ceF6mk05qx2My3EPOoldKlQ2ShoHvI4WZk=;
 b=Q4dkEsGHkLwhD5bhJSmdG33imK0ekey3yhoxCmqzIfMd0/jhBZdQVJB4JYDDhkAOLC
 eysK6+RVeAy64yhV+EYV5u2mCOlDBIOkE5L0jimNRNjuEH29dVA1uxMC9THEL7cuWaDt
 aFnSmStvD4pzcmXngoSKlGw1uXKlWCn3zRGkTXu/gihOIDVgu5tQkpNuMEKqkuM4p2AV
 4d/vqI1Gf1VqY1zck6gWFIXI5Z+VauKVIv/PnV6Endb4xQD1gcyxhom24/a+h8la/Qkk
 PFzyv+ypWGZes+jvxDAyu3xgUw+CS++Ryi2O9XB8Ok0DDsFdZV9dx2DWDt32rCzceGAD
 GOjw==
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=kEitIDsU6ceF6mk05qx2My3EPOoldKlQ2ShoHvI4WZk=;
 b=dQJFqoi+aYyqlPqEhSazmcp1jh8A1ati7t4V2dSnIwteLOAI9K7HLS/6OTEawP4IMn
 /967hgS+3cVOSBvCjUR0BmCkTs9ivCsvlIWYLk3CG3dyKwTLeMSZXv/A22nMvL8uPasi
 X7ORNVgLSB/Qn2yJ1V4gRMB5ERE/zmJv3/5M2W33U1m6q0x6LILMqZLhdLrSoc00jLOP
 qgkRayC2aDkQq/MQKIqLTKLQdcbQd0Z4ipu4aZerstiXnPJlL27vcN/oQCtsiZz4hDfK
 BlXP6TuYPTcCIRSgN/0QA3p8eS1W42wiIHEbwKoJ9ITskKawnK9Vg1ogPzNU/fComUPH
 gnFw==
X-Gm-Message-State: AOAM530xA/GPj01vxceavdoYJecVl+Z3QyEZ+mNz8jjl9EDMiJt0usrM
 x8HQlO8t2Rnx4Cg+L9qM/oQhGR17Bh8aPFd31d0qOIf8
X-Google-Smtp-Source: ABdhPJyRfT0Kp65/piDdXV6gXm9tNk2idDCZe7AcSMkX2al25RFu+tJPzqR/7UryeGBucGjRZy8U97aY4DcDbp/rmqA=
X-Received: by 2002:a05:6402:1e88:b0:419:746e:fb05 with SMTP id
 f8-20020a0564021e8800b00419746efb05mr16758878edf.307.1648740883542; Thu, 31
 Mar 2022 08:34:43 -0700 (PDT)
MIME-Version: 1.0
References: <Rjjd7fhVSjF6O7UsQS-jyKOTglh6iezHoxXxyH8ywv5wKrHNQD5p9mLDUhYxsxuZCzb6bH0TgcXsDtTB8vWYdCbn2-bLjF5GhI8g6DRYCeA=@protonmail.com>
 <CAGpPWDYCVq-15d-hwMWGs=WoG7=7n7zR-pUrx9ANNpYb5z-31A@mail.gmail.com>
 <D908viKzD2oAEvIxutANq_OUQ1izhkDvUEb1lybk1Qg1EAyqyGi0FrLICo6VwGr8lAW3IlSUIw3MOKG8S0yvmwexkQ91Ych8sctJ0qkfnvI=@protonmail.com>
 <CAGpPWDbTfW3fTO1K=aFj1vUym5zbDes8DgifqLHUGCCV7Vgh4g@mail.gmail.com>
 <ewwe4V1o9Vhw3O3L6h8Eolcr16ilAewpxRsHEMC_VNllnfut7uHeQgSjA4ghapjo6QbBO9fDk8dk16w3FBfGI3ds7Y3J-38mZ4ydKg9T7Oo=@protonmail.com>
In-Reply-To: <ewwe4V1o9Vhw3O3L6h8Eolcr16ilAewpxRsHEMC_VNllnfut7uHeQgSjA4ghapjo6QbBO9fDk8dk16w3FBfGI3ds7Y3J-38mZ4ydKg9T7Oo=@protonmail.com>
From: Billy Tetrud <billy.tetrud@gmail.com>
Date: Thu, 31 Mar 2022 10:34:26 -0500
Message-ID: <CAGpPWDZEAWX5LXzvmNfgPJJP5qYE=wJAUavSPyDt7mOMqJjfTg@mail.gmail.com>
To: pushd <pushd@protonmail.com>
Content-Type: multipart/alternative; boundary="000000000000b0b85f05db85663f"
X-Mailman-Approved-At: Thu, 31 Mar 2022 15:37:39 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
 Anthony Towns <aj@erisian.com.au>
Subject: Re: [bitcoin-dev] Speedy Trial
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, 31 Mar 2022 15:34:50 -0000

--000000000000b0b85f05db85663f
Content-Type: text/plain; charset="UTF-8"

> I am not trying to convince you

 If that's really true then you're wasting my and everyone's time here.

> Signaling period is a waste of time if mining pools that agreed on a soft
fork earlier do politics

They can and will do politics regardless of why misunderstandings about
signaling. This is not a relevant point.

> It is considered as voting not just by people outside Bitcoin but the
participants itself

This is not a concrete downside. You are simply restating the premise.

> It gives miners an edge over economic nodes that enforce consensus rules

This is completely false. I have to assume you don't include yourself in
the list of users who think a passing vote of miners is required to upgrade
Bitcoin. Am I wrong? If not, then you should know that this
misunderstanding gives no one an edge.

So I'm counting 0 concrete downsides of this misunderstanding of how
signaling works that are both relevant and true. I'm going to stick with my
conclusion that this is a pointless dead end argument to make about soft
fork deployment in particular, and literally any technical design in
general.

You will be able to find 3 people who misunderstand BIP8, or literally any
other thing you come up with. You could probably find thousands. Or
millions if you ask people who've never heard of it. The argument that
changing the design will somehow improve that situation is perplexing, but
the argument that changing the idea might be a good idea on that basis is
completely unconscionable.


On Thu, Mar 31, 2022, 09:19 pushd <pushd@protonmail.com> wrote:

> > Why do you care what they think? Why does it matter if they
> misunderstand?
>
> I care about improving soft fork activation mechanism and shared one of
> the advantages that helps avoid misleading things. It matters because they
> are participants in this process.
>
>
> > If the people aren't imaginary, then its their importance that's
> imaginary.
>
> Neither the people nor their importance is imaginary. They are a part of
> Bitcoin and as important as our opinion about soft forks on this mailing
> list.
>
>
> > This isn't even sufficient evidence that they don't understand.
>
> One example of an exchange: https://i.postimg.cc/zv4M6MSp/2KM5tcE.png
>
> One example of a user:
> https://bitcoin.stackexchange.com/questions/97043/is-there-an-active-list-of-bips-currently-open-for-voting/
>
> 3 examples for each (user, mining pool and exchange) are enough to discuss
> a problem or list advantages of BIP 8/LOT=TRUE. I can create an archive
> with more if it helps during next soft fork.
>
>
> > You haven't convinced me this is a significant problem. What are the
> concrete downsides? Why do you think this can't be fixed by simple
> persistent explaining?
>
> I am not trying to convince you and we can have different opinions.
>
> Downsides:
>
> - Signaling period is a waste of time if mining pools that agreed on a
> soft fork earlier do politics or influenced by councils such as BMC or
> governments during signaling
>
> - It is considered as voting not just by people outside Bitcoin but the
> participants itself
>
> - It gives miners an edge over economic nodes that enforce consensus rules
>
> Simple persistent explaining has not helped in last few years. I don't see
> anything wrong in listing this as one of the advantages for BIP8/LOT=TRUE.
>
>
> pushd
> ---
>
> parallel lines meet at infinity?
>
> ------- Original Message -------
> On Thursday, March 31st, 2022 at 10:01 AM, Billy Tetrud <
> billy.tetrud@gmail.com> wrote:
>
> > Many users, miners and exchanges still think its voting
>
> Why do you care what they think? Why does it matter if they misunderstand?
>
> > it is not an imaginary group of people
>
> If the people aren't imaginary, then its their importance that's imaginary.
>
> > One example of a mining pool
>
> This isn't even sufficient evidence that they don't understand. Its quite
> possible they're using the word "voting" loosely or that they don't
> understand english very well. And again, so what if they tweet things that
> are not correctly worded? This is not a reason to change how we design
> bitcoin soft forks.
>
> Its not even wrong to say that a particular signaling round is very much
> like voting. What's wrong is saying that bitcoin upgrades are made if and
> only if miners vote to approve those changes.
>
> > I see a problem that exists
>
> You haven't convinced me this is a significant problem. What are the
> concrete downsides? Why do you think this can't be fixed by simple
> persistent explaining? You can find groups of people who misunderstand
> basically any aspect of bitcoin. The solution to people misunderstanding
> the design is never to change how bitcoin is designed.
>
>
> On Wed, Mar 30, 2022 at 4:14 PM pushd <pushd@protonmail.com> wrote:
>
>> > No it does not. This narrative is the worst. A bad explanation of
>> speedy trial can mislead people into thinking miner signalling is how
>> Bitcoin upgrades are voted in. But a bad explanation can explain anything
>> badly.
>>
>> I agree it is worst but why do you think this narrative exists? People
>> have tried explaining it. Many users, miners and exchanges still think its
>> voting. I think the problem is with activation method so BIP 8/LOT=TRUE is
>> a solution.
>>
>>
>> > The solution is not to change how we engineer soft forks, it's to
>> explain speedy trial better to this imaginary group of important people
>> that think miner signaling is voting.
>>
>> We can suggest different solutions but the problem exists and it is not
>> an imaginary group of people.
>>
>> One example of a mining pool: https://archive.ph/oyH04
>>
>>
>> > We shouldn't change how we engineer Bitcoin because of optics. I
>> completely object to that point continuing to be used.
>>
>> Voting as described on wiki is quite similar to what happens during
>> miners signaling followed by activation if a certain threshold is reached.
>> If some participants in this process consider it voting instead of
>> signaling for readiness then listing advantages of a better activation
>> method should help everyone reading this thread/email.
>>
>> Sorry, I don't understand your objection. I see a problem that exists
>> since years and a better activation method fixes it. There are other
>> positives for using BIP 8/LOT=TRUE which I shared in
>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-March/020178.html
>>
>> I will continue to discuss this problem with solutions until we use
>> better activation methods for future soft forks in any discussion about
>> activation methods.
>>
>>
>> pushd
>> ---
>>
>> parallel lines meet at infinity?
>>
>> ------- Original Message -------
>> On Thursday, March 31st, 2022 at 1:40 AM, Billy Tetrud <
>> billy.tetrud@gmail.com> wrote:
>>
>> @Pushd
>>
>> > Speedy trial makes it worse by misleading lot of bitcoin users
>> including miners to consider signaling as voting and majority votes decide
>> if a soft fork gets activated
>>
>> No it does not. This narrative is the worst. A bad explanation of speedy
>> trial can mislead people into thinking miner signalling is how Bitcoin
>> upgrades are voted in. But a bad explanation can explain anything badly.
>> The solution is not to change how we engineer soft forks, it's to explain
>> speedy trial better to this imaginary group of important people that think
>> miner signaling is voting.
>>
>> We shouldn't change how we engineer Bitcoin because of optics. I
>> completely object to that point continuing to be used.
>>
>> On Wed, Mar 30, 2022, 05:36 pushd via bitcoin-dev <
>> bitcoin-dev@lists.linuxfoundation.org> wrote:
>>
>>> > Any case where a flawed proposal makes it through getting activation
>>> parameters set and released, but doesn't achieve supermajority hashpower
>>> support is made worse by bip8/lot=true in comparison to speedy trial.
>>>
>>> - Flawed proposal making it through activation is a failure of review
>>> process
>>>
>>> - Supermajority hashpower percentage decided by bitcoin core developers
>>> can choose to not follow old or new consensus rules at any point
>>>
>>> - Speedy trial makes it worse by misleading lot of bitcoin users
>>> including miners to consider signaling as voting and majority votes decide
>>> if a soft fork gets activated
>>>
>>> - BIP 8/LOT=TRUE keeps things simple. Miners need to follow consensus
>>> rules as they do right now if they wish to mine blocks for subsidy and fees.
>>>
>>>
>>> Note: Mining pools or individual miners can participate in soft fork
>>> discussions regardless of activation method and share their concern which
>>> can be evaluated based on technical merits.
>>>
>>>
>>> pushd
>>> ---
>>>
>>> parallel lines meet at infinity?
>>> _______________________________________________
>>> bitcoin-dev mailing list
>>> bitcoin-dev@lists.linuxfoundation.org
>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>>
>>
>>
>

--000000000000b0b85f05db85663f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"auto"><div>&gt; I am not trying to convince yo=
u</div><div dir=3D"auto"><br></div><div dir=3D"auto">=C2=A0If that&#39;s re=
ally true then you&#39;re wasting my and everyone&#39;s time here.</div><di=
v dir=3D"auto"><br></div><div dir=3D"auto">&gt; Signaling period is a waste=
 of time if mining pools that agreed on a soft fork earlier do politics</di=
v><div dir=3D"auto"><br></div><div dir=3D"auto">They can and will do politi=
cs regardless of why misunderstandings about signaling. This is not a relev=
ant point.</div><div dir=3D"auto"><br></div><div dir=3D"auto">&gt; It is co=
nsidered as voting not just by people outside Bitcoin but the participants =
itself</div><div dir=3D"auto"><br></div><div dir=3D"auto">This is not a con=
crete downside. You are simply restating the premise.=C2=A0</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">&gt; It gives miners an edge over eco=
nomic nodes that enforce consensus rules</div><div dir=3D"auto"><br></div><=
div dir=3D"auto">This is completely false. I have to assume you don&#39;t i=
nclude yourself in the list of users who think a passing vote of miners is =
required to upgrade Bitcoin. Am I wrong? If not, then you should know that =
this misunderstanding gives no one an edge.=C2=A0</div><div dir=3D"auto"><b=
r></div><div dir=3D"auto">So I&#39;m counting 0 concrete downsides of this =
misunderstanding of how signaling works that are both relevant and true. I&=
#39;m going to stick with my conclusion that this is a pointless dead end a=
rgument to make about soft fork deployment in particular, and literally any=
 technical design in general.=C2=A0</div><div dir=3D"auto"><br></div><div d=
ir=3D"auto">You will be able to find 3 people who misunderstand BIP8, or li=
terally any other thing you come up with. You could probably find thousands=
. Or millions if you ask people who&#39;ve never heard of it. The argument =
that changing the design will somehow improve that situation is perplexing,=
 but the argument that changing the idea might be a good idea on that basis=
 is completely unconscionable.=C2=A0</div><div dir=3D"auto"><br></div><div =
dir=3D"auto"><br><div class=3D"gmail_quote" dir=3D"auto"><div dir=3D"ltr" c=
lass=3D"gmail_attr">On Thu, Mar 31, 2022, 09:19 pushd &lt;<a href=3D"mailto=
:pushd@protonmail.com" target=3D"_blank">pushd@protonmail.com</a>&gt; wrote=
:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex"><div style=3D"font-family:arial;f=
ont-size:14px"><span>&gt; Why do you care what they think? Why does it matt=
er if they misunderstand?</span><div><br></div><div><span>I care about impr=
oving soft fork activation mechanism and shared one of the advantages that =
helps avoid misleading things. It matters because they are participants in =
this process.</span></div><div><br></div><div><br></div><div><span>&gt; If =
the people aren&#39;t imaginary, then its their importance that&#39;s imagi=
nary.</span></div><div><br></div><div><span>Neither the people nor their im=
portance is imaginary. They are a part of Bitcoin and as important as our o=
pinion about soft forks on this mailing list.</span></div><div><br></div><d=
iv><br></div><div><span>&gt; This isn&#39;t even sufficient evidence that t=
hey don&#39;t understand.</span></div><div><br></div><div><span>One example=
 of an exchange: <a rel=3D"noreferrer nofollow noopener noreferrer" href=3D=
"https://i.postimg.cc/zv4M6MSp/2KM5tcE.png" target=3D"_blank">https://i.pos=
timg.cc/zv4M6MSp/2KM5tcE.png</a></span></div><div><br></div><div><span>One =
example of a user: <a rel=3D"noreferrer nofollow noopener noreferrer" href=
=3D"https://bitcoin.stackexchange.com/questions/97043/is-there-an-active-li=
st-of-bips-currently-open-for-voting/" target=3D"_blank">https://bitcoin.st=
ackexchange.com/questions/97043/is-there-an-active-list-of-bips-currently-o=
pen-for-voting/</a></span></div><div><br></div><div><span>3 examples for ea=
ch (user, mining pool and exchange) are enough to discuss a problem or list=
 advantages of BIP 8/LOT=3DTRUE. I can create an archive with more if it he=
lps during next soft fork.</span></div><div><br></div><div><br></div><div><=
span>&gt; You haven&#39;t convinced me this is a significant problem. What =
are the concrete downsides? Why do you think this can&#39;t be fixed by sim=
ple persistent explaining? </span></div><div><br></div><div><span>I am not =
trying to convince you and we can have different opinions.</span></div><div=
><br></div><div><span>Downsides:</span></div><div><br></div><div><span>- Si=
gnaling period is a waste of time if mining pools that agreed on a soft for=
k earlier do politics or influenced by councils such as BMC or governments =
during signaling</span></div><div><br></div><div><span>- It is considered a=
s voting not just by people outside Bitcoin but the participants itself</sp=
an></div><div><br></div><div><span>- It gives miners an edge over economic =
nodes that enforce consensus rules</span></div><div><br></div><span>Simple =
persistent explaining has not helped in last few years. I don&#39;t see any=
thing wrong in listing this as one of the advantages for BIP8/LOT=3DTRUE.</=
span><br></div><div style=3D"font-family:arial;font-size:14px"><span><br></=
span></div><div style=3D"font-family:arial;font-size:14px"><br></div>
<div style=3D"font-family:arial;font-size:14px">
    <div>
        <span style=3D"font-family:arial">pushd</span><div style=3D"font-fa=
mily:arial">---</div><div style=3D"font-family:arial"><br></div><span style=
=3D"font-family:arial">parallel lines meet at infinity?</span></div>
</div>
<div style=3D"font-family:arial;font-size:14px"><br></div><div>
        ------- Original Message -------<br>
        On Thursday, March 31st, 2022 at 10:01 AM, Billy Tetrud &lt;<a href=
=3D"mailto:billy.tetrud@gmail.com" rel=3D"noreferrer" target=3D"_blank">bil=
ly.tetrud@gmail.com</a>&gt; wrote:<br><br>
        <blockquote type=3D"cite">
            <div dir=3D"ltr">&gt;

<span style=3D"font-family:arial;font-size:14px">Many users, miners and exc=
hanges still think its voting</span><div><span style=3D"font-family:arial;f=
ont-size:14px"><br></span></div><div><span style=3D"font-family:arial;font-=
size:14px">Why do you care what they think? Why does it matter if they misu=
nderstand?</span></div><div><span style=3D"font-family:arial;font-size:14px=
"><br></span></div><div><span style=3D"font-family:arial;font-size:14px">&g=
t; </span><span style=3D"font-family:arial;font-size:14px">it is not an ima=
ginary group of people</span></div><div><span style=3D"font-family:arial;fo=
nt-size:14px"><br></span></div><div><span style=3D"font-family:arial;font-s=
ize:14px">If the people aren&#39;t imaginary, then its their importance tha=
t&#39;s imaginary.</span></div><div><span style=3D"font-family:arial;font-s=
ize:14px"><br></span></div><div><span style=3D"font-family:arial;font-size:=
14px">&gt; </span><span style=3D"font-family:arial;font-size:14px">One exam=
ple of a mining pool</span></div><div><span style=3D"font-family:arial;font=
-size:14px"><br></span></div><div><span style=3D"font-family:arial;font-siz=
e:14px">This isn&#39;t even sufficient evidence that they don&#39;t underst=
and. Its quite possible they&#39;re using the word &quot;voting&quot; loose=
ly or that they don&#39;t understand english very well. And again, so what =
if they tweet things that are not correctly worded? This is not a reason to=
 change how we design bitcoin soft forks. </span></div><div><span style=3D"=
font-family:arial;font-size:14px"><br></span></div><div><span style=3D"font=
-family:arial;font-size:14px">Its not even wrong to say that a particular s=
ignaling round is very much like voting. What&#39;s wrong is saying that bi=
tcoin upgrades are made if and only if miners vote to approve those changes=
. </span></div><div><span style=3D"font-family:arial;font-size:14px"><br></=
span></div><div><span style=3D"font-family:arial;font-size:14px">&gt; </spa=
n><span style=3D"font-family:arial;font-size:14px">I see a problem that exi=
sts</span></div><div><span style=3D"font-family:arial;font-size:14px"><br><=
/span></div><div><span style=3D"font-family:arial;font-size:14px">You haven=
&#39;t convinced me this is a significant problem. What are the concrete do=
wnsides? Why do you think this can&#39;t be fixed by simple persistent expl=
aining? You can find groups of people who misunderstand basically any aspec=
t of bitcoin. The solution to people misunderstanding the design is never t=
o change how bitcoin is designed.</span></div><div><span style=3D"font-fami=
ly:arial;font-size:14px"><br></span></div></div><br><div class=3D"gmail_quo=
te"><div class=3D"gmail_attr" dir=3D"ltr">On Wed, Mar 30, 2022 at 4:14 PM p=
ushd &lt;<a href=3D"mailto:pushd@protonmail.com" rel=3D"noreferrer nofollow=
 noopener noreferrer" target=3D"_blank">pushd@protonmail.com</a>&gt; wrote:=
<br></div><blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex" class=3D"gmail_quote"><div style=3D"f=
ont-family:arial;font-size:14px">&gt; <span>No it does not. This narrative =
is the worst. A bad explanation of speedy trial can mislead people into thi=
nking miner signalling is how Bitcoin upgrades are voted in. But a bad expl=
anation can explain anything badly. </span><br><span></span></div><div styl=
e=3D"font-family:arial;font-size:14px"><span><br></span></div><div style=3D=
"font-family:arial;font-size:14px">I agree it is worst but why do you think=
 this narrative exists? People have tried explaining it. Many users, miners=
 and exchanges still think its voting. I think the problem is with activati=
on method so BIP 8/LOT=3DTRUE is a solution.</div><div style=3D"font-family=
:arial;font-size:14px"><br></div><div style=3D"font-family:arial;font-size:=
14px"><br></div><div style=3D"font-family:arial;font-size:14px">&gt; <span =
style=3D"background-color:rgb(255,255,255);display:inline">The solution is =
not to change how we engineer soft forks, it&#39;s to explain speedy trial =
better to this imaginary group of important people that think miner signali=
ng is voting.</span></div><div style=3D"font-family:arial;font-size:14px"><=
span style=3D"background-color:rgb(255,255,255);display:inline"><br></span>=
</div><div style=3D"font-family:arial;font-size:14px"><span style=3D"backgr=
ound-color:rgb(255,255,255);display:inline">We can suggest different soluti=
ons but the problem exists and it is not an imaginary group of people.</spa=
n></div><div style=3D"font-family:arial;font-size:14px"><span style=3D"back=
ground-color:rgb(255,255,255);display:inline"><br></span></div><div style=
=3D"font-family:arial;font-size:14px"><span style=3D"background-color:rgb(2=
55,255,255);display:inline">One example of a mining pool: <span><a href=3D"=
https://archive.ph/oyH04" rel=3D"noreferrer nofollow noopener noreferrer" t=
arget=3D"_blank">https://archive.ph/oyH04</a></span></span></div><div style=
=3D"font-family:arial;font-size:14px"><span style=3D"background-color:rgb(2=
55,255,255);display:inline"><br></span></div><div style=3D"font-family:aria=
l;font-size:14px"></div><div style=3D"font-family:arial;font-size:14px"><sp=
an style=3D"background-color:rgb(255,255,255);display:inline"><br></span></=
div><div style=3D"font-family:arial;font-size:14px"><span style=3D"backgrou=
nd-color:rgb(255,255,255);display:inline">&gt; <span>We shouldn&#39;t chang=
e how we engineer Bitcoin because of optics. I completely object to that po=
int continuing to be used.</span></span></div><div style=3D"font-family:ari=
al;font-size:14px"><br></div><div style=3D"font-family:arial;font-size:14px=
">Voting as described on wiki is quite similar to what happens during miner=
s signaling followed by activation if a certain threshold is reached. If so=
me participants in this process consider it voting instead of signaling for=
 readiness then listing advantages of a better activation method should hel=
p everyone reading this thread/email.</div><div style=3D"font-family:arial;=
font-size:14px"><span style=3D"background-color:rgb(255,255,255);display:in=
line"><span><br></span></span></div><div style=3D"font-family:arial;font-si=
ze:14px">Sorry, I don&#39;t understand your objection. I see a problem that=
 exists since years and a better activation method fixes it. There are othe=
r positives for using BIP 8/LOT=3DTRUE which I shared in <span><a href=3D"h=
ttps://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-March/020178.ht=
ml" rel=3D"noreferrer nofollow noopener noreferrer" target=3D"_blank">https=
://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-March/020178.html</=
a></span></div><div style=3D"font-family:arial;font-size:14px"><br></div><d=
iv style=3D"font-family:arial;font-size:14px">I will continue to discuss th=
is problem with solutions until we use better activation methods for future=
 soft forks in any discussion about activation methods.</div><div style=3D"=
font-family:arial;font-size:14px"><br></div><div style=3D"font-family:arial=
;font-size:14px"><br></div>
<div style=3D"font-family:arial;font-size:14px">
    <div>
        <span style=3D"font-family:arial">pushd</span><div style=3D"font-fa=
mily:arial">---</div><div style=3D"font-family:arial"><br></div><span style=
=3D"font-family:arial">parallel lines meet at infinity?</span>
    </div>
    <div style=3D"font-family:arial;font-size:14px"><br></div></div><div>
        ------- Original Message -------<br>
        On Thursday, March 31st, 2022 at 1:40 AM, Billy Tetrud &lt;<a href=
=3D"mailto:billy.tetrud@gmail.com" rel=3D"noreferrer nofollow noopener nore=
ferrer" target=3D"_blank">billy.tetrud@gmail.com</a>&gt; wrote:<br><br>
        <blockquote type=3D"cite">
            <div dir=3D"auto">@Pushd<div dir=3D"auto"><br></div><div dir=3D=
"auto">&gt; <span style=3D"font-family:arial;font-size:12.8px">Speedy trial=
 makes it worse by misleading lot of bitcoin users including miners to cons=
ider signaling as voting and majority votes decide if a soft fork gets acti=
vated</span></div><div dir=3D"auto"><font face=3D"arial"><span style=3D"fon=
t-size:12.8px"><br></span></font><span style=3D"font-family:arial;font-size=
:12.8px"></span></div><div dir=3D"auto"><font face=3D"arial"><span style=3D=
"font-size:12.8px">No it does not. This narrative is the worst. A bad expla=
nation of speedy trial can mislead people into thinking miner signalling is=
 how Bitcoin upgrades are voted in. But a bad explanation can explain anyth=
ing badly. The solution is not to change how we engineer soft forks, it&#39=
;s to explain speedy trial better to this imaginary group of important peop=
le that think miner signaling is voting. </span></font></div><div dir=3D"au=
to"><font face=3D"arial"><span style=3D"font-size:12.8px"><br></span></font=
></div><div dir=3D"auto"><font face=3D"arial"><span style=3D"font-size:12.8=
px">We shouldn&#39;t change how we engineer Bitcoin because of optics. I co=
mpletely object to that point continuing to be used.</span></font></div></d=
iv><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On =
Wed, Mar 30, 2022, 05:36 pushd via bitcoin-dev &lt;<a rel=3D"noreferrer nof=
ollow noopener noreferrer" href=3D"mailto:bitcoin-dev@lists.linuxfoundation=
.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote=
:<br></div><blockquote class=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-size:14px">&gt; <span>Any case where a flawed propos=
al makes it through getting activation</span><div><span>parameters set and =
released, but doesn&#39;t achieve supermajority hashpower</span></div><span=
>support is made worse by bip8/lot=3Dtrue in comparison to speedy trial.</s=
pan></div><div style=3D"font-family:arial;font-size:14px"><br></div><div><s=
pan style=3D"font-family:arial;font-size:14px">- Flawed proposal making it =
through activation is a failure of review process</span><div style=3D"font-=
family:arial;font-size:14px"><br></div><div style=3D"font-family:arial;font=
-size:14px"><span>- Supermajority hashpower percentage decided by bitcoin c=
ore developers can choose to not follow old or new consensus rules at any p=
oint</span></div><div style=3D"font-family:arial;font-size:14px"><br></div>=
<div><font face=3D"arial">- Speedy trial makes it worse by misleading lot o=
f bitcoin users including miners to consider signaling as voting and majori=
ty votes decide if a soft fork gets activated</font></div><div style=3D"fon=
t-family:arial;font-size:14px"><br></div><div style=3D"font-family:arial;fo=
nt-size:14px"><span>- BIP 8/LOT=3DTRUE keeps things simple. Miners need to =
follow consensus rules as they do right now if they wish to mine blocks for=
 subsidy and fees.</span></div><div style=3D"font-family:arial;font-size:14=
px"><br></div><div style=3D"font-family:arial;font-size:14px"><br></div><sp=
an style=3D"font-family:arial;font-size:14px">Note: Mining pools or individ=
ual miners can participate in soft fork discussions regardless of activatio=
n method and share their concern which can be evaluated based on technical =
merits.</span><br></div><div><span style=3D"font-family:arial;font-size:14p=
x"><br></span></div><div style=3D"font-family:arial;font-size:14px"><br></d=
iv>
<div style=3D"font-family:arial;font-size:14px">
    <div>
        <span style=3D"font-family:arial">pushd</span><div style=3D"font-fa=
mily:arial">---</div><div style=3D"font-family:arial"><br></div><span style=
=3D"font-family:arial">parallel lines meet at infinity?</span></div>
</div>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" rel=3D"noreferrer =
nofollow noopener noreferrer" target=3D"_blank">bitcoin-dev@lists.linuxfoun=
dation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer nofollow noopener noreferrer" target=3D"_blank">https://l=
ists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a><br>
</blockquote></div>

        </blockquote><br>
    </div></blockquote></div>

        </blockquote><br>
    </div></blockquote></div></div></div>
</div>

--000000000000b0b85f05db85663f--