From mboxrd@z Thu Jan 1 00:00:00 1970
Delivery-date: Tue, 02 Apr 2024 12:04:23 -0700
Received: from mail-ot1-f64.google.com ([209.85.210.64])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBDD7VM4YZ4NBBLVNWGYAMGQEFZDO44A@googlegroups.com>)
id 1rrjQj-0003vR-S5
for bitcoindev@gnusha.org; Tue, 02 Apr 2024 12:04:23 -0700
Received: by mail-ot1-f64.google.com with SMTP id 46e09a7af769-6e6864c33e0sf6631204a34.0
for <bitcoindev@gnusha.org>; Tue, 02 Apr 2024 12:04:21 -0700 (PDT)
ARC-Seal: i=2; a=rsa-sha256; t=1712084655; cv=pass;
d=google.com; s=arc-20160816;
b=jJUCvuDwFdpCrmqdNJyQL4n8RkBwa4tuWnWZ7ItPqRRtn55TnBEUkF/wgrPIslW+Qg
LODPSxSdE0cWDWqpd9mIYw9g08Y+8eSRBj5aszoL6Y5dO5UKsZemU18MnUW7YvSI6wCQ
iXD3o3fbSkAPfq18nota6rcqkXoC9+/VCXdO4+oij+SM8yxjHAYTOsmuDHOt3xAibmmK
f+4DY4TgUlTIvPkasKxScX9AcIwBCKEjZEqifLtDPqcUVteVsWHoECnyCU6o3dCui5ak
VrjT7KZq/zj1XqSnM0DUQ2lf0Tcf1xl6HD3bYU0ma335fRrhZpgFdrkqpZrSTxeaCXg8
NU0g==
ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:content-transfer-encoding
:mime-version:message-id:references:in-reply-to:user-agent:subject
:to:from:date:sender:dkim-signature;
bh=cu7rtj5HWfuqEnHfSsJOJqR5XQEzOVkpvCrqrbD+xkg=;
fh=84Zqos9IIgp8oXdlZAF+kcxrZ606Gw7F/FysVIUcVCo=;
b=Sk3mxW/V3luw6tSuQEKh4HV5aqMlXpzkm8PX2OmHWABxheBOjbf2BMT5CMkg9vwn5s
fQw2Yj/a43SBt9wjikdlTdbp5JCyUnbSp+2s9m+1lBsw5nsOhGTMdxVb5yud+X/Cc5cj
CNSvP/n82sxVexG2nbRcW7F+VJ7rA4v3+0LEj8+vxH1YSslXOeDsuHOOKqI9uAo0T3fD
fk+s/icivYc9SCsrLWRNo8I1QzMyTuADaMuBBDt3Imw3ZHzVi+zfEyLjUBz4ypmMrciu
LWfsT3CJyVrr+O8StpIJ7fW7kzqoAPxUcQVteTuw4eKtunO+xNdlUrjuEc4IPZCo8BsG
wXSw==;
darn=gnusha.org
ARC-Authentication-Results: i=2; gmr-mx.google.com;
dkim=pass (test mode) header.i=@dashjr.org header.s=zinan header.b=nMBV9qIP;
spf=pass (google.com: domain of luke@dashjr.org designates 192.3.11.21 as permitted sender) smtp.mailfrom=luke@dashjr.org;
dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=dashjr.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1712084655; x=1712689455; darn=gnusha.org;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-authentication-results
:x-original-sender:content-transfer-encoding:mime-version:message-id
:references:in-reply-to:user-agent:subject:to:from:date:sender:from
:to:cc:subject:date:message-id:reply-to;
bh=cu7rtj5HWfuqEnHfSsJOJqR5XQEzOVkpvCrqrbD+xkg=;
b=HNiJV2MKCUWqNNyPkjO0iPDtVSHXaNzVVws1vivwWS5dLzpvtIl+l0XJVS9dvYQbEj
RGa9G6CLLrTDk3MwtKcVj/CTJpaIjGLbfd+qnnTP5Oo5vOUjAKYu9zWgCXjgq++ZBhjr
/Y9PIQICZLkj/VIjmcOvp1poXh0pGW5RzO0PBBShedgFeBQIsJ4WU4O14G9j2+ydd4aS
ymbfC22GEPhGLDAlWX9Fe8DCt+esvBmvF97nJm+PtvfSne4MuOqW0FOxAjVykkNcmW2g
4MYznWduVN8A8UNu8oIer0E3v7/5BnmhYDLuYR+2TVs1crPd431xNZ23kqHacF++Htik
ealA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1712084655; x=1712689455;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-authentication-results
:x-original-sender:content-transfer-encoding:mime-version:message-id
:references:in-reply-to:user-agent:subject:to:from:date:x-beenthere
:x-gm-message-state:sender:from:to:cc:subject:date:message-id
:reply-to;
bh=cu7rtj5HWfuqEnHfSsJOJqR5XQEzOVkpvCrqrbD+xkg=;
b=Cpn/srCrBqmXPmq7jlg5RQVUnXFxjiCs4xjUJgkzr/r9eSyqMZPtTYn2a47zc7zoPl
oLBnK2DC3SkF80xWiC0sTJJAxpO/3PZYgkIiUhFEipEDTvoBuK0wzZY68U+9+31XOt9z
upx7bSy0U7WPwSy99TL0hHctOvPoq2EjMrxGqULL49hXyeRs6FK0cFB9UHjlMMJqBviz
kQutY2KuLITLxi+8CN2rhX3VS7kvZ1I6FxzmpTdlClYCgqTXLmFa5DuMd6cOkDkazS0S
2hUJbUKgwLBMPLL63qVGsmGHjGr5aNCH38kMnrz/HUUsCBcZqPwvAzZvts5dlccO7Vnt
AlJw==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=2; AJvYcCXmRZ6ZpbrZni+Fz5J7R2sWfX2h1Kxft3O/vTqgudEay1hd2JaNH6fFJ9AX09W13bz/TWLUyDeOd3iAsjVd3WeDP4vMIxM=
X-Gm-Message-State: AOJu0Yyn7QBLaodOYtu3WTBUDzqV2c5kM5xyLT7htsgziq5/eFgxUiVy
D3WIM1N9RBqDm0NZ5YGq2TXC1Asn4VlH1n0rprpGPgh7IfvQ2hFT
X-Google-Smtp-Source: AGHT+IFlKfdYr1In8Ejkj7ILpzLvSjfYDjMjtLHxU2VTtFrdO6/qs+SuPPEexCKFhhh7fyDnalc4HA==
X-Received: by 2002:a05:6871:3a2c:b0:220:941d:18b7 with SMTP id pu44-20020a0568713a2c00b00220941d18b7mr663882oac.59.1712084655083;
Tue, 02 Apr 2024 12:04:15 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com
Received: by 2002:a05:6870:780a:b0:22a:b2ba:b4cf with SMTP id
hb10-20020a056870780a00b0022ab2bab4cfls975121oab.0.-pod-prod-08-us; Tue, 02
Apr 2024 12:04:14 -0700 (PDT)
X-Forwarded-Encrypted: i=2; AJvYcCX6cigrd0/0VvnWialqspmjV40XrfHxNU+L4kT9lBgbdXHAat4uYQrhdh8Wll9ML/6qyzVkbxMgvsvnrQJAjldoRBM48SSREHVUJiA=
X-Received: by 2002:a05:6871:33a5:b0:22a:53b5:d5ce with SMTP id ng37-20020a05687133a500b0022a53b5d5cemr546962oac.3.1712084654273;
Tue, 02 Apr 2024 12:04:14 -0700 (PDT)
Received: by 2002:a05:6808:189c:b0:3c4:f6ee:b071 with SMTP id 5614622812f47-3c4f6eeb13fmsb6e;
Tue, 2 Apr 2024 08:39:47 -0700 (PDT)
X-Forwarded-Encrypted: i=2; AJvYcCU8ldm5q0bOLTxifZ0AaLiigzfdnvaTvto4wTcfYVVyD9WVH4QamAuGoXf85F02zGgqpf2TszZhpF7aZNeC3G+pplElQqVKPi9v2AQ=
X-Received: by 2002:a05:6602:4fd4:b0:7d0:c8c1:e5cf with SMTP id gs20-20020a0566024fd400b007d0c8c1e5cfmr91675iob.16.1712072386311;
Tue, 02 Apr 2024 08:39:46 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1712072386; cv=none;
d=google.com; s=arc-20160816;
b=qaZrKNGYCepVjX5/1ZWJHt8LYwFso4Z+wQFik0OfZ0yeFDhkWC0mFmrWMUyONz4ly4
1eDy94tOCqLYbbcQfTzOzVnrc1teobE+6/Q6nUkfRRNRhuvRmf5CIHHHE1RFRkq9DVDj
u53oNbEsRr1QQsw9d1R2zu0Glv3p6bpje9X4zlOug4mzL2UNRElJy6ek6bZDrAGq07qj
Hvr8H2NRA+q2lc4DQrYFmddvS2P4aaXEiEHhQxbhB4oyOU0Y2pRa5PVsPFWYUyphOORd
X6XeVPfzMQti9/dkIVQVWgDRx6fRS6pDBuq1fHIkoylXeHwiApbXozAzGX96kO3KOnQ1
5r6w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=content-transfer-encoding:mime-version:message-id:references
:in-reply-to:user-agent:subject:to:from:date:dkim-signature;
bh=wgdEeEcn8Mfo7vUzWbMqyQ0FAHVD7CKustJE+arTP5A=;
fh=Ov9DU4HXk6JZswSWHOSd4fYxLlDHbgqPo0GpF8UZRzM=;
b=CEKAMVzaTxot/G2NYUDsd76AitPYZZd0aVojnmhd2YqeyZRxS7C+/rqQ17TzV6NZ9D
RHEg7ZeU7STK3P7u+5giibTF9wB/5dwKyw+NcCNii2uvY1mDi0Sed1tEYGFcaeJ6a6h5
ZrHdZ6sBEw6To98ihbXXIAqknc6nc0chDI3mQ6YXAHCGAasj0G/niupXDb1UiOKL0nqu
UjpYPNWnc4l9v8fo1kJ169ZXqp5M0q9yyTPRXPHtE2Z82otecHg0XTWn7WKyFt9vXdiI
8D88ULWxPENZjpzLYCFf7C98RHZG3Vsoq6Anp3EeWwC8eOMPb5/utn8NdxCDU8S6dnq7
Qh+A==;
dara=google.com
ARC-Authentication-Results: i=1; gmr-mx.google.com;
dkim=pass (test mode) header.i=@dashjr.org header.s=zinan header.b=nMBV9qIP;
spf=pass (google.com: domain of luke@dashjr.org designates 192.3.11.21 as permitted sender) smtp.mailfrom=luke@dashjr.org;
dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=dashjr.org
Received: from zinan.dashjr.org (zinan.dashjr.org. [192.3.11.21])
by gmr-mx.google.com with ESMTP id h30-20020a05660208de00b007d0cd1d9ae1si276765ioz.2.2024.04.02.08.39.45
for <bitcoindev@googlegroups.com>;
Tue, 02 Apr 2024 08:39:45 -0700 (PDT)
Received-SPF: pass (google.com: domain of luke@dashjr.org designates 192.3.11.21 as permitted sender) client-ip=192.3.11.21;
Received: from [127.0.0.1] (unknown [172.58.160.235])
(Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id C774B2219F0;
Tue, 2 Apr 2024 15:39:35 +0000 (UTC)
X-Hashcash: 1:23:240402:bitcoindev@googlegroups.com::i=5uy6agwI1qhilc:vEDx
X-Hashcash: 1:23:240402:gloria@brink.dev::ujUghmt+GlznEd/L:q4N
Date: Tue, 02 Apr 2024 09:39:25 -0600
From: Luke Dashjr <luke@dashjr.org>
To: bitcoindev@googlegroups.com, Gloria Zhao <gloria@brink.dev>,
Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: Adding New BIP Editors
User-Agent: K-9 Mail for Android
In-Reply-To: <a18850ec-4659-4683-8e50-9758a7f431can@googlegroups.com>
References: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com> <d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n@googlegroups.com> <52a0d792-d99f-4360-ba34-0b12de183fef@murch.one> <84309c3f-e848-d333-fd28-bdd55899b713@netpurgatory.com> <9baa15e4-062d-478f-8c87-8ff19ab79989@murch.one> <4c1462b7-ea1c-4a36-be81-7c3719157fabn@googlegroups.com> <6806b22d-043d-4201-841a-95e17cd8d542@mattcorallo.com> <77554baa9330c57361c65c1fc85557f1@dtrt.org> <cbb0b74f-c60b-4c8a-9e97-9b1c0e0eb047n@googlegroups.com> <f14cf0de-20f2-4786-bb92-d686a73c1218@achow101.com> <16a728e9-e987-4e7b-bace-2629143d173fn@googlegroups.com> <64FDB7CF-CBFB-416D-8BCF-2DC50CD2E4B7@dashjr.org> <a18850ec-4659-4683-8e50-9758a7f431can@googlegroups.com>
Message-ID: <847D8B06-9F61-4515-B6B2-6093E7F7A80D@dashjr.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary=----MPPR57GVYMXD8IFGOQT5GBOIK9CB1V
Content-Transfer-Encoding: 7bit
X-Original-Sender: luke@dashjr.org
X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass (test
mode) header.i=@dashjr.org header.s=zinan header.b=nMBV9qIP; spf=pass
(google.com: domain of luke@dashjr.org designates 192.3.11.21 as permitted
sender) smtp.mailfrom=luke@dashjr.org; dmarc=pass (p=NONE sp=NONE
dis=NONE) header.from=dashjr.org
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: -0.7 (/)
------MPPR57GVYMXD8IFGOQT5GBOIK9CB1V
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
On the timeline, there has already been a very reasonable objection raised =
by Antoine. I'm also unlikely to be available around that time (and through=
the weekend) to actually do it. So it'll need to be next week at the earli=
est, but I don't see a problem with closer to May if that's important to so=
me.
Luke
On April 2, 2024 9:13:46 AM CST, Gloria Zhao <gloria@brink.dev> wrote:
>> If we are all just in a holding pattern, perhaps we could timebox this=
=20
>> decision process: how about we invite arguments for and against any=20
>> candidates in this thread until next Friday EOD (April 5th). If any=20
>> candidates find broad support, those candidates could be added as new=20
>> editors to the repository on the following Monday (April 8th).
>
>Thanks, ACK this timeline for moving forward.
>
>Assuming they are willing, I am in favor of adding Murch, Ruben, and=20
>Kanzure as BIP editors. They have all demonstrated through years of=20
>experience contributing to / moderating {the mailing list, stack exchange,=
=20
>Optech} that they have the technical expertise, skills in technical=20
>documentation, and track record of good judgement appropriate for this rol=
e.
>
>Best,
>Gloria
>
>On Tuesday, April 2, 2024 at 3:30:58=E2=80=AFPM UTC+1 Luke Dashjr wrote:
>
>> No, there was no such refusal. The ONLY issue at hand with regard to mor=
e=20
>> BIP editors is that I don't have time to keep up with it by myself. If y=
our=20
>> goal is anything else, please sit this discussion out (aside from perhap=
s=20
>> reasonable objections to new editors). BIP number assignments are trivia=
l=20
>> and not a concern.
>>
>> It seems there's an attempt to take advantage of the need for more BIP=
=20
>> editors to change or bypass the BIP process without proper procedures=20
>> followed. While there may be arguments for improving the BIP process, th=
at=20
>> is unrelated and would need to go through a BIP, not simply fiat of a ne=
w=20
>> editor. Any potential new editor will need to follow the BIP process as =
it=20
>> currently is defined until such a new BIP is accepted.
>>
>> Luke
>>
>>
>> On April 2, 2024 7:49:22 AM CST, /dev /fd0 <alice...@gmail.com> wrote:
>>
>>> > Does it matter? The number that a proposal gets has no impact on
>>> > literally anything else. They could do it sequentially and it wouldn'=
t
>>> > actually make a difference as long as there are no collisions.
>>>
>>> Process followed to assign the number started this whole debate recentl=
y=20
>>> and creation of BINANA. Previous BIP editor refused to assign numbers t=
o=20
>>> some BIPs. Kanzure had [tweeted][0] asking users on twitter if a BIP sh=
ould=20
>>> be assigned number. So I am curious what process exactly would be follo=
wed=20
>>> by new BIP editors.
>>>
>>> > For example, this was done when Luke was hacked -
>>> > all of his permissions were immediately removed as soon as the news c=
ame
>>> > out, and were only returned several months later once verified
>>> > communication with Luke were established and he was certain that his
>>> > GitHub account was no longer (at risk of being) compromised.
>>>
>>> Thanks for sharing. I wasn't aware of this.
>>>
>>> [0]: https://x.com/kanzure/status/1752663903715168280
>>>
>>> /dev/fd0
>>> floppy disk guy
>>>
>>> On Tuesday, April 2, 2024 at 8:22:16=E2=80=AFAM UTC Ava Chow wrote:
>>>
>>>>
>>>>
>>>> On 04/01/2024 07:55 PM, /dev /fd0 wrote:=20
>>>> > I think before we decide new BIP editors its important to discuss so=
me=20
>>>> > things about the process itself:=20
>>>> >=20
>>>> > 1. Quoting first paragraph from BIPs repo README: "People wishing to=
=20
>>>> > submit BIPs, first should propose their idea or document to the=20
>>>> > bitco...@lists.linuxfoundation.org mailing list (do not assign a=20
>>>> > number - read BIP 2 for the full process). After discussion, please=
=20
>>>> open=20
>>>> > a PR. After copy-editing and acceptance, it will be published here."=
=20
>>>> >=20
>>>> > If Kanzure and Ruben are BIP editors, does it mean they can censor=
=20
>>>> > someone from submitting BIPs? This question makes sense because they=
=20
>>>> > will have control over the whole improvement process for "bitcoin" b=
y=20
>>>> > being moderators for mailing list and BIP editors.=20
>>>>
>>>> If the only requirement is that a BIP shows up on the mailing list=20
>>>> first, then they can already censor them. Having them as BIP editors=
=20
>>>> wouldn't change that. It's not clear to me that this requirement is=20
>>>> strictly enforced anyways.=20
>>>>
>>>> Furthermore, they would not have the permissions to delete PRs or=20
>>>> issues, so once a PR is opened, even if closed, would still be there.=
=20
>>>> The status quo w.r.t that would not be any different. At worst, they=
=20
>>>> could refuse to assign a BIP a number, but that's no different than wh=
at=20
>>>> already happens today. In fact, the situation would likely be better=
=20
>>>> because there would be multiple BIP editors and so what goes into the=
=20
>>>> repo is not at the whim of a single person.=20
>>>>
>>>> > 2. How are numbers going to be assigned to BIPs?=20
>>>>
>>>> Does it matter? The number that a proposal gets has no impact on=20
>>>> literally anything else. They could do it sequentially and it wouldn't=
=20
>>>> actually make a difference as long as there are no collisions.=20
>>>>
>>>> > 3. Will there be copy of BIPs and pull requests maintained elsewhere=
=20
>>>> > like bitcoin core?=20
>>>>
>>>> I'm not sure why this is relevant to this discussion, but presumably=
=20
>>>> there already are, and if there aren't, you can do it yourself. It's=
=20
>>>> just like any other repo on GitHub.=20
>>>>
>>>> > 4. What are the expectations from new BIP editors? In what situation=
=20
>>>> do=20
>>>> > we look for next BIP editors or in other words, what will be the=20
>>>> process=20
>>>> > to remove an editor if lot of people are unhappy with their work?=20
>>>>
>>>> The expectations are as outlined to BIP 2, and that they are actually=
=20
>>>> active. The situation for looking for new BIP editors in the future is=
=20
>>>> presumably similar to the one we are in currently - people who write=
=20
>>>> BIPs are frustrated with things taking a long time to be merged with t=
he=20
>>>> root cause being slow response times from the current editor. The=20
>>>> process would likely be very similar: names are proposed, there is=20
>>>> discussion about those people, and eventually some are added.=20
>>>>
>>>> As for removal, this has not been something we've ever done before, so=
=20
>>>> the process for this is undefined. However, it would presumably be a=
=20
>>>> similar procedure as for adding someone. It begins with someone raisin=
g=20
>>>> a complaint about one of the editors on this mailing list or some othe=
r=20
>>>> place a discussion, and a community discussion commences about whether=
=20
>>>> or not to remove them.=20
>>>>
>>>> There are certainly situations where one of the GitHub org owners may=
=20
>>>> take emergency action and remove a maintainer's privileges. This is on=
ly=20
>>>> done when there is a clear danger than the account may do something=20
>>>> malicious, and the privileges would be returned if there is clarity th=
at=20
>>>> it is safe to do so. For example, this was done when Luke was hacked -=
=20
>>>> all of his permissions were immediately removed as soon as the news ca=
me=20
>>>> out, and were only returned several months later once verified=20
>>>> communication with Luke were established and he was certain that his=
=20
>>>> GitHub account was no longer (at risk of being) compromised.=20
>>>>
>>>> Ava=20
>>>>
>>>> >=20
>>>> > /dev/fd0=20
>>>> > floppy disk guy=20
>>>> >=20
>>>> > On Monday, April 1, 2024 at 9:16:54=E2=80=AFPM UTC David A. Harding =
wrote:=20
>>>> >=20
>>>> > On 2024-03-28 10:04, Matt Corallo wrote:=20
>>>> > > Please provide justification rather than simply saying "I like=20
>>>> > Bob!".=20
>>>> >=20
>>>> > Using only comments from the mailing list, the following appears to =
be=20
>>>> > the candidate list along with the current support. Asterisks denote=
=20
>>>> > candidates who indicated their willingness to accept the role.=20
>>>> >=20
>>>> > - Bryan "Kanzure" Bishop, recommended by Ava Chow[1], Chris=20
>>>> Stewart[3],=20
>>>> > Michael Folkson[6], Peter Todd[9], Matt Corallo[10], Brandon=20
>>>> > Black[11],=20
>>>> > Antoine Riard[12], Murch[13], Antoine Poinsot[15], John Carvalho[16]=
=20
>>>> >=20
>>>> > - Ruben Somsen, recommended by Ava Chow[1], Chris Stewart[3], Michae=
l=20
>>>> > Folkson[6], Antoine Riard[12], Murch[13], Antoine Poinsot[15], John=
=20
>>>> > Carvalho[16]=20
>>>> >=20
>>>> > - Jon Atack*, recommended by Luke Dashjr[2], Chris Stewart[3],=20
>>>> > /dev/fd0[5][7],=20
>>>> > Brandon Black[11], Antoine Riard[12], Ava Chow[14], John Carvalho[16=
]=20
>>>> >=20
>>>> > - Olaoluwa "Roasbeef" Osuntokun, recommended by Chris Stewart[3], Jo=
hn=20
>>>> > C. Vernaleo[4], /dev/fd0[5][7], Keagan McClelland[8], Antoine=20
>>>> > Riard[12], Ava Chow[14]=20
>>>> >=20
>>>> > - Mark "Murch" Erhardt*, recommended by Michael Folkson[6], Keagan=
=20
>>>> > McClelland[8], Matt Corallo[10], Brandon Black[11], Antoine Riard[12=
],=20
>>>> > Ava Chow[14]=20
>>>> >=20
>>>> > - Michael Folkson*=20
>>>> >=20
>>>> > Note: Luke Dashjr proposed[17] Seccour and Greg Tonoski for "non-dev=
=20
>>>> > triaging", Tonoski proposed himself[18] for "BIP editor", and Antoin=
e=20
>>>> > Riard[12] proposed Seccour for "decentralized PM".=20
>>>> >=20
>>>> > I searched the BIPs repo by commenter to see if any of the above=20
>>>> > candidates had been especially active there, which is listed below a=
s:=20
>>>> > total PRs they commented on (number still open/number closed).=20
>>>> >=20
>>>> > - 21 (1/20) commenter:kanzure=20
>>>> > - 3 (2/1) commenter:rubensomsen=20
>>>> > - 15 (0/15) commenter:jonatack=20
>>>> > - 18 (2/16) commenter:roasbeef=20
>>>> > - 10 (6/4) commenter:Murchandamus=20
>>>> > - 57 (6/51) commenter:michaelfolkson=20
>>>> >=20
>>>> > I'll also note that Osuntokun is the only member of the set to have =
a=20
>>>> > merged BIP that they co-authored, although I believe there are=20
>>>> > far-along=20
>>>> > draft BIPs for both Murch (terminology) and Somsen (Silent Payments)=
.=20
>>>> I=20
>>>> > don't think this should be a requirement, but I do think it=20
>>>> > demonstrates=20
>>>> > familiarity with the process.=20
>>>> >=20
>>>> > Speaking only for myself, I think all of the candidates above with=
=20
>>>> > multiple recommendations from other community participants are fully=
=20
>>>> > qualified for the role, so I'll only provide a detailed justificatio=
n=20
>>>> > for the person who would be my first pick: Murch is not only a=20
>>>> > longstanding and broadly liked Bitcoin contributor, but (as Corallo=
=20
>>>> > mentioned) he has worked on standardizing terminology through a draf=
t=20
>>>> > BIP. In addition, he provided an extremely detailed review of all 30=
0=20
>>>> > pages of a draft of Mastering Bitcoin (3rd edition) and has reviewed=
=20
>>>> > drafts of over 200 weekly Optech newsletters, in both cases=20
>>>> > significantly improving the accuracy and comprehensibility of the=20
>>>> > documentation. To me, that seems very similar to the work we'd ask h=
im=20
>>>> > to perform as a BIPs editor and it's something that he's already=20
>>>> doing,=20
>>>> > so I think there's an excellent fit of person to role.=20
>>>> >=20
>>>> > -Dave=20
>>>> >=20
>>>> > [1]=20
>>>> > https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8...@achow101.com/=
=20
>>>> > <https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8...@achow101.com=
/=20
>>>> <https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8-ba1a-c9d97927551e=
@achow101.com/>>=20
>>>>
>>>> > [2]=20
>>>> > https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106...@dashjr.org/=
=20
>>>> > <https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106...@dashjr.org/=
=20
>>>> <https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106-b843-c1ff8f8a62a3=
@dashjr.org/>>=20
>>>>
>>>> > [3]=20
>>>> >=20
>>>> https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a...@googlegroups.co=
m/=20
>>>> <
>>>> https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a...@googlegroups.co=
m/=20
>>>> <https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a-8fd6-cddc46f129a2=
n@googlegroups.com/>>=20
>>>>
>>>> > [4]=20
>>>> >=20
>>>> https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.co=
m/=20
>>>> <
>>>> https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.co=
m/=20
>>>> <https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333-fd28-bdd55899b713=
@netpurgatory.com/>>=20
>>>>
>>>> > [5]=20
>>>> >=20
>>>> https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.co=
m/=20
>>>> <
>>>> https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.co=
m/=20
>>>> <https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36-be81-7c3719157fab=
n@googlegroups.com/>>=20
>>>>
>>>> > [6]=20
>>>> >=20
>>>> https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.co=
m/=20
>>>> <
>>>> https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.co=
m/=20
>>>> <https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2-a787-639a3564d006=
n@googlegroups.com/>>=20
>>>>
>>>> > [7]=20
>>>> >=20
>>>> https://gnusha.org/pi/bitcoindev/846b668f-8386-4869...@googlegroups.co=
m/=20
>>>> <
>>>> https://gnusha.org/pi/bitcoindev/846b668f-8386-4869...@googlegroups.co=
m/=20
>>>> <https://gnusha.org/pi/bitcoindev/846b668f-8386-4869-a3b1-55d346efbea1=
n@googlegroups.com/>>=20
>>>>
>>>> > [8]=20
>>>> >=20
>>>> https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEa=
zRA5...@mail.gmail.com/=20
>>>> <
>>>> https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEa=
zRA5...@mail.gmail.com/=20
>>>> <https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLE=
azRA5nVw9siYCPj4A@mail.gmail.com/>>=20
>>>>
>>>> > [9] https://gnusha.org/pi/bitcoindev/ZgePPvbf...@petertodd.org/=20
>>>> > <https://gnusha.org/pi/bitcoindev/ZgePPvbf...@petertodd.org/=20
>>>> <https://gnusha.org/pi/bitcoindev/ZgePPvbfrr4wZG7k@petertodd.org/>>=20
>>>> > [10]=20
>>>> >=20
>>>> https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5...@mattcorallo.com=
/=20
>>>> <https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5...@mattcorallo.co=
m/=20
>>>> <https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5-86e2-7ba0336a9bf2=
@mattcorallo.com/>>=20
>>>>
>>>> > [11] https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg69V@console/=20
>>>> > <https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg69V@console/>=20
>>>> > [12]=20
>>>> >=20
>>>> https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+E...@mail.gma=
il.com/=20
>>>> <
>>>> https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+E...@mail.gma=
il.com/=20
>>>> <https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+EKMCP5oEbHSK=
SXpq0VKVBhJLhrw@mail.gmail.com/>>=20
>>>>
>>>> > [13]=20
>>>> > https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a...@murch.one/=20
>>>> > <https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a...@murch.one/=
=20
>>>> <https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a-920b-32bd88d5e778=
@murch.one/>>=20
>>>>
>>>> > [14]=20
>>>> > https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f...@achow101.com/=
=20
>>>> > <https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f...@achow101.com=
/=20
>>>> <https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f-866d-c555b80b0644=
@achow101.com/>>=20
>>>>
>>>> > [15]=20
>>>> >=20
>>>> https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsu=
izh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@p=
rotonmail.com/=20
>>>> <
>>>> https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsu=
izh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@p=
rotonmail.com/>=20
>>>>
>>>> > [16]=20
>>>> >=20
>>>> https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552...@googlegroups.co=
m/=20
>>>> <
>>>> https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552...@googlegroups.co=
m/=20
>>>> <https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552-88ca-11b9ed340661=
n@googlegroups.com/>>=20
>>>>
>>>> > [17]=20
>>>> >=20
>>>> https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd=
9Qrst+...@mail.gmail.com/=20
>>>> <
>>>> https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd=
9Qrst+...@mail.gmail.com/=20
>>>> <https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMv=
d9Qrst+nmyypaedYZgg@mail.gmail.com/>>=20
>>>>
>>>> >=20
>>>> > --=20
>>>> > You received this message because you are subscribed to the Google=
=20
>>>> > Groups "Bitcoin Development Mailing List" group.=20
>>>> > To unsubscribe from this group and stop receiving emails from it, se=
nd=20
>>>> > an email to bitcoindev+...@googlegroups.com=20
>>>> > <mailto:bitcoindev+...@googlegroups.com>.=20
>>>> > To view this discussion on the web visit=20
>>>> >=20
>>>> https://groups.google.com/d/msgid/bitcoindev/cbb0b74f-c60b-4c8a-9e97-9=
b1c0e0eb047n%40googlegroups.com=20
>>>> <
>>>> https://groups.google.com/d/msgid/bitcoindev/cbb0b74f-c60b-4c8a-9e97-9=
b1c0e0eb047n%40googlegroups.com?utm_medium=3Demail&utm_source=3Dfooter>.=20
>>>>
>>>>
>>>>
>
>--=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 =
email to bitcoindev+unsubscribe@googlegroups.com.
>To view this discussion on the web visit https://groups.google.com/d/msgid=
/bitcoindev/a18850ec-4659-4683-8e50-9758a7f431can%40googlegroups.com.
--=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/847D8B06-9F61-4515-B6B2-6093E7F7A80D%40dashjr.org.
------MPPR57GVYMXD8IFGOQT5GBOIK9CB1V
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<html><head></head><body><div dir=3D"auto">On the timeline, there has alrea=
dy been a very reasonable objection raised by Antoine. I'm also unlikely to=
be available around that time (and through the weekend) to actually do it.=
So it'll need to be next week at the earliest, but I don't see a problem w=
ith closer to May if that's important to some.<br><br>Luke<br></div><br><br=
><div class=3D"gmail_quote"><div dir=3D"auto">On April 2, 2024 9:13:46 AM C=
ST, Gloria Zhao <gloria@brink.dev> wrote:</div><blockquote class=3D"g=
mail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(=
204, 204, 204); padding-left: 1ex;">
> If we are all just in a holding pattern, perhaps we could timebox this=
=20
<br>> decision process: how about we invite arguments for and against an=
y=20
<br>> candidates in this thread until next Friday EOD (April 5th). If an=
y=20
<br>> candidates find broad support, those candidates could be added as =
new=20
<br>> editors to the repository on the following Monday (April 8th).<br>=
<div><br></div><div>Thanks, ACK this timeline for moving forward.</div><div=
><br></div><div>Assuming they are willing, I am in favor of adding Murch, R=
uben, and Kanzure as BIP editors. They have all demonstrated through years =
of experience contributing to / moderating {the mailing list, stack exchang=
e, Optech} that they have the technical expertise, skills in technical docu=
mentation, and track record of good judgement appropriate for this role.<br=
></div><div><br></div><div>Best,</div><div>Gloria<br></div><div><br></div><=
div class=3D"gmail_quote"><div dir=3D"auto" class=3D"gmail_attr">On Tuesday=
, April 2, 2024 at 3:30:58=E2=80=AFPM UTC+1 Luke Dashjr wrote:<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin: 0 0 0 0.8ex; border-left: 1=
px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div dir=3D"auto">No,=
there was no such refusal. The ONLY issue at hand with regard to more BIP =
editors is that I don't have time to keep up with it by myself. If your goa=
l is anything else, please sit this discussion out (aside from perhaps reas=
onable objections to new editors). BIP number assignments are trivial and n=
ot a concern.<br><br>It seems there's an attempt to take advantage of the n=
eed for more BIP editors to change or bypass the BIP process without proper=
procedures followed. While there may be arguments for improving the BIP pr=
ocess, that is unrelated and would need to go through a BIP, not simply fia=
t of a new editor. Any potential new editor will need to follow the BIP pro=
cess as it currently is defined until such a new BIP is accepted.<br><br>Lu=
ke</div></div><div><br><br><div class=3D"gmail_quote"><div dir=3D"auto">On =
April 2, 2024 7:49:22 AM CST, /dev /fd0 <<a href data-email-masked rel=
=3D"nofollow">alice...@gmail.com</a>> wrote:</div><blockquote class=3D"g=
mail_quote" style=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">
>
Does it matter? The number that a proposal gets has no impact on<br>> li=
terally anything else. They could do it sequentially and it wouldn't<br>>=
; actually make a difference as long as there are no collisions.<div><br></=
div><div>Process followed to assign the number started this whole debate re=
cently and creation of BINANA. Previous BIP editor refused to assign number=
s to some BIPs. Kanzure had [tweeted][0] asking users on twitter if a BIP s=
hould be assigned number. So I am curious what process exactly would be fol=
lowed by new BIP editors.</div><div><br></div><div>> For example, this w=
as done when Luke was hacked -</div>> all of his permissions were immedi=
ately removed as soon as the news came<br>> out, and were only returned =
several months later once verified<br>> communication with Luke were est=
ablished and he was certain that his<br>> GitHub account was no longer (=
at risk of being) compromised.<div><br></div><div>Thanks for sharing. I was=
n't aware of this.<br><div><br></div><div>[0]: <a href=3D"https://x.co=
m/kanzure/status/1752663903715168280" target=3D"_blank" rel=3D"nofollow" da=
ta-saferedirecturl=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://x.=
com/kanzure/status/1752663903715168280&source=3Dgmail&ust=3D1712155=
859865000&usg=3DAOvVaw00y5c6ekPt8Os6yTQ0tWgn">https://x.com/kanzure/sta=
tus/1752663903715168280</a></div><div><br></div><div>/dev/fd0</div><div>flo=
ppy disk guy<br><br></div></div><div class=3D"gmail_quote"><div dir=3D"auto=
" class=3D"gmail_attr">On Tuesday, April 2, 2024 at 8:22:16=E2=80=AFAM UTC =
Ava Chow wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>On 04/01/2024 07:55 PM, /dev /fd0 wrote:
<br>> I think before we decide new BIP editors its important to discuss =
some=20
<br>> things about the process itself:
<br>>=20
<br>> 1. Quoting first paragraph from BIPs repo README: "People wishing =
to=20
<br>> submit BIPs, first should propose their idea or document to the=20
<br>> <a rel=3D"nofollow">bitco...@lists.linuxfoundation.org</a> mailing=
list (do not assign a=20
<br>> number - read BIP 2 for the full process). After discussion, pleas=
e open=20
<br>> a PR. After copy-editing and acceptance, it will be published here=
."
<br>>=20
<br>> If Kanzure and Ruben are BIP editors, does it mean they can censor=
=20
<br>> someone from submitting BIPs? This question makes sense because th=
ey=20
<br>> will have control over the whole improvement process for "bitcoin"=
by=20
<br>> being moderators for mailing list and BIP editors.
<br>
<br>If the only requirement is that a BIP shows up on the mailing list=20
<br>first, then they can already censor them. Having them as BIP editors=20
<br>wouldn't change that. It's not clear to me that this requirement is=20
<br>strictly enforced anyways.
<br>
<br>Furthermore, they would not have the permissions to delete PRs or=20
<br>issues, so once a PR is opened, even if closed, would still be there.=
=20
<br>The status quo w.r.t that would not be any different. At worst, they=20
<br>could refuse to assign a BIP a number, but that's no different than wha=
t=20
<br>already happens today. In fact, the situation would likely be better=20
<br>because there would be multiple BIP editors and so what goes into the=
=20
<br>repo is not at the whim of a single person.
<br>
<br>> 2. How are numbers going to be assigned to BIPs?
<br>
<br>Does it matter? The number that a proposal gets has no impact on=20
<br>literally anything else. They could do it sequentially and it wouldn't=
=20
<br>actually make a difference as long as there are no collisions.
<br>
<br>> 3. Will there be copy of BIPs and pull requests maintained elsewhe=
re=20
<br>> like bitcoin core?
<br>
<br>I'm not sure why this is relevant to this discussion, but presumably=20
<br>there already are, and if there aren't, you can do it yourself. It's=20
<br>just like any other repo on GitHub.
<br>
<br>> 4. What are the expectations from new BIP editors? In what situati=
on do=20
<br>> we look for next BIP editors or in other words, what will be the p=
rocess=20
<br>> to remove an editor if lot of people are unhappy with their work?
<br>
<br>The expectations are as outlined to BIP 2, and that they are actually=
=20
<br>active. The situation for looking for new BIP editors in the future is=
=20
<br>presumably similar to the one we are in currently - people who write=20
<br>BIPs are frustrated with things taking a long time to be merged with th=
e=20
<br>root cause being slow response times from the current editor. The=20
<br>process would likely be very similar: names are proposed, there is=20
<br>discussion about those people, and eventually some are added.
<br>
<br>As for removal, this has not been something we've ever done before, so=
=20
<br>the process for this is undefined. However, it would presumably be a=20
<br>similar procedure as for adding someone. It begins with someone raising=
=20
<br>a complaint about one of the editors on this mailing list or some other=
=20
<br>place a discussion, and a community discussion commences about whether=
=20
<br>or not to remove them.
<br>
<br>There are certainly situations where one of the GitHub org owners may=
=20
<br>take emergency action and remove a maintainer's privileges. This is onl=
y=20
<br>done when there is a clear danger than the account may do something=20
<br>malicious, and the privileges would be returned if there is clarity tha=
t=20
<br>it is safe to do so. For example, this was done when Luke was hacked -=
=20
<br>all of his permissions were immediately removed as soon as the news cam=
e=20
<br>out, and were only returned several months later once verified=20
<br>communication with Luke were established and he was certain that his=20
<br>GitHub account was no longer (at risk of being) compromised.
<br>
<br>Ava
<br>
<br>>=20
<br>> /dev/fd0
<br>> floppy disk guy
<br>>=20
<br>> On Monday, April 1, 2024 at 9:16:54=E2=80=AFPM UTC David A. Hardin=
g wrote:
<br>>=20
<br>> On 2024-03-28 10:04, Matt Corallo wrote:
<br>> > Please provide justification rather than simply saying "=
I like
<br>> Bob!".
<br>>=20
<br>> Using only comments from the mailing list, the following appea=
rs to be
<br>> the candidate list along with the current support. Asterisks d=
enote
<br>> candidates who indicated their willingness to accept the role.
<br>>=20
<br>> - Bryan "Kanzure" Bishop, recommended by Ava Chow[1], Chris St=
ewart[3],
<br>> Michael Folkson[6], Peter Todd[9], Matt Corallo[10], Brandon
<br>> Black[11],
<br>> Antoine Riard[12], Murch[13], Antoine Poinsot[15], John Carval=
ho[16]
<br>>=20
<br>> - Ruben Somsen, recommended by Ava Chow[1], Chris Stewart[3], =
Michael
<br>> Folkson[6], Antoine Riard[12], Murch[13], Antoine Poinsot[15],=
John
<br>> Carvalho[16]
<br>>=20
<br>> - Jon Atack*, recommended by Luke Dashjr[2], Chris Stewart[3],
<br>> /dev/fd0[5][7],
<br>> Brandon Black[11], Antoine Riard[12], Ava Chow[14], John Carva=
lho[16]
<br>>=20
<br>> - Olaoluwa "Roasbeef" Osuntokun, recommended by Chris Stewart[=
3], John
<br>> C. Vernaleo[4], /dev/fd0[5][7], Keagan McClelland[8], Antoine
<br>> Riard[12], Ava Chow[14]
<br>>=20
<br>> - Mark "Murch" Erhardt*, recommended by Michael Folkson[6], Ke=
agan
<br>> McClelland[8], Matt Corallo[10], Brandon Black[11], Antoine Ri=
ard[12],
<br>> Ava Chow[14]
<br>>=20
<br>> - Michael Folkson*
<br>>=20
<br>> Note: Luke Dashjr proposed[17] Seccour and Greg Tonoski for "n=
on-dev
<br>> triaging", Tonoski proposed himself[18] for "BIP editor", and =
Antoine
<br>> Riard[12] proposed Seccour for "decentralized PM".
<br>>=20
<br>> I searched the BIPs repo by commenter to see if any of the abo=
ve
<br>> candidates had been especially active there, which is listed b=
elow as:
<br>> total PRs they commented on (number still open/number closed).
<br>>=20
<br>> - 21 (1/20) commenter:kanzure
<br>> - 3 (2/1) commenter:rubensomsen
<br>> - 15 (0/15) commenter:jonatack
<br>> - 18 (2/16) commenter:roasbeef
<br>> - 10 (6/4) commenter:Murchandamus
<br>> - 57 (6/51) commenter:michaelfolkson
<br>>=20
<br>> I'll also note that Osuntokun is the only member of the set to=
have a
<br>> merged BIP that they co-authored, although I believe there are
<br>> far-along
<br>> draft BIPs for both Murch (terminology) and Somsen (Silent Pay=
ments). I
<br>> don't think this should be a requirement, but I do think it
<br>> demonstrates
<br>> familiarity with the process.
<br>>=20
<br>> Speaking only for myself, I think all of the candidates above =
with
<br>> multiple recommendations from other community participants are=
fully
<br>> qualified for the role, so I'll only provide a detailed justif=
ication
<br>> for the person who would be my first pick: Murch is not only a
<br>> longstanding and broadly liked Bitcoin contributor, but (as Co=
rallo
<br>> mentioned) he has worked on standardizing terminology through =
a draft
<br>> BIP. In addition, he provided an extremely detailed review of =
all 300
<br>> pages of a draft of Mastering Bitcoin (3rd edition) and has re=
viewed
<br>> drafts of over 200 weekly Optech newsletters, in both cases
<br>> significantly improving the accuracy and comprehensibility of =
the
<br>> documentation. To me, that seems very similar to the work we'd=
ask him
<br>> to perform as a BIPs editor and it's something that he's alrea=
dy doing,
<br>> so I think there's an excellent fit of person to role.
<br>>=20
<br>> -Dave
<br>>=20
<br>> [1]
<br>> <a href=3D"https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8=
...@achow101.com/" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/2092f7ff-4860-47f8...@achow101.com/&source=3Dgmail&ust=3D17121=
55859866000&usg=3DAOvVaw1OU3uS906r6ueGSX7vlDnA">https://gnusha.org/pi/b=
itcoindev/2092f7ff-4860-47f8...@achow101.com/</a>
<br>> <<a href=3D"https://gnusha.org/pi/bitcoindev/2092f7ff-4860-=
47f8-ba1a-c9d97927551e@achow101.com/" rel=3D"nofollow" target=3D"_blank" da=
ta-saferedirecturl=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gn=
usha.org/pi/bitcoindev/2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com/&a=
mp;source=3Dgmail&ust=3D1712155859866000&usg=3DAOvVaw12fzWCAWoAru5u=
dSxp2ozf">https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8...@achow101.c=
om/</a>>
<br>> [2]
<br>> <a href=3D"https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106=
...@dashjr.org/" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=3D=
"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bitcoinde=
v/9288df7b-f2e9-4106...@dashjr.org/&source=3Dgmail&ust=3D1712155859=
866000&usg=3DAOvVaw3V4tobrdlWDX9cdz6X4-Pm">https://gnusha.org/pi/bitcoi=
ndev/9288df7b-f2e9-4106...@dashjr.org/</a>
<br>> <<a href=3D"https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-=
4106-b843-c1ff8f8a62a3@dashjr.org/" rel=3D"nofollow" target=3D"_blank" data=
-saferedirecturl=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnus=
ha.org/pi/bitcoindev/9288df7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org/&s=
ource=3Dgmail&ust=3D1712155859866000&usg=3DAOvVaw1BZwDwHSqXKYB_-0TD=
oSis">https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106...@dashjr.org/</a=
>>
<br>> [3]
<br>> <a href=3D"https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a=
...@googlegroups.com/" rel=3D"nofollow" target=3D"_blank" data-saferedirect=
url=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bit=
coindev/d1e7183c-30e6-4f1a...@googlegroups.com/&source=3Dgmail&ust=
=3D1712155859866000&usg=3DAOvVaw1YsW073xDYWFgnfws5QU2L">https://gnusha.=
org/pi/bitcoindev/d1e7183c-30e6-4f1a...@googlegroups.com/</a> <<a href=
=3D"https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n@=
googlegroups.com/" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n@googlegroups.com/&source=3Dg=
mail&ust=3D1712155859866000&usg=3DAOvVaw0rkB9_KayaDBH_SfdzChDy">htt=
ps://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a...@googlegroups.com/</a>&g=
t;
<br>> [4]
<br>> <a href=3D"https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333=
...@netpurgatory.com/" rel=3D"nofollow" target=3D"_blank" data-saferedirect=
url=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bit=
coindev/84309c3f-e848-d333...@netpurgatory.com/&source=3Dgmail&ust=
=3D1712155859866000&usg=3DAOvVaw0RT-FF4-WE-ISc243rwwVg">https://gnusha.=
org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.com/</a> <<a href=
=3D"https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333-fd28-bdd55899b713@n=
etpurgatory.com/" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/84309c3f-e848-d333-fd28-bdd55899b713@netpurgatory.com/&source=3Dgm=
ail&ust=3D1712155859866000&usg=3DAOvVaw32VNEwY_I1xizjrSJDL-fo">http=
s://gnusha.org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.com/</a>>=
;
<br>> [5]
<br>> <a href=3D"https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36=
...@googlegroups.com/" rel=3D"nofollow" target=3D"_blank" data-saferedirect=
url=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bit=
coindev/4c1462b7-ea1c-4a36...@googlegroups.com/&source=3Dgmail&ust=
=3D1712155859866000&usg=3DAOvVaw2u-eAEjTGZZZPkeb57gf4Z">https://gnusha.=
org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.com/</a> <<a href=
=3D"https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36-be81-7c3719157fabn@=
googlegroups.com/" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/4c1462b7-ea1c-4a36-be81-7c3719157fabn@googlegroups.com/&source=3Dg=
mail&ust=3D1712155859866000&usg=3DAOvVaw2jFEhl5ga1Fkjwi9awVRNK">htt=
ps://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.com/</a>&g=
t;
<br>> [6]
<br>> <a href=3D"https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2=
...@googlegroups.com/" rel=3D"nofollow" target=3D"_blank" data-saferedirect=
url=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bit=
coindev/a116fba3-5948-48d2...@googlegroups.com/&source=3Dgmail&ust=
=3D1712155859866000&usg=3DAOvVaw1CgIqGvWYVDpweP__m14iu">https://gnusha.=
org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.com/</a> <<a href=
=3D"https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2-a787-639a3564d006n@=
googlegroups.com/" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/a116fba3-5948-48d2-a787-639a3564d006n@googlegroups.com/&source=3Dg=
mail&ust=3D1712155859866000&usg=3DAOvVaw3QrRfkndxh5-IV-CUMMh9K">htt=
ps://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.com/</a>&g=
t;
<br>> [7]
<br>> <a href=3D"https://gnusha.org/pi/bitcoindev/846b668f-8386-4869=
...@googlegroups.com/" rel=3D"nofollow" target=3D"_blank" data-saferedirect=
url=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bit=
coindev/846b668f-8386-4869...@googlegroups.com/&source=3Dgmail&ust=
=3D1712155859866000&usg=3DAOvVaw04yVBzdpLF736fM4Iu955h">https://gnusha.=
org/pi/bitcoindev/846b668f-8386-4869...@googlegroups.com/</a> <<a href=
=3D"https://gnusha.org/pi/bitcoindev/846b668f-8386-4869-a3b1-55d346efbea1n@=
googlegroups.com/" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/846b668f-8386-4869-a3b1-55d346efbea1n@googlegroups.com/&source=3Dg=
mail&ust=3D1712155859866000&usg=3DAOvVaw1trsyLNcu93vVTypfe0A0n">htt=
ps://gnusha.org/pi/bitcoindev/846b668f-8386-4869...@googlegroups.com/</a>&g=
t;
<br>> [8]
<br>> <a href=3D"https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS=
110ut8tX=3DwruqgLEazRA5...@mail.gmail.com/" rel=3D"nofollow" target=3D"_bla=
nk" data-saferedirecturl=3D"https://www.google.com/url?hl=3Den&q=3Dhttp=
s://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX%3DwruqgLEazRA5...@m=
ail.gmail.com/&source=3Dgmail&ust=3D1712155859866000&usg=3DAOvV=
aw2OtMQZb20PPB3JKfvoKj_V">https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7Y=
RS110ut8tX=3DwruqgLEazRA5...@mail.gmail.com/</a> <<a href=3D"https://gnu=
sha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEazRA5nVw9siYCPj4A=
@mail.gmail.com/" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/CALeFGL1-LKPWd7YRS110ut8tX%3DwruqgLEazRA5nVw9siYCPj4A@mail.gmail.com/&=
amp;source=3Dgmail&ust=3D1712155859866000&usg=3DAOvVaw0Kzic9SPRJvaO=
8DylZ7wmc">https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3Dwr=
uqgLEazRA5...@mail.gmail.com/</a>>
<br>> [9] <a href=3D"https://gnusha.org/pi/bitcoindev/ZgePPvbf...@pe=
tertodd.org/" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=3D"ht=
tps://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bitcoindev/Z=
gePPvbf...@petertodd.org/&source=3Dgmail&ust=3D1712155859866000&=
;usg=3DAOvVaw2AP5VO_aJ14Dim4QngEe8F">https://gnusha.org/pi/bitcoindev/ZgePP=
vbf...@petertodd.org/</a>
<br>> <<a href=3D"https://gnusha.org/pi/bitcoindev/ZgePPvbfrr4wZG=
7k@petertodd.org/" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/ZgePPvbfrr4wZG7k@petertodd.org/&source=3Dgmail&ust=3D171215585=
9866000&usg=3DAOvVaw0MkpcCr4ys9fJKFx_7AJip">https://gnusha.org/pi/bitco=
indev/ZgePPvbf...@petertodd.org/</a>>
<br>> [10]
<br>> <a href=3D"https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5=
...@mattcorallo.com/" rel=3D"nofollow" target=3D"_blank" data-saferedirectu=
rl=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bitc=
oindev/f9435999-42df-46b5...@mattcorallo.com/&source=3Dgmail&ust=3D=
1712155859866000&usg=3DAOvVaw1ACxyI8JAvnrygsXWPSmbE">https://gnusha.org=
/pi/bitcoindev/f9435999-42df-46b5...@mattcorallo.com/</a> <<a href=3D"ht=
tps://gnusha.org/pi/bitcoindev/f9435999-42df-46b5-86e2-7ba0336a9bf2@mattcor=
allo.com/" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=3D"https=
://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bitcoindev/f943=
5999-42df-46b5-86e2-7ba0336a9bf2@mattcorallo.com/&source=3Dgmail&us=
t=3D1712155859866000&usg=3DAOvVaw2hr_3ajadqsyjMFU3-PnyB">https://gnusha=
.org/pi/bitcoindev/f9435999-42df-46b5...@mattcorallo.com/</a>>
<br>> [11] <a href=3D"https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg=
69V@console/" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=3D"ht=
tps://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bitcoindev/Z=
gWRu32FXzqqg69V@console/&source=3Dgmail&ust=3D1712155859866000&=
usg=3DAOvVaw2Hn0P5YAjTG73Nn88TIWCv">https://gnusha.org/pi/bitcoindev/ZgWRu3=
2FXzqqg69V@console/</a>
<br>> <<a href=3D"https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg6=
9V@console/" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=3D"htt=
ps://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bitcoindev/Zg=
WRu32FXzqqg69V@console/&source=3Dgmail&ust=3D1712155859866000&u=
sg=3DAOvVaw2Hn0P5YAjTG73Nn88TIWCv">https://gnusha.org/pi/bitcoindev/ZgWRu32=
FXzqqg69V@console/</a>>
<br>> [12]
<br>> <a href=3D"https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO=
+FiF6+E...@mail.gmail.com/" rel=3D"nofollow" target=3D"_blank" data-safered=
irecturl=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/p=
i/bitcoindev/CALZpt%2BE8DohYEJ9aO%2BFiF6%2BE...@mail.gmail.com/&source=
=3Dgmail&ust=3D1712155859866000&usg=3DAOvVaw0l-u5qlF6fuwkd7iEb9109"=
>https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+E...@mail.gmail.c=
om/</a> <<a href=3D"https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+=
FiF6+EKMCP5oEbHSKSXpq0VKVBhJLhrw@mail.gmail.com/" rel=3D"nofollow" target=
=3D"_blank" data-saferedirecturl=3D"https://www.google.com/url?hl=3Den&=
q=3Dhttps://gnusha.org/pi/bitcoindev/CALZpt%2BE8DohYEJ9aO%2BFiF6%2BEKMCP5oE=
bHSKSXpq0VKVBhJLhrw@mail.gmail.com/&source=3Dgmail&ust=3D1712155859=
866000&usg=3DAOvVaw0W1nFmnPJ7F4Df20UvME-v">https://gnusha.org/pi/bitcoi=
ndev/CALZpt+E8DohYEJ9aO+FiF6+E...@mail.gmail.com/</a>>
<br>> [13]
<br>> <a href=3D"https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a=
...@murch.one/" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=3D"=
https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bitcoindev=
/53a0015c-b76a-441a...@murch.one/&source=3Dgmail&ust=3D171215585986=
6000&usg=3DAOvVaw13gj8GZhKl2i4pojnBFOHB">https://gnusha.org/pi/bitcoind=
ev/53a0015c-b76a-441a...@murch.one/</a>
<br>> <<a href=3D"https://gnusha.org/pi/bitcoindev/53a0015c-b76a-=
441a-920b-32bd88d5e778@murch.one/" rel=3D"nofollow" target=3D"_blank" data-=
saferedirecturl=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnush=
a.org/pi/bitcoindev/53a0015c-b76a-441a-920b-32bd88d5e778@murch.one/&sou=
rce=3Dgmail&ust=3D1712155859866000&usg=3DAOvVaw0hy7DJLVPIwtO_CoRBec=
jA">https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a...@murch.one/</a>&g=
t;
<br>> [14]
<br>> <a href=3D"https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f=
...@achow101.com/" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/ae482890-bce3-468f...@achow101.com/&source=3Dgmail&ust=3D17121=
55859866000&usg=3DAOvVaw2Bf_fHGKTArjsMwJ87oGNc">https://gnusha.org/pi/b=
itcoindev/ae482890-bce3-468f...@achow101.com/</a>
<br>> <<a href=3D"https://gnusha.org/pi/bitcoindev/ae482890-bce3-=
468f-866d-c555b80b0644@achow101.com/" rel=3D"nofollow" target=3D"_blank" da=
ta-saferedirecturl=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gn=
usha.org/pi/bitcoindev/ae482890-bce3-468f-866d-c555b80b0644@achow101.com/&a=
mp;source=3Dgmail&ust=3D1712155859866000&usg=3DAOvVaw0xevdp7yO6R6Qk=
ljG-tNMv">https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f...@achow101.c=
om/</a>>
<br>> [15]
<br>> <a href=3D"https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmI=
BVBd0WpT5Wof_oSBXsuizh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH=
4gwU1c2jS4xojo=3D@protonmail.com/" rel=3D"nofollow" target=3D"_blank" data-=
saferedirecturl=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnush=
a.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh7692AUDw2TojfvC=
qvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo%3D@protonmail.com/&=
;source=3Dgmail&ust=3D1712155859866000&usg=3DAOvVaw2EFeOkWgH3s2mVc-=
TUtHim">https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSB=
Xsuizh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=
=3D@protonmail.com/</a> <<a href=3D"https://gnusha.org/pi/bitcoindev/ppB=
S1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWa=
wf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@protonmail.com/" rel=3D"nofollow" target=
=3D"_blank" data-saferedirecturl=3D"https://www.google.com/url?hl=3Den&=
q=3Dhttps://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsui=
zh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo%3D@pr=
otonmail.com/&source=3Dgmail&ust=3D1712155859866000&usg=3DAOvVa=
w2EFeOkWgH3s2mVc-TUtHim">https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85km=
IBVBd0WpT5Wof_oSBXsuizh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXO=
H4gwU1c2jS4xojo=3D@protonmail.com/</a>>
<br>> [16]
<br>> <a href=3D"https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552=
...@googlegroups.com/" rel=3D"nofollow" target=3D"_blank" data-saferedirect=
url=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bit=
coindev/ad284018-e99c-4552...@googlegroups.com/&source=3Dgmail&ust=
=3D1712155859866000&usg=3DAOvVaw22pOXvOYB4Axx_2tcyMfEA">https://gnusha.=
org/pi/bitcoindev/ad284018-e99c-4552...@googlegroups.com/</a> <<a href=
=3D"https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552-88ca-11b9ed340661n@=
googlegroups.com/" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/ad284018-e99c-4552-88ca-11b9ed340661n@googlegroups.com/&source=3Dg=
mail&ust=3D1712155859866000&usg=3DAOvVaw0wHQ1-5UjBefxeLVMrTQB7">htt=
ps://gnusha.org/pi/bitcoindev/ad284018-e99c-4552...@googlegroups.com/</a>&g=
t;
<br>> [17]
<br>> <a href=3D"https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo=
76PdqwJU=3D=3DYJMvd9Qrst+...@mail.gmail.com/" rel=3D"nofollow" target=3D"_b=
lank" data-saferedirecturl=3D"https://www.google.com/url?hl=3Den&q=3Dht=
tps://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU%3D%3DYJMvd9Qrst%2=
B...@mail.gmail.com/&source=3Dgmail&ust=3D1712155859866000&usg=
=3DAOvVaw1NYS3BTdaP8kR-9FLlacR3">https://gnusha.org/pi/bitcoindev/CAMHHROw9=
mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qrst+...@mail.gmail.com/</a> <<a href=3D"ht=
tps://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qrst+n=
myypaedYZgg@mail.gmail.com/" rel=3D"nofollow" target=3D"_blank" data-safere=
directurl=3D"https://www.google.com/url?hl=3Den&q=3Dhttps://gnusha.org/=
pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU%3D%3DYJMvd9Qrst%2BnmyypaedYZgg@mai=
l.gmail.com/&source=3Dgmail&ust=3D1712155859866000&usg=3DAOvVaw=
0exsWlL131EGdt7paJfv3t">https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo=
76PdqwJU=3D=3DYJMvd9Qrst+...@mail.gmail.com/</a>>
<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 rel=3D"nofollow">bitcoindev+...@googlegroups.com</a=
>=20
<br>> <mailto:<a 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/cbb0b74f-c=
60b-4c8a-9e97-9b1c0e0eb047n%40googlegroups.com" rel=3D"nofollow" target=3D"=
_blank" data-saferedirecturl=3D"https://www.google.com/url?hl=3Den&q=3D=
https://groups.google.com/d/msgid/bitcoindev/cbb0b74f-c60b-4c8a-9e97-9b1c0e=
0eb047n%2540googlegroups.com&source=3Dgmail&ust=3D1712155859866000&=
amp;usg=3DAOvVaw23FA4F34CysfVe7p1eC0Qq">https://groups.google.com/d/msgid/b=
itcoindev/cbb0b74f-c60b-4c8a-9e97-9b1c0e0eb047n%40googlegroups.com</a> <=
<a href=3D"https://groups.google.com/d/msgid/bitcoindev/cbb0b74f-c60b-4c8a-=
9e97-9b1c0e0eb047n%40googlegroups.com?utm_medium=3Demail&utm_source=3Df=
ooter" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=3D"https://w=
ww.google.com/url?hl=3Den&q=3Dhttps://groups.google.com/d/msgid/bitcoin=
dev/cbb0b74f-c60b-4c8a-9e97-9b1c0e0eb047n%2540googlegroups.com?utm_medium%3=
Demail%26utm_source%3Dfooter&source=3Dgmail&ust=3D1712155859866000&=
amp;usg=3DAOvVaw3NAJi7D-_-qqvuQj2uuZwi">https://groups.google.com/d/msgid/b=
itcoindev/cbb0b74f-c60b-4c8a-9e97-9b1c0e0eb047n%40googlegroups.com?utm_medi=
um=3Demail&utm_source=3Dfooter</a>>.
<br>
<br></blockquote></div>
<p></p></blockquote></div></div></blockquote></div>
<p></p></blockquote></div></body></html>
<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/847D8B06-9F61-4515-B6B2-6093E7F7A80D%40dashjr.org?utm=
_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/bitc=
oindev/847D8B06-9F61-4515-B6B2-6093E7F7A80D%40dashjr.org</a>.<br />
------MPPR57GVYMXD8IFGOQT5GBOIK9CB1V--