summaryrefslogtreecommitdiff
path: root/1c/7e6263dd6dace7752da452669403c123f6cd79
blob: 9600d18f37166cf1bd7b4a641d595c0122715719 (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
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 55DF2C002D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu,  9 Jun 2022 04:31:05 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id 3D66041BE2
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu,  9 Jun 2022 04:31:05 +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 HSug0B6dk02M
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu,  9 Jun 2022 04:31:01 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com
 [IPv6:2607:f8b0:4864:20::62e])
 by smtp4.osuosl.org (Postfix) with ESMTPS id B03CE41B8E
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu,  9 Jun 2022 04:31:01 +0000 (UTC)
Received: by mail-pl1-x62e.google.com with SMTP id f9so8870490plg.0
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 08 Jun 2022 21:31:01 -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;
 bh=Bp7xERjxw5Ap7GQsZJEQHsOLJi2sX4qCDn/2/SB+YfI=;
 b=DpqNorbTq9CE9u2TcdZpt1wY4JGIRw7yRD5eQ06472AKEBkuQtUi2Ze6hsSE3WoUJF
 I+IMB2ORCvNNM3/2pSbN1H15kRoedZ/iRQ2Xll17hwrqYOHiNRi/yROyMczdKP6drcgm
 g58qQmil4g/eyWxmSXRcHCknEHeie23NFIZ8DaP8Yz/pudqHDZzDJlfeHI0z5B0cAH28
 ztG/h/TkvztsEV/0fOLlnW++tnkgF+0V6/n6voSeWVzxxmpY3QqVWbSruLZLzIqmf/EY
 I3IvJIqTeDdHfQMS9wGwkYS0hvJRwHx9Y8VwPb0iN6GqR33z0mKa5tYUXBSMx2EdJq/L
 p8dw==
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;
 bh=Bp7xERjxw5Ap7GQsZJEQHsOLJi2sX4qCDn/2/SB+YfI=;
 b=tcC6br/x3nk4ywG/v4iC6hls58NkGoxRfpKOJl2XgtRDfNjeBBCa1CiKz+NitOFOm8
 943S2L/EGkZhyeStZjBW+beyiNBzHwDg7nnuV0hDjYv3GYxGgIGCkQdbiqYSBuG38yXv
 zT5hx9HEjOgyudynHj/JpZswgjlXgRY52vX3IcYL0S4YAKdGdvbKyuU0t63P4UA/ARrN
 fKyPz0mZdcvOG5OaxXdjTdYn0/UzEFKH3M1JGdOWsex1sqLLt5otPiPOGIbLmJyt2l5C
 nMYVf2foOrUunEZliAjMOmwUM4lXAUV6tzvn4jVhQnDJ87fs37uksF1sPGPSIN75ouwZ
 ZcaQ==
X-Gm-Message-State: AOAM530N19f1AWeltlEZ5blzozaebqvUiz+Gz4U0OHIePzYQisz+rRKA
 mEMfrTHenZga0gzLn41cVMmDdVPjaSKqqAdgEddRc8Rn
X-Google-Smtp-Source: ABdhPJzixusG8jkq51Xvtxn/wrKXbZKg3QcTh+F2Bhy96aqCw/JRDBxmCvQhQ999+6V1/+m0jj8PaFwhilG1qE4qOBQ=
X-Received: by 2002:a17:902:ebc8:b0:15f:417c:288b with SMTP id
 p8-20020a170902ebc800b0015f417c288bmr37832220plg.14.1654749060933; Wed, 08
 Jun 2022 21:31:00 -0700 (PDT)
MIME-Version: 1.0
References: <QOWIpROGDv5HHP2GsDiSOsTJ9TVZhFeSP3C03_e2Z3XtOKC_4N5GJtxbdlxuhErvhLZXo1Rn_7SWAQ9XRPwHFuYyArZryTVENefDZuGTAYA=@protonmail.com>
 <CABm2gDoyFUhcryx9wSx2NOWt126img+51UehtkW7Nfg2Sf97aQ@mail.gmail.com>
 <zyE-uR_2M7vAE8jXf3wthIGQj_-dz9FoL50ERTmCb-MCv4zyMgoHAdSff539SPtROJpJdgrfBspM3IZJrNQ9V4kpDnyMB9X6mlWf0eSk1Rk=@protonmail.com>
 <CAGpPWDYWm4Y8ZcuEdm_7qhGzG3KRv0s=opT0RnVa_fM3SamTJg@mail.gmail.com>
 <CABm2gDr6QyVUPFODRBBvWY-sukX+k9-kLKpjPnwwaQqejQL88w@mail.gmail.com>
