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
|
Delivery-date: Mon, 22 Jul 2024 05:07:49 -0700
Received: from mail-yb1-f190.google.com ([209.85.219.190])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBDQJH5PWYQERBDEX7G2AMGQENWB5TQQ@googlegroups.com>)
id 1sVrpT-0001ER-Uj
for bitcoindev@gnusha.org; Mon, 22 Jul 2024 05:07:49 -0700
Received: by mail-yb1-f190.google.com with SMTP id 3f1490d57ef6-e02b5792baasf9133082276.2
for <bitcoindev@gnusha.org>; Mon, 22 Jul 2024 05:07:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1721650061; x=1722254861; darn=gnusha.org;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:reply-to:x-original-sender
:mime-version:subject:references:in-reply-to:message-id:to:from:date
:from:to:cc:subject:date:message-id:reply-to;
bh=7xjW5odPstEfY8gOhrXxhwgxRPA+qG2dsL9GHjDYslg=;
b=JztG7Cl4J1rW5/GmKPex0z4Fm0FHeCWTEE6EGpiBXBngUBYbdC4FjoG79umdiUmCeu
ZGFYjoaANCMeylEDbqNecKibw6D+ZyAMCzavCwh6eJ24H9FT3oHEFbRTfd1LPZttVeLk
87G+r6q+XQDp4UMUrWsmHLrl4OcHgO6U4fXz2oNgGI5v2C53mZ47HmBHmhUXyreiRm2n
9T5X/LNxMgIByU6zdpkbXh7V5W2qy5aPcDqbrySPYYW5KWvLOiYHavEYKUGYMcgTMivK
6SS4vXmScHYw1GFylKp8YKYa0g3H5CaHLVVHz2PXB2nlGIWDt+70P3SH1lkH/8OaJiS2
MnNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1721650061; x=1722254861;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:reply-to:x-original-sender
:mime-version:subject:references:in-reply-to:message-id:to:from:date
:x-beenthere:x-gm-message-state:from:to:cc:subject:date:message-id
:reply-to;
bh=7xjW5odPstEfY8gOhrXxhwgxRPA+qG2dsL9GHjDYslg=;
b=SuB0Ac8Jn2lG36O+ZwOiyTqrOUvK3UiDN+f5qm2wGGNMcVJaRQedujCUORETpewFkt
R7s9tLFinSLNsDXVJGPh3WDxntgvCnaeLxXxEjhALDoxqskG/oyrNv1m3A6IuEL0Z4Kp
NgVdmEX21KW5i6DqZo/yMp1I8E7PRRC5LdsxJ9gvBUJy8F9ul4ACinWpsRoodZk6cDJI
bu2rSyssRgluE6JgJN/0n14u30dZ7mbx/Ex1hnU9OWCgvWqDVJbzJqBmdrD6YlMLHSaF
OKVD7AKeDUcvFrWNPt6lSvHIbFv3w1wOjzZKC13+cHvwZ7UdpJ72yI+I2kAr36YEch6I
WQiw==
X-Forwarded-Encrypted: i=1; AJvYcCX43FZA8yDfTkuhtuj8WqIxkxtEiKcUORmlDlcWsDtk6QShZAnF/tk5urzT/jttUk+X7LYshcXyO8CApsI41UylM1TVBWQ=
X-Gm-Message-State: AOJu0YyYw22GitWEDM/AYlSJfQvCudtT239gnN9VEJcDgYCGL92qQYIm
Mn6whvyHNowxAcHne96kzmYj2ds2t6Rb1Cewf6R8F7deOCZ42kkX
X-Google-Smtp-Source: AGHT+IHhhEp/KgE4j/wXMpuChY0Y9mZo/A6DkcpDGr45RuRCUNGXVWt8Q/O4LHY2+WqgcVt8KbpQXw==
X-Received: by 2002:a05:6902:1201:b0:e05:fc30:7057 with SMTP id 3f1490d57ef6-e087067957cmr8267559276.43.1721650061409;
Mon, 22 Jul 2024 05:07:41 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com
Received: by 2002:a25:f912:0:b0:e03:6457:383f with SMTP id 3f1490d57ef6-e05fdb408a3ls6326216276.1.-pod-prod-09-us;
Mon, 22 Jul 2024 05:07:40 -0700 (PDT)
X-Received: by 2002:a05:690c:d81:b0:61d:4701:5e66 with SMTP id 00721157ae682-66a63a71ec9mr5890037b3.2.1721650060022;
Mon, 22 Jul 2024 05:07:40 -0700 (PDT)
Received: by 2002:a05:690c:2d11:b0:66a:8967:a513 with SMTP id 00721157ae682-66a8967cff9ms7b3;
Sun, 21 Jul 2024 18:59:53 -0700 (PDT)
X-Received: by 2002:a05:690c:38b:b0:62d:a29:537e with SMTP id 00721157ae682-66a663575camr4672187b3.4.1721613592511;
Sun, 21 Jul 2024 18:59:52 -0700 (PDT)
Date: Sun, 21 Jul 2024 18:59:52 -0700 (PDT)
From: "'Anonymous User' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <3f7d43bd-af9e-4af5-860a-223504bb4fcan@googlegroups.com>
In-Reply-To: <a8eac5f2-b85a-434f-868e-eba7fd2558c6@achow101.com>
References: <Zpk7EYgmlgPP3Y9D@petertodd.org>
<18fc443d-c347-4a84-94fe-81308ae20b76n@googlegroups.com>
<Zpm73WHBNIkkIT0Y@petertodd.org>
<CALZpt+HJvBXM_geK7JC8umrt1goq8bc+pnY0mk+o+r_+bjrtew@mail.gmail.com>
<Zpp6U00Mp7Z/bOej@petertodd.org>
<4d950527-4430-49f2-8e38-3755bc58e301n@googlegroups.com>
<4f7eddff-9e2d-4beb-bcc6-832584cb939d@achow101.com>
<2aa2d6fa-ae72-4aef-9fda-49e2f7c657abn@googlegroups.com>
<a8eac5f2-b85a-434f-868e-eba7fd2558c6@achow101.com>
Subject: Re: [bitcoindev] Re: A "Free" Relay Attack Taking Advantage of The
Lack of Full-RBF In Core
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_342116_216611184.1721613592246"
X-Original-Sender: situo@berkeley.edu
X-Original-From: Anonymous User <situo@berkeley.edu>
Reply-To: Anonymous User <situo@berkeley.edu>
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com
List-ID: <bitcoindev.googlegroups.com>
X-Google-Group-Id: 786775582512
List-Post: <https://groups.google.com/group/bitcoindev/post>, <mailto:bitcoindev@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:bitcoindev+help@googlegroups.com>
List-Archive: <https://groups.google.com/group/bitcoindev
List-Subscribe: <https://groups.google.com/group/bitcoindev/subscribe>, <mailto:bitcoindev+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+786775582512+unsubscribe@googlegroups.com>,
<https://groups.google.com/group/bitcoindev/subscribe>
X-Spam-Score: -1.0 (-)
------=_Part_342116_216611184.1721613592246
Content-Type: multipart/alternative;
boundary="----=_Part_342117_6754146.1721613592246"
------=_Part_342117_6754146.1721613592246
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
I came from some twitter discussion so I think this thread is trending. I=
=20
think we need to figure a way out onward.=20
Here is a last resort solution by launching this attack in production. We=
=20
should avoid making this last resort solution, but from what Peter Todd=20
said, below seems completely practical.
Please treat it as story reading and do not overthink that this is the way=
=20
to go.
- a few people in the list form a group and fork bitcoin core and apply the=
=20
patch from Peter Todd
- work with a few miners to massively perform the free relay attacks and=20
other mempool related attacks in an effort to force mining pools and miners=
=20
to switch from bitcoin core into the fork in order for their nodes to=20
continue running in a healthy manner
- build a free service for file transfer or VPN taking advantage of rbf in=
=20
the Bitcoin network and make it a public good that millions of users can=20
use, causing most of the mempool transactions to be conflicting (due to=20
different implementations of rbf) and therefore wallets have to eventually=
=20
stop broadcasting transactions to bitcoin core nodes (which could be using=
=20
a completely new list of seed nodes, disabling the existing seed node=20
list), and non-bitcoin-core nodes, in order to have more healthy=20
transaction flows and mempool data sharing, would start node-shopping by=20
disconnecting themselves from bitcoin core nodes and refusing to be their=
=20
peers=20
- core is forced to find a way onward, or the core gives up and archives=20
the bitcoin core repo
The damage is probably just a few days of slower transaction processing,=20
much smaller than the price spike caused by ordinals last year.=20
Democracy starts with people having different opinions that DO NOT need to=
=20
reconcile. So, it is not about how we get different people in this mail=20
list, or the non-public security list, to achieve the same opinions, like=
=20
whether full RBF is needed. It is about how Bitcoin can allow two groups of=
=20
people that have fundamentally different opinions and are unwilling and=20
impossible to reconcile. We can have 5-10 security disclosure mail lists by=
=20
different groups of people, and good-faith vulnerability reporters can=20
choose to exclusively report the bugs to some groups that the reporters=20
feel to be knowledgeable and responsive and, importantly, have the capacity=
=20
and the motivation to work on it.=20
I feel bad for Peter Todd. If I were him, I wouldn't report the bug. I=20
would sell the bug because I got nothing in return, but probably more=20
jealousy or more retaliation for being the only person serious about an=20
issue.=20
Btw, Peter already has a fork.=20
Ethereum has great software development process as well as its ecosystem.=
=20
Smart contracts get heavily audited not because people care about security.=
=20
It is because North Korea has successfully stolen probably hundreds of=20
millions of dollars from different projects and even causing some projects=
=20
to fall apart. This is in essence similar to, if one day Bitcoin has a=20
memory exploit issue that causes a massive amount of miners to lose coins=
=20
that they own, and the network again needs to decide whether to do a hard=
=20
fork, that is the time when we will be discussing if stopping development=
=20
in C/C++ and limiting Bitcoin core development to Rust and Rust only are=20
the way forward.
Thanks,
Anonymous user, as the floppy disk guy recommends this might be the best=20
way to engage in the mailing list onward
I strongly encourage people to try engaging in this email list anonymously.=
=20
It feels great to say things out loud without worrying about retaliation on=
=20
unrelated matters. Also, this should be permitted. We still don't know who=
=20
Satoshi is. If I were Satoshi, I probably also wouldn't report a bug I=20
know.=20
On Sunday, July 21, 2024 at 1:49:10=E2=80=AFPM UTC-7 Ava Chow wrote:
> On 07/20/2024 10:06 PM, Antoine Riard wrote:
> > "Naive", as saying this is the _Bitcoin Core_ project list only can onl=
y=20
> > provoke blind
> > spot among the list members if the security issues are either affecting=
=20
> > old part of
> > the codebases that younger members have less experiences with (some=20
> > parts like consensus
> > or block-relay are modified only every 5 years) or novel factors from=
=20
> > upstream or downstream
> > (e.g the internet networking stack or implications on deployed contract=
=20
> > protocols like
> > lightning). On both the former and latter criterias, I think Peter=20
> > overly meets the bar.
>
> Peter was not the only "senior" person on the security list. Obviously I=
=20
> will not disclose non-public information, but certainly there are people=
=20
> on the security list who are just as, if not more, senior than Peter.
>
> Furthermore, the "old parts" still do get changed, and someone who no=20
> longer actively contributes to the project is more likely to be unaware=
=20
> of how the code actually works today, even if they are familiar with=20
> components that change infrequently.
>
> > When you've big sh*t hitting the fan like inflation bugs or level DB=20
> > 2013 unexpected fork you
> > prefer have experts with a decade of experience to collaborate with, an=
d=20
> > sharing the same cultural
> > and ethical norms of the active contributors evaluated by numbers on=20
> > commits on the last single-digit
> > years.
>
> Not being on the list does not preclude him from being consulted if the=
=20
> need arises.
>
> With the two examples you provide, I am not aware of Peter being=20
> actively involved in the resolution of both of those, whereas there are=
=20
> current members of the list who were.
>
>
> In general though, it is not clear to me how it was beneficial to have=20
> Peter on the security list, nor how not having him is directly harmful.=
=20
> In the 2 years that I have been on the security list, I was unaware that=
=20
> Peter was a recipient until shortly before he was removed. My=20
> understanding is that others who have been on the list longer than me=20
> were also unaware.
>
> Ava
>
> >=20
> > I'll repropose Peter admission on the security list mailing list in the=
=20
> > coming weeks by opening an
> > issue on the bitcoin-meta repository, once this current mailing list=20
> > thread has slowed down a bit,
> > or at least the technical analysis has been dissociated from the=20
> > proceedings which have all been
> > bundle in a big message. In my very personal opinion, I still trust mor=
e=20
> > Peter competence and experience
> > than some other people I know who are on the security mailing list.
> >=20
> > All that said I appreciate your answer and I'm satisfied from the=20
> > personal role you've have played
> > in the matter with, and be reassured I'll keep you among the recipient=
=20
> > of future security issues with
> > a potential impact on bitcoin core that I might find or be aware off.
> >=20
> > Best,
> > Antoine
> > ots hash:=20
> db441b51684ad3a6897f67d42c74ccfcb9a4ffed40d4bdbe30a2edd867ccdd54
> >=20
> > Le samedi 20 juillet 2024 =C3=A0 01:50:25 UTC+1, Ava Chow a =C3=A9crit =
:
> >=20
> > On 07/19/2024 07:58 PM, Antoine Riard wrote:
> > > As said in one my previous email, I'm still curious about achow101
> > > explaining publicly
> > > why you have been kicked-out of the bitcoin-security mailing
> > list, when
> > > you were certainly
> > > more senior than achow101 in matters of base-layer security
> > issues or
> > > even hard technical
> > > issues like consensus interactions (e.g bip65). I'll re-iterate my
> > > respect towards achow101
> > > as a maintainer from years of collaboration, though this is a topic
> > > worthy of an answer.
> >=20
> > I am not the one that removed Peter from the mailing list, nor do I
> > even
> > have the login(s) to do so.
> >=20
> > There was a discussion amongst several members of the security list
> > about who was on the list, and who should be on the list. Given that
> > the
> > security list is the _Bitcoin Core_ security list, we determined that
> > the people who should be on the list are people who still actively
> > contribute to the project. As Peter Todd no longer actively contribute
> > code nor code review to the project, we decided that it didn't make
> > sense to continue to have him on the list.
> >=20
> > My recollection is that multiple other people were removed from the
> > list
> > for the same reason at the same time.
> >=20
> > Ava
> >=20
> > --=20
> > You received this message because you are subscribed to the Google=20
> > Groups "Bitcoin Development Mailing List" group.
> > To unsubscribe from this group and stop receiving emails from it, send=
=20
> > an email to bitcoindev+...@googlegroups.com=20
> > <mailto:bitcoindev+...@googlegroups.com>.
> > To view this discussion on the web visit=20
> >=20
> https://groups.google.com/d/msgid/bitcoindev/2aa2d6fa-ae72-4aef-9fda-49e2=
f7c657abn%40googlegroups.com=20
> <
> https://groups.google.com/d/msgid/bitcoindev/2aa2d6fa-ae72-4aef-9fda-49e2=
f7c657abn%40googlegroups.com?utm_medium=3Demail&utm_source=3Dfooter
> >.
>
>
--=20
You received this message because you are subscribed to the Google Groups "=
Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/=
bitcoindev/3f7d43bd-af9e-4af5-860a-223504bb4fcan%40googlegroups.com.
------=_Part_342117_6754146.1721613592246
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div>I came from some twitter discussion so I think this thread is trending=
. I think we need to figure a way out onward.=C2=A0</div><div><br /></div><=
div>Here is a last resort solution by launching this attack in production. =
We should avoid making this last resort solution, but from what Peter Todd =
said, below seems completely practical.</div><div>Please treat it as story =
reading and do not overthink that this is the way to go.</div><div><br /></=
div><div>- a few people in the list form a group and fork bitcoin core and =
apply the patch from Peter Todd</div><div>- work with a few miners to massi=
vely perform the free relay attacks and other mempool related attacks in an=
effort to force mining pools and miners to switch from bitcoin core into t=
he fork in order for their nodes to continue running in a healthy manner</d=
iv><div>- build a free service for file transfer or VPN taking advantage of=
rbf in the Bitcoin network and make it a public good that millions of user=
s can use, causing most of the mempool transactions to be conflicting (due =
to different implementations of rbf) and therefore wallets have to eventual=
ly stop broadcasting transactions to bitcoin core nodes (which could be usi=
ng a completely new list of seed nodes, disabling the existing seed node li=
st), and non-bitcoin-core nodes, in order to have more healthy transaction =
flows and mempool data sharing, would start node-shopping by disconnecting =
themselves from bitcoin core nodes and refusing to be their peers=C2=A0</di=
v><div>- core is forced to find a way onward, or the core gives up and arch=
ives the bitcoin core repo</div><div><br /></div><div>The damage is probabl=
y just a few days of slower transaction processing, much smaller than the p=
rice spike caused by ordinals last year.=C2=A0</div><div><br /></div><div>D=
emocracy starts with people having different opinions that DO NOT need to r=
econcile. So, it is not about how we get different people in this mail list=
, or the non-public security list, to achieve the same opinions, like wheth=
er full RBF is needed. It is about how Bitcoin can allow two groups of peop=
le that have fundamentally different opinions and are unwilling and impossi=
ble to reconcile. We can have 5-10 security disclosure mail lists by differ=
ent groups of people, and good-faith vulnerability reporters can choose to =
exclusively report the bugs to some groups that the reporters feel to be kn=
owledgeable and responsive and, importantly, have the capacity and the moti=
vation to work on it.=C2=A0<br /></div><div><br /></div><div>I feel bad for=
Peter Todd. If I were him, I wouldn't report the bug. I would sell the bug=
because I got nothing in return, but probably more jealousy or more=C2=A0r=
etaliation for being the only person serious about an issue.=C2=A0</div><di=
v>Btw, Peter already has a fork.=C2=A0</div><div><br /></div><div>Ethereum =
has great software development process as well as its ecosystem. Smart cont=
racts get heavily audited not because people care about security. It is bec=
ause North Korea has successfully stolen probably hundreds of millions of d=
ollars from different projects and even causing some projects to fall apart=
. This is in essence similar to, if one day Bitcoin has a memory exploit is=
sue that causes a massive amount of miners to lose coins that they own, and=
the network again needs to decide whether to do a hard fork, that is the t=
ime when we will be discussing if stopping development in C/C++ and limitin=
g Bitcoin core development to Rust and Rust only are the way forward.</div>=
<div><br /></div><div>Thanks,</div><div>Anonymous user, as the floppy disk =
guy recommends this might be the best way to engage in the mailing list onw=
ard</div><div><br /></div><div>I strongly encourage people to try engaging =
in this email list anonymously. It feels great to say things out loud witho=
ut worrying about retaliation on unrelated matters. Also, this should be pe=
rmitted. We still don't know who Satoshi is. If I were Satoshi, I probably =
also wouldn't report a bug I know.=C2=A0</div><br /><div class=3D"gmail_quo=
te"><div dir=3D"auto" class=3D"gmail_attr">On Sunday, July 21, 2024 at 1:49=
:10=E2=80=AFPM UTC-7 Ava Chow wrote:<br/></div><blockquote class=3D"gmail_q=
uote" style=3D"margin: 0 0 0 0.8ex; border-left: 1px solid rgb(204, 204, 20=
4); padding-left: 1ex;">On 07/20/2024 10:06 PM, Antoine Riard wrote:
<br>> "Naive", as saying this is the _Bitcoin Core_ project li=
st only can only=20
<br>> provoke blind
<br>> spot among the list members if the security issues are either affe=
cting=20
<br>> old part of
<br>> the codebases that younger members have less experiences with (som=
e=20
<br>> parts like consensus
<br>> or block-relay are modified only every 5 years) or novel factors f=
rom=20
<br>> upstream or downstream
<br>> (e.g the internet networking stack or implications on deployed con=
tract=20
<br>> protocols like
<br>> lightning). On both the former and latter criterias, I think Peter=
=20
<br>> overly meets the bar.
<br>
<br>Peter was not the only "senior" person on the security list. =
Obviously I=20
<br>will not disclose non-public information, but certainly there are peopl=
e=20
<br>on the security list who are just as, if not more, senior than Peter.
<br>
<br>Furthermore, the "old parts" still do get changed, and someon=
e who no=20
<br>longer actively contributes to the project is more likely to be unaware=
=20
<br>of how the code actually works today, even if they are familiar with=20
<br>components that change infrequently.
<br>
<br>> When you've big sh*t hitting the fan like inflation bugs or le=
vel DB=20
<br>> 2013 unexpected fork you
<br>> prefer have experts with a decade of experience to collaborate wit=
h, and=20
<br>> sharing the same cultural
<br>> and ethical norms of the active contributors evaluated by numbers =
on=20
<br>> commits on the last single-digit
<br>> years.
<br>
<br>Not being on the list does not preclude him from being consulted if the=
=20
<br>need arises.
<br>
<br>With the two examples you provide, I am not aware of Peter being=20
<br>actively involved in the resolution of both of those, whereas there are=
=20
<br>current members of the list who were.
<br>
<br>
<br>In general though, it is not clear to me how it was beneficial to have=
=20
<br>Peter on the security list, nor how not having him is directly harmful.=
=20
<br>In the 2 years that I have been on the security list, I was unaware tha=
t=20
<br>Peter was a recipient until shortly before he was removed. My=20
<br>understanding is that others who have been on the list longer than me=
=20
<br>were also unaware.
<br>
<br>Ava
<br>
<br>>=20
<br>> I'll repropose Peter admission on the security list mailing li=
st in the=20
<br>> coming weeks by opening an
<br>> issue on the bitcoin-meta repository, once this current mailing li=
st=20
<br>> thread has slowed down a bit,
<br>> or at least the technical analysis has been dissociated from the=
=20
<br>> proceedings which have all been
<br>> bundle in a big message. In my very personal opinion, I still trus=
t more=20
<br>> Peter competence and experience
<br>> than some other people I know who are on the security mailing list=
.
<br>>=20
<br>> All that said I appreciate your answer and I'm satisfied from =
the=20
<br>> personal role you've have played
<br>> in the matter with, and be reassured I'll keep you among the r=
ecipient=20
<br>> of future security issues with
<br>> a potential impact on bitcoin core that I might find or be aware o=
ff.
<br>>=20
<br>> Best,
<br>> Antoine
<br>> ots hash: db441b51684ad3a6897f67d42c74ccfcb9a4ffed40d4bdbe30a2edd8=
67ccdd54
<br>>=20
<br>> Le samedi 20 juillet 2024 =C3=A0 01:50:25 UTC+1, Ava Chow a =C3=A9=
crit=C2=A0:
<br>>=20
<br>> On 07/19/2024 07:58 PM, Antoine Riard wrote:
<br>> > As said in one my previous email, I'm still curious =
about achow101
<br>> > explaining publicly
<br>> > why you have been kicked-out of the bitcoin-security mai=
ling
<br>> list, when
<br>> > you were certainly
<br>> > more senior than achow101 in matters of base-layer secur=
ity
<br>> issues or
<br>> > even hard technical
<br>> > issues like consensus interactions (e.g bip65). I'll=
re-iterate my
<br>> > respect towards achow101
<br>> > as a maintainer from years of collaboration, though this=
is a topic
<br>> > worthy of an answer.
<br>>=20
<br>> I am not the one that removed Peter from the mailing list, nor=
do I
<br>> even
<br>> have the login(s) to do so.
<br>>=20
<br>> There was a discussion amongst several members of the security=
list
<br>> about who was on the list, and who should be on the list. Give=
n that
<br>> the
<br>> security list is the _Bitcoin Core_ security list, we determin=
ed that
<br>> the people who should be on the list are people who still acti=
vely
<br>> contribute to the project. As Peter Todd no longer actively co=
ntribute
<br>> code nor code review to the project, we decided that it didn&#=
39;t make
<br>> sense to continue to have him on the list.
<br>>=20
<br>> My recollection is that multiple other people were removed fro=
m the
<br>> list
<br>> for the same reason at the same time.
<br>>=20
<br>> Ava
<br>>=20
<br>> --=20
<br>> You received this message because you are subscribed to the Google=
=20
<br>> Groups "Bitcoin Development Mailing List" group.
<br>> To unsubscribe from this group and stop receiving emails from it, =
send=20
<br>> an email to <a href data-email-masked rel=3D"nofollow">bitcoindev+=
...@googlegroups.com</a>=20
<br>> <mailto:<a href data-email-masked rel=3D"nofollow">bitcoindev+.=
..@googlegroups.com</a>>.
<br>> To view this discussion on the web visit=20
<br>> <a href=3D"https://groups.google.com/d/msgid/bitcoindev/2aa2d6fa-a=
e72-4aef-9fda-49e2f7c657abn%40googlegroups.com" target=3D"_blank" rel=3D"no=
follow" data-saferedirecturl=3D"https://www.google.com/url?hl=3Den&q=3D=
https://groups.google.com/d/msgid/bitcoindev/2aa2d6fa-ae72-4aef-9fda-49e2f7=
c657abn%2540googlegroups.com&source=3Dgmail&ust=3D1721699937499000&=
amp;usg=3DAOvVaw3JOhcYcqwB56VabiynSMa8">https://groups.google.com/d/msgid/b=
itcoindev/2aa2d6fa-ae72-4aef-9fda-49e2f7c657abn%40googlegroups.com</a> <=
<a href=3D"https://groups.google.com/d/msgid/bitcoindev/2aa2d6fa-ae72-4aef-=
9fda-49e2f7c657abn%40googlegroups.com?utm_medium=3Demail&utm_source=3Df=
ooter" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=3D"https://w=
ww.google.com/url?hl=3Den&q=3Dhttps://groups.google.com/d/msgid/bitcoin=
dev/2aa2d6fa-ae72-4aef-9fda-49e2f7c657abn%2540googlegroups.com?utm_medium%3=
Demail%26utm_source%3Dfooter&source=3Dgmail&ust=3D1721699937499000&=
amp;usg=3DAOvVaw36PPWcBQurpSiSdteuW7C5">https://groups.google.com/d/msgid/b=
itcoindev/2aa2d6fa-ae72-4aef-9fda-49e2f7c657abn%40googlegroups.com?utm_medi=
um=3Demail&utm_source=3Dfooter</a>>.
<br>
<br></blockquote></div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/3f7d43bd-af9e-4af5-860a-223504bb4fcan%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/3f7d43bd-af9e-4af5-860a-223504bb4fcan%40googlegroups.com</a>.=
<br />
------=_Part_342117_6754146.1721613592246--
------=_Part_342116_216611184.1721613592246--
|