In-Reply-To: <CABm2gDr6QyVUPFODRBBvWY-sukX+k9-kLKpjPnwwaQqejQL88w@mail.gmail.com>
From: Billy Tetrud <billy.tetrud@gmail.com>
Date: Wed, 8 Jun 2022 23:30:45 -0500
Message-ID: <CAGpPWDY_FivTFSQnUM5P5oCT9WX3+NSm61UHOSa2bERVMPH6ow@mail.gmail.com>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000f82e9f05e0fc494d"
X-Mailman-Approved-At: Thu, 09 Jun 2022 09:52:33 +0000
Subject: Re: [bitcoin-dev] Bitcoin covenants are inevitable
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, 09 Jun 2022 04:31:05 -0000

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

@jorge

> Who do you mean by "the non technical folks"?

I mean people that don't have software engineering skills. This is the
twittersphere, reddit, most podcasters, etc etc. This is the vast majority
of the bitcoin community, and the vast majority of.. everyone.

> You don't include alicexbt or yourself as a "technical folk", do you?

I have no idea what alicexbt's skillset is. I do include myself. I have a
degree in software engineering. I work as a programmer in the bitcoin
space. I have written papers on technical aspects of bitcoin. Why would you
assume that I'm not technical as someone who participates in the bitcoin
developers mailing list? Perhaps its projection?

On Wed, Jun 8, 2022 at 3:31 PM Jorge Tim=C3=B3n via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Who do you mean by "the non technical folks"?
> You don't include alicexbt or yourself as a "technical folk", do you?
>
>
> On Wed, Jun 8, 2022 at 8:38 AM Billy Tetrud via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> Wholeheartedly agree with you alicexbt. There are no technical issues
>> that have been shown that I'm aware of. Once the non-technical folks hav=
e
>> time to discuss it and realize that, I'm hopeful things will move forwar=
d.
>> Perhaps we can learn from this and figure out how to better catch the
>> attention of the larger bitcoin community  for important changes without
>> alarming them.
>>
>> On Sun, Jun 5, 2022 at 2:48 AM alicexbt via bitcoin-dev <
>> bitcoin-dev@lists.linuxfoundation.org> wrote:
>>
>>> Hi Jorge,
>>>
>>>
>>> Misinformation is false or inaccurate information, especially that whic=
h
>>> is deliberately intended to deceive. A combination of 'misleading' and
>>> 'information'. Here are a few examples and I am sure I missed a lot of
>>> others but its difficult for me to keep a track of everything:
>>>
>>>
>>> 1) Sapio is open source and everything mentioned in tweet is false:
>>> https://web.archive.org/web/20220503050140/https://twitter.com/coinable=
S/status/1521354192434073602
>>>
>>> 2) Personal attacks on author of BIP 119 with false information:
>>> https://nitter.net/s3cp256k1/status/1521238634111770624
>>>
>>> 3) Andreas Antonopoulos shared false things about CTV and explained by
>>> Ryan in this email:
>>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-May/020414=
.html
>>>
>>> 4) Misleading things shared in these emails by Michael Folkson:
>>>
>>>
>>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/01=
9728.html
>>>
>>>
>>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/0202=
35.html
>>>
>>>
>>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/0202=
86.html
>>>
>>>
>>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/0203=
43.html
>>>
>>>
>>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/0203=
86.html
>>>
>>> 5) Peter Todd and Zac shared misleading things about BIP 119, bitcoin
>>> and L2. I replied in this email:
>>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/0203=
22.html
>>>
>>> 6) Social media influencers like Peter McCormack tweeted they don't
>>> understand BIP 119 but its an attack (this was even retweeted by develo=
pers
>>> like Peter Todd):
>>> https://nitter.net/PeterMcCormack/status/1521253840963653632
>>>
>>> 7) Some misconceptions about BIP 119 cleared by Bitcoin Magazine:
>>> https://bitcoinmagazine.com/technical/what-is-bip-119-bitcoin-controver=
sy-explained
>>>
>>> 8) There were lies and misinformation about BIP 119 on social media
>>> according to this Bitcoin Magazine article:
>>> https://bitcoinmagazine.com/technical/analyzing-bip119-and-the-controve=
rsy-surrounding-it
>>>
>>> 9) John Carvalho tweeting false things:
>>>
>>>     https://nitter.net/BitcoinErrorLog/status/1468599535538745359
>>>
>>>     https://nitter.net/BitcoinErrorLog/status/1522652884218822658
>>>
>>>     https://nitter.net/BitcoinErrorLog/status/1442554615967354880
>>>
>>>     https://nitter.net/search?q=3DMIT%20(from%3ABitcoinErrorLog)
>>>
>>> 10) Greg Maxwell responding to misinformation related to BIP 119 but
>>> adding false things in the comments:
>>> https://www.reddit.com/r/Bitcoin/comments/uim560/bip_119/i7dhfpb/
>>>
>>>
>>> I am not surprised by your email but it would be better if the people
>>> who are interested in reviewing BIP 119 could raise the bar and not sha=
re
>>> misleading information.
>>>
>>>
>>> /dev/fd0
>>>
>>>
>>> Sent with Proton Mail secure email.
>>> ------- Original Message -------
>>> On Sunday, June 5th, 2022 at 12:12 AM, Jorge Tim=C3=B3n <jtimon@jtimon.=
cc>
>>> wrote:
>>>
>>>
>>> > "Some people say CTV is contentious, but they're spreading
>>> misinformation"? Really? Seriously?Come on, guys, we can do better than
>>> nina jankovich and the "fact checkers".
>>> > Please, rise the bar.
>>> > On Fri, Jun 3, 2022, 19:44 alicexbt via bitcoin-dev <
>>> bitcoin-dev@lists.linuxfoundation.org> wrote:
>>> >
>>> > > Note: This email is an opinion and not an attack on bitcoin
>>> > >
>>> > > Covenants on bitcoin will eventually be implemented with a soft
>>> fork. CTV is the easiest and best possible way OP_TX looks good as well=
.
>>> Apart from the technical merits, covenants will improve a few other thi=
ngs:
>>> > >
>>> > > - Developers can build interesting projects with real demand in
>>> market.
>>> > > - Students learn Sapio and not just solidity.
>>> > > - Better tooling could be available for application developers.
>>> > > - Maybe we see bitcoin developer hackathons in different countries.
>>> > > - Demand for block space might increase, it wont be just exchanges
>>> and coinjoin.
>>> > > - Funding of bitcoin developers and projects might improve. Wont
>>> need to convince a few people for grants.
>>> > >
>>> > > **Why covenants are not contentious?**
>>> > >
>>> > > Some people may write paragraphs about CTV being contentious, sprea=
d
>>> misinformation and do all types of drama, politics etc. on social media=
 but
>>> there are zero technical NACKs for CTV. We have discussed other covenan=
t
>>> proposals in detail on mailing list and IRC meetings with an open minde=
d
>>> approach.
>>> > >
>>> > > All the developers that participated in the discussion are either
>>> okay with CTV or OP_TX or covenants in general.
>>> > >
>>> > > **How and when should covenants be implemented in Bitcoin?**
>>> > >
>>> > > I don't think we should wait for years anticipating a proposal that
>>> everyone will agree on or argue for years to pretend changes are hard i=
n
>>> Bitcoin. We should improve the review process for soft fork BIPs and sh=
are
>>> honest opinions with agreement, disagreement on technical merits.
>>> > >
>>> > > I prefer BIP 8 or improved BIP 8 for soft fork but I won't mind
>>> anything else being used if that improves Bitcoin. Covenants implemente=
d in
>>> Bitcoin before the next cycle would provide opportunity for developers =
to
>>> build interesting things during the bear market. Ossification supporter=
s
>>> also believe there is some window that will close soon, maybe doing cha=
nges
>>> considering each case individually will be a better approach. CTV is no=
t a
>>> rushed soft fork, less people followed the research and it was not
>>> mentioned on social media repeatedly by the respected developers like o=
ther
>>> soft forks.
>>> > >
>>> > > /dev/fd0
>>> > >
>>> > >
>>> > > Sent with Proton Mail secure email.
>>> > > _______________________________________________
>>> > > bitcoin-dev mailing list
>>> > > bitcoin-dev@lists.linuxfoundation.org
>>> > > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>> _______________________________________________
>>> bitcoin-dev mailing list
>>> bitcoin-dev@lists.linuxfoundation.org
>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr">@jorge<br><div><br></div><div><div>&gt; Who do you mean by=
 &quot;the non technical folks&quot;?<br></div><div><br></div><div>I mean p=
eople that don&#39;t have software engineering skills. This is the twitters=
phere, reddit, most podcasters, etc etc. This is the vast majority of the b=
itcoin community, and the vast majority=C2=A0of.. everyone.=C2=A0</div><div=
><br></div><div>&gt; You don&#39;t include alicexbt or yourself as a &quot;=
technical folk&quot;, do you?</div></div><div><br></div><div>

I have no idea what alicexbt&#39;s skillset is.=20

I do include myself. I have a degree in software engineering. I work as a p=
rogrammer in the bitcoin space. I have written=C2=A0papers on technical=C2=
=A0aspects of bitcoin. Why would you assume that I&#39;m not technical as s=
omeone who participates in the bitcoin developers=C2=A0mailing=C2=A0list? P=
erhaps its projection?=C2=A0</div></div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Wed, Jun 8, 2022 at 3:31 PM Jorge Tim=
=C3=B3n via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfounda=
tion.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt; w=
rote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr"><div>Who do you mean by &quot;the non technical folks&quot;?<br></=
div><div>You don&#39;t include alicexbt or yourself as a &quot;technical fo=
lk&quot;, do you?</div><div><br></div></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jun 8, 2022 at 8:38 AM Billy =
Tetrud via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundat=
ion.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wr=
ote:<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 dir=3D=
"ltr">Wholeheartedly agree with you alicexbt. There are no technical issues=
 that have been shown that I&#39;m aware of. Once the non-technical folks h=
ave time to discuss it and realize that, I&#39;m hopeful things will move f=
orward. Perhaps we can learn from this and figure out how to better catch t=
he attention of the larger bitcoin community=C2=A0 for important=C2=A0chang=
es without alarming them.=C2=A0</div><br><div class=3D"gmail_quote"><div di=
r=3D"ltr" class=3D"gmail_attr">On Sun, Jun 5, 2022 at 2:48 AM alicexbt via =
bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" ta=
rget=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Jorge,<br>
<br>
<br>
Misinformation is false or inaccurate information, especially that which is=
 deliberately intended to deceive. A combination of &#39;misleading&#39; an=
d &#39;information&#39;. Here are a few examples and I am sure I missed a l=
ot of others but its difficult for me to keep a track of everything:<br>
<br>
<br>
1) Sapio is open source and everything mentioned in tweet is false: <a href=
=3D"https://web.archive.org/web/20220503050140/https://twitter.com/coinable=
S/status/1521354192434073602" rel=3D"noreferrer" target=3D"_blank">https://=
web.archive.org/web/20220503050140/https://twitter.com/coinableS/status/152=
1354192434073602</a><br>
<br>
2) Personal attacks on author of BIP 119 with false information: <a href=3D=
"https://nitter.net/s3cp256k1/status/1521238634111770624" rel=3D"noreferrer=
" target=3D"_blank">https://nitter.net/s3cp256k1/status/1521238634111770624=
</a><br>
<br>
3) Andreas Antonopoulos shared false things about CTV and explained by Ryan=
 in this email: <a href=3D"https://lists.linuxfoundation.org/pipermail/bitc=
oin-dev/2022-May/020414.html" rel=3D"noreferrer" target=3D"_blank">https://=
lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-May/020414.html</a><br=
>
<br>
4) Misleading things shared in these emails by Michael Folkson:<br>
<br>
=C2=A0 =C2=A0 <a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoi=
n-dev/2022-January/019728.html" rel=3D"noreferrer" target=3D"_blank">https:=
//lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019728.html<=
/a><br>
<br>
=C2=A0 =C2=A0 <a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoi=
n-dev/2022-April/020235.html" rel=3D"noreferrer" target=3D"_blank">https://=
lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020235.html</a><=
br>
<br>
=C2=A0 =C2=A0 <a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoi=
n-dev/2022-April/020286.html" rel=3D"noreferrer" target=3D"_blank">https://=
lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020286.html</a><=
br>
<br>
=C2=A0 =C2=A0 <a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoi=
n-dev/2022-April/020343.html" rel=3D"noreferrer" target=3D"_blank">https://=
lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020343.html</a><=
br>
<br>
=C2=A0 =C2=A0 <a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoi=
n-dev/2022-April/020386.html" rel=3D"noreferrer" target=3D"_blank">https://=
lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020386.html</a><=
br>
<br>
5) Peter Todd and Zac shared misleading things about BIP 119, bitcoin and L=
2. I replied in this email: <a href=3D"https://lists.linuxfoundation.org/pi=
permail/bitcoin-dev/2022-April/020322.html" rel=3D"noreferrer" target=3D"_b=
lank">https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/02=
0322.html</a><br>
<br>
6) Social media influencers like Peter McCormack tweeted they don&#39;t und=
erstand BIP 119 but its an attack (this was even retweeted by developers li=
ke Peter Todd): <a href=3D"https://nitter.net/PeterMcCormack/status/1521253=
840963653632" rel=3D"noreferrer" target=3D"_blank">https://nitter.net/Peter=
McCormack/status/1521253840963653632</a><br>
<br>
7) Some misconceptions about BIP 119 cleared by Bitcoin Magazine: <a href=
=3D"https://bitcoinmagazine.com/technical/what-is-bip-119-bitcoin-controver=
sy-explained" rel=3D"noreferrer" target=3D"_blank">https://bitcoinmagazine.=
com/technical/what-is-bip-119-bitcoin-controversy-explained</a><br>
<br>
8) There were lies and misinformation about BIP 119 on social media accordi=
ng to this Bitcoin Magazine article: <a href=3D"https://bitcoinmagazine.com=
/technical/analyzing-bip119-and-the-controversy-surrounding-it" rel=3D"nore=
ferrer" target=3D"_blank">https://bitcoinmagazine.com/technical/analyzing-b=
ip119-and-the-controversy-surrounding-it</a><br>
<br>
9) John Carvalho tweeting false things:<br>
<br>
=C2=A0 =C2=A0 <a href=3D"https://nitter.net/BitcoinErrorLog/status/14685995=
35538745359" rel=3D"noreferrer" target=3D"_blank">https://nitter.net/Bitcoi=
nErrorLog/status/1468599535538745359</a><br>
<br>
=C2=A0 =C2=A0 <a href=3D"https://nitter.net/BitcoinErrorLog/status/15226528=
84218822658" rel=3D"noreferrer" target=3D"_blank">https://nitter.net/Bitcoi=
nErrorLog/status/1522652884218822658</a><br>
<br>
=C2=A0 =C2=A0 <a href=3D"https://nitter.net/BitcoinErrorLog/status/14425546=
15967354880" rel=3D"noreferrer" target=3D"_blank">https://nitter.net/Bitcoi=
nErrorLog/status/1442554615967354880</a><br>
<br>
=C2=A0 =C2=A0 <a href=3D"https://nitter.net/search?q=3DMIT%20(from%3ABitcoi=
nErrorLog)" rel=3D"noreferrer" target=3D"_blank">https://nitter.net/search?=
q=3DMIT%20(from%3ABitcoinErrorLog)</a><br>
<br>
10) Greg Maxwell responding to misinformation related to BIP 119 but adding=
 false things in the comments: <a href=3D"https://www.reddit.com/r/Bitcoin/=
comments/uim560/bip_119/i7dhfpb/" rel=3D"noreferrer" target=3D"_blank">http=
s://www.reddit.com/r/Bitcoin/comments/uim560/bip_119/i7dhfpb/</a><br>
<br>
<br>
I am not surprised by your email but it would be better if the people who a=
re interested in reviewing BIP 119 could raise the bar and not share mislea=
ding information.<br>
<br>
<br>
/dev/fd0<br>
<br>
<br>
Sent with Proton Mail secure email.<br>
------- Original Message -------<br>
On Sunday, June 5th, 2022 at 12:12 AM, Jorge Tim=C3=B3n &lt;<a href=3D"mail=
to:jtimon@jtimon.cc" target=3D"_blank">jtimon@jtimon.cc</a>&gt; wrote:<br>
<br>
<br>
&gt; &quot;Some people say CTV is contentious, but they&#39;re spreading mi=
sinformation&quot;? Really? Seriously?Come on, guys, we can do better than =
nina jankovich and the &quot;fact checkers&quot;.<br>
&gt; Please, rise the bar.<br>
&gt; On Fri, Jun 3, 2022, 19:44 alicexbt via bitcoin-dev &lt;<a href=3D"mai=
lto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@li=
sts.linuxfoundation.org</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; Note: This email is an opinion and not an attack on bitcoin<br>
&gt; &gt;<br>
&gt; &gt; Covenants on bitcoin will eventually be implemented with a soft f=
ork. CTV is the easiest and best possible way OP_TX looks good as well. Apa=
rt from the technical merits, covenants will improve a few other things:<br=
>
&gt; &gt;<br>
&gt; &gt; - Developers can build interesting projects with real demand in m=
arket.<br>
&gt; &gt; - Students learn Sapio and not just solidity.<br>
&gt; &gt; - Better tooling could be available for application developers.<b=
r>
&gt; &gt; - Maybe we see bitcoin developer hackathons in different countrie=
s.<br>
&gt; &gt; - Demand for block space might increase, it wont be just exchange=
s and coinjoin.<br>
&gt; &gt; - Funding of bitcoin developers and projects might improve. Wont =
need to convince a few people for grants.<br>
&gt; &gt;<br>
&gt; &gt; **Why covenants are not contentious?**<br>
&gt; &gt;<br>
&gt; &gt; Some people may write paragraphs about CTV being contentious, spr=
ead misinformation and do all types of drama, politics etc. on social media=
 but there are zero technical NACKs for CTV. We have discussed other covena=
nt proposals in detail on mailing list and IRC meetings with an open minded=
 approach.<br>
&gt; &gt;<br>
&gt; &gt; All the developers that participated in the discussion are either=
 okay with CTV or OP_TX or covenants in general.<br>
&gt; &gt;<br>
&gt; &gt; **How and when should covenants be implemented in Bitcoin?**<br>
&gt; &gt;<br>
&gt; &gt; I don&#39;t think we should wait for years anticipating a proposa=
l that everyone will agree on or argue for years to pretend changes are har=
d in Bitcoin. We should improve the review process for soft fork BIPs and s=
hare honest opinions with agreement, disagreement on technical merits.<br>
&gt; &gt;<br>
&gt; &gt; I prefer BIP 8 or improved BIP 8 for soft fork but I won&#39;t mi=
nd anything else being used if that improves Bitcoin. Covenants implemented=
 in Bitcoin before the next cycle would provide opportunity for developers =
to build interesting things during the bear market. Ossification supporters=
 also believe there is some window that will close soon, maybe doing change=
s considering each case individually will be a better approach. CTV is not =
a rushed soft fork, less people followed the research and it was not mentio=
ned on social media repeatedly by the respected developers like other soft =
forks.<br>
&gt; &gt;<br>
&gt; &gt; /dev/fd0<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Sent with Proton Mail secure email.<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; bitcoin-dev mailing list<br>
&gt; &gt; <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=
=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a><br>
&gt; &gt; <a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bit=
coin-dev" rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundatio=
n.org/mailman/listinfo/bitcoin-dev</a><br>
_______________________________________________<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>
_______________________________________________<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>
_______________________________________________<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>

--000000000000f82e9f05e0fc494d--