path: root/0b/79096bb19d1b292b91cfcd537f23b7160fa6d7

Delivery-date: Tue, 02 Apr 2024 06:58:49 -0700
Received: from mail-yw1-f192.google.com ([209.85.128.192])
	by mail.fairlystable.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
	(Exim 4.94.2)
	(envelope-from <bitcoindev+bncBCU2P6FJ3EBBBEE6WCYAMGQEZ6V7M7A@googlegroups.com>)
	id 1rref2-0000HW-4r
	for bitcoindev@gnusha.org; Tue, 02 Apr 2024 06:58:49 -0700
Received: by mail-yw1-f192.google.com with SMTP id 00721157ae682-61510f72bb3sf19757607b3.0
        for <bitcoindev@gnusha.org>; Tue, 02 Apr 2024 06:58:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=20230601; t=1712066322; x=1712671122; darn=gnusha.org;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-sender:mime-version
         :subject:references:in-reply-to:message-id:to:from:date:sender:from
         :to:cc:subject:date:message-id:reply-to;
        bh=Zadsu5nyn5Oj/L9kcoO0DAA+l35vjiivJhfOh8fNr08=;
        b=Z6yNYMJGi7cKVTEg16ryOGpoIl8uiqQt2QUkq2GbHwgE/hGC55VhScefq6Jcv+qjuZ
         rJYYyU8hsowqiGzf6PcgAyqmv50TPhQYqAmYV0U5Yc9M/DrmwRgRkNxVL7moLF7jiyLe
         8BpvucMBw7VvKLCiqew5DHNMBZMjAsjtgPpiJlCg4NnXbsT/1+ng7ndTIOEJ4ymMO/ZH
         0KVqg8NVTW1AFsh7iN0tkv6iAjx6VJOzFP+qNVJWPDtFm2h0k1r1H+55vrnSTf/A7Ai8
         wghWTp8txTAAliRUY5bPMXnK3QLWIO+ZIlLvH7O+Y64cFk/rZNZoWFQbpJktIkkBk9Tb
         2tyA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20230601; t=1712066322; x=1712671122; darn=gnusha.org;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence: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=Zadsu5nyn5Oj/L9kcoO0DAA+l35vjiivJhfOh8fNr08=;
        b=drs2Ru73aGQXB3OESO1BazMcEuEYKTZY+1PwQdjkYvSGPFAHHMsHY8t06Q7sFFedXy
         befuKPgZ3zlvYYKfpSJVY394ihTKVelfFO3zQhxQyYLAOOQ0AiVor2IJZMLmuDqAW/7y
         Qoq69dFKFdUgdyBdPJk9hSOIRNeuuX5mnCRjNkfjQlPEvVdr4W4/+RRCeZw5tDYXUYxd
         V3+XmxiV0O0AwHyMeK/S2xP0x6OVUs6TFhm1vu1iNf1+55H2lOV9wOkhmDzxszaLryPu
         h3QwKyWY+Tz7eBN0XnZIDxn3GD8teYSG+SfSbiyCadRooGBzPKaIPY9F5+18Qr3ziFP4
         PXtg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1712066322; x=1712671122;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-sender:mime-version
         :subject:references:in-reply-to:message-id:to:from:date:x-beenthere
         :x-gm-message-state:sender:from:to:cc:subject:date:message-id
         :reply-to;
        bh=Zadsu5nyn5Oj/L9kcoO0DAA+l35vjiivJhfOh8fNr08=;
        b=QdoFqNKXbAjU/x6tgqTfFdC7Sa5rmTZXMcKR8UsuY6vYngEvLdtLTijs9v76IC/JbF
         rWdk8zxX2t5iS0StzttWKQiUYuLbNhPJUsFToU/+aROceXFL+UB9QPKNLXn5aKlne/0o
         5OfnHiYEjq7dpNrwZiNGJN4QBt0efBA7YKrrvcY/ITHWABGGqLG6gYowDcwTB3FoxJD8
         9Hu9x/dA2ep88kUIhzh0p9aUnvN2ERrGwVunnTYrgd+RwNo7qoRGdSDHwjeluP6OVhqw
         aronPMMfgLfuTOiljXl0sIHbdoO/XEw6q0+lX9lTNomRGfq2+dWKj0yRj6BMt7lU8I2E
         Nq9Q==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=1; AJvYcCWVDcW7MA2IuiDYysg6DVAS84qvu1xXSvNcVjuLbf/W+91XpklpXzgKRUPo4dsRp1maLuX8tEEQbZpRsGP2Q4e48twE0Rk=
X-Gm-Message-State: AOJu0YyY1HcalVltQ6fz6O0AIR7i/iCV1wk9yQPVJccab8EGNMeUI/Au
	1tLhf51dvUWIOgP5nceTijrrHmH9g/WpUYl4qeZ+lInmlSR56OBH
X-Google-Smtp-Source: AGHT+IFInNLcLWpBwdEIsgCfKYC4uLmrAZLloqiKhbYJxpq5hKUmx5GpRIV54/z9P30nl837X54snQ==
X-Received: by 2002:a25:3546:0:b0:dcd:5635:5c11 with SMTP id c67-20020a253546000000b00dcd56355c11mr10849301yba.45.1712066321560;
        Tue, 02 Apr 2024 06:58:41 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com
Received: by 2002:a25:d8d7:0:b0:dcc:4b24:c0dd with SMTP id p206-20020a25d8d7000000b00dcc4b24c0ddls1607477ybg.0.-pod-prod-08-us;
 Tue, 02 Apr 2024 06:58:40 -0700 (PDT)
X-Received: by 2002:a05:690c:24c:b0:614:2c5c:d275 with SMTP id ba12-20020a05690c024c00b006142c5cd275mr3247834ywb.4.1712066320285;
        Tue, 02 Apr 2024 06:58:40 -0700 (PDT)
Received: by 2002:a05:690c:399:b0:609:3e5d:63d0 with SMTP id 00721157ae682-614306bf5bcms7b3;
        Tue, 2 Apr 2024 06:49:25 -0700 (PDT)
X-Received: by 2002:a05:6902:2306:b0:dcc:50ca:e153 with SMTP id do6-20020a056902230600b00dcc50cae153mr3992633ybb.7.1712065763341;
        Tue, 02 Apr 2024 06:49:23 -0700 (PDT)
Date: Tue, 2 Apr 2024 06:49:22 -0700 (PDT)
From: /dev /fd0 <alicexbtong@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <16a728e9-e987-4e7b-bace-2629143d173fn@googlegroups.com>
In-Reply-To: <f14cf0de-20f2-4786-bb92-d686a73c1218@achow101.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>
Subject: Re: [bitcoindev] Re: Adding New BIP Editors
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_46188_1726060605.1712065762908"
X-Original-Sender: alicexbtong@gmail.com
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.5 (/)

------=_Part_46188_1726060605.1712065762908
Content-Type: multipart/alternative; 
	boundary="----=_Part_46189_192944896.1712065762908"

------=_Part_46189_192944896.1712065762908
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

>  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 recently=20
and creation of BINANA. Previous BIP editor refused to assign numbers to=20
some BIPs. Kanzure had [tweeted][0] asking users on twitter if a BIP should=
=20
be assigned number. So I am curious what process exactly would be followed=
=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 came
> 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:
> > I think before we decide new BIP editors its important to discuss some=
=20
> > things about the process itself:
> >=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 ope=
n=20
> > a PR. After copy-editing and acceptance, it will be published here."
> >=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" by=
=20
> > being moderators for mailing list and BIP editors.
>
> 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.
>
> 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 what=
=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.
>
> > 2. How are numbers going to be assigned to BIPs?
>
> 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.
>
> > 3. Will there be copy of BIPs and pull requests maintained elsewhere=20
> > like bitcoin core?
>
> 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.
>
> > 4. What are the expectations from new BIP editors? In what situation do=
=20
> > we look for next BIP editors or in other words, what will be the proces=
s=20
> > to remove an editor if lot of people are unhappy with their work?
>
> 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 the=
=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.
>
> 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 raising=
=20
> a complaint about one of the editors on this mailing list or some other=
=20
> place a discussion, and a community discussion commences about whether=20
> or not to remove them.
>
> There are certainly situations where one of the GitHub org owners may=20
> take emergency action and remove a maintainer's privileges. This is only=
=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 that=
=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 came=
=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.
>
> Ava
>
> >=20
> > /dev/fd0
> > floppy disk guy
> >=20
> > On Monday, April 1, 2024 at 9:16:54=E2=80=AFPM UTC David A. Harding wro=
te:
> >=20
> > On 2024-03-28 10:04, Matt Corallo wrote:
> > > Please provide justification rather than simply saying "I like
> > Bob!".
> >=20
> > Using only comments from the mailing list, the following appears to be
> > the candidate list along with the current support. Asterisks denote
> > candidates who indicated their willingness to accept the role.
> >=20
> > - Bryan "Kanzure" Bishop, recommended by Ava Chow[1], Chris Stewart[3],
> > Michael Folkson[6], Peter Todd[9], Matt Corallo[10], Brandon
> > Black[11],
> > Antoine Riard[12], Murch[13], Antoine Poinsot[15], John Carvalho[16]
> >=20
> > - Ruben Somsen, recommended by Ava Chow[1], Chris Stewart[3], Michael
> > Folkson[6], Antoine Riard[12], Murch[13], Antoine Poinsot[15], John
> > Carvalho[16]
> >=20
> > - Jon Atack*, recommended by Luke Dashjr[2], Chris Stewart[3],
> > /dev/fd0[5][7],
> > Brandon Black[11], Antoine Riard[12], Ava Chow[14], John Carvalho[16]
> >=20
> > - Olaoluwa "Roasbeef" Osuntokun, recommended by Chris Stewart[3], John
> > C. Vernaleo[4], /dev/fd0[5][7], Keagan McClelland[8], Antoine
> > Riard[12], Ava Chow[14]
> >=20
> > - Mark "Murch" Erhardt*, recommended by Michael Folkson[6], Keagan
> > McClelland[8], Matt Corallo[10], Brandon Black[11], Antoine Riard[12],
> > Ava Chow[14]
> >=20
> > - Michael Folkson*
> >=20
> > Note: Luke Dashjr proposed[17] Seccour and Greg Tonoski for "non-dev
> > triaging", Tonoski proposed himself[18] for "BIP editor", and Antoine
> > Riard[12] proposed Seccour for "decentralized PM".
> >=20
> > I searched the BIPs repo by commenter to see if any of the above
> > candidates had been especially active there, which is listed below as:
> > total PRs they commented on (number still open/number closed).
> >=20
> > - 21 (1/20) commenter:kanzure
> > - 3 (2/1) commenter:rubensomsen
> > - 15 (0/15) commenter:jonatack
> > - 18 (2/16) commenter:roasbeef
> > - 10 (6/4) commenter:Murchandamus
> > - 57 (6/51) commenter:michaelfolkson
> >=20
> > I'll also note that Osuntokun is the only member of the set to have a
> > merged BIP that they co-authored, although I believe there are
> > far-along
> > draft BIPs for both Murch (terminology) and Somsen (Silent Payments). I
> > don't think this should be a requirement, but I do think it
> > demonstrates
> > familiarity with the process.
> >=20
> > Speaking only for myself, I think all of the candidates above with
> > multiple recommendations from other community participants are fully
> > qualified for the role, so I'll only provide a detailed justification
> > for the person who would be my first pick: Murch is not only a
> > longstanding and broadly liked Bitcoin contributor, but (as Corallo
> > mentioned) he has worked on standardizing terminology through a draft
> > BIP. In addition, he provided an extremely detailed review of all 300
> > pages of a draft of Mastering Bitcoin (3rd edition) and has reviewed
> > drafts of over 200 weekly Optech newsletters, in both cases
> > significantly improving the accuracy and comprehensibility of the
> > documentation. To me, that seems very similar to the work we'd ask him
> > to perform as a BIPs editor and it's something that he's already doing,
> > so I think there's an excellent fit of person to role.
> >=20
> > -Dave
> >=20
> > [1]
> > https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8...@achow101.com/
> > <https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8...@achow101.com/=
=20
> <https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8-ba1a-c9d97927551e@ac=
how101.com/>
> >
> > [2]
> > https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106...@dashjr.org/
> > <https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106...@dashjr.org/=20
> <https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106-b843-c1ff8f8a62a3@da=
shjr.org/>
> >
> > [3]
> > https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a...@googlegroups.com=
/=20
> <https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a...@googlegroups.com/=
=20
> <https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n@g=
ooglegroups.com/>
> >
> > [4]
> > https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.com=
/=20
> <https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.com/=
=20
> <https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333-fd28-bdd55899b713@ne=
tpurgatory.com/>
> >
> > [5]
> > https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.com=
/=20
> <https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.com/=
=20
> <https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36-be81-7c3719157fabn@g=
ooglegroups.com/>
> >
> > [6]
> > https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.com=
/=20
> <https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.com/=
=20
> <https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2-a787-639a3564d006n@g=
ooglegroups.com/>
> >
> > [7]
> > https://gnusha.org/pi/bitcoindev/846b668f-8386-4869...@googlegroups.com=
/=20
> <https://gnusha.org/pi/bitcoindev/846b668f-8386-4869...@googlegroups.com/=
=20
> <https://gnusha.org/pi/bitcoindev/846b668f-8386-4869-a3b1-55d346efbea1n@g=
ooglegroups.com/>
> >
> > [8]
> >=20
> https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEazRA=
5...@mail.gmail.com/=20
> <
> https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEazRA=
5...@mail.gmail.com/=20
> <https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEazR=
A5nVw9siYCPj4A@mail.gmail.com/>
> >
> > [9] https://gnusha.org/pi/bitcoindev/ZgePPvbf...@petertodd.org/
> > <https://gnusha.org/pi/bitcoindev/ZgePPvbf...@petertodd.org/=20
> <https://gnusha.org/pi/bitcoindev/ZgePPvbfrr4wZG7k@petertodd.org/>>
> > [10]
> > https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5...@mattcorallo.com/=
=20
> <https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5...@mattcorallo.com/=
=20
> <https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5-86e2-7ba0336a9bf2@ma=
ttcorallo.com/>
> >
> > [11] https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg69V@console/
> > <https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg69V@console/>
> > [12]
> >=20
> https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+E...@mail.gmail.=
com/=20
> <
> https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+E...@mail.gmail.=
com/=20
> <https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+EKMCP5oEbHSKSXp=
q0VKVBhJLhrw@mail.gmail.com/>
> >
> > [13]
> > https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a...@murch.one/
> > <https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a...@murch.one/=20
> <https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a-920b-32bd88d5e778@mu=
rch.one/>
> >
> > [14]
> > https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f...@achow101.com/
> > <https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f...@achow101.com/=
=20
> <https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f-866d-c555b80b0644@ac=
how101.com/>
> >
> > [15]
> >=20
> https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh=
7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@prot=
onmail.com/=20
> <
> https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh=
7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@prot=
onmail.com/
> >
> > [16]
> > https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552...@googlegroups.com=
/=20
> <https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552...@googlegroups.com/=
=20
> <https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552-88ca-11b9ed340661n@g=
ooglegroups.com/>
> >
> > [17]
> >=20
> https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qr=
st+...@mail.gmail.com/=20
> <
> https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qr=
st+...@mail.gmail.com/=20
> <https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Q=
rst+nmyypaedYZgg@mail.gmail.com/>
> >
> >=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/cbb0b74f-c60b-4c8a-9e97-9b1c=
0e0eb047n%40googlegroups.com=20
> <
> https://groups.google.com/d/msgid/bitcoindev/cbb0b74f-c60b-4c8a-9e97-9b1c=
0e0eb047n%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/16a728e9-e987-4e7b-bace-2629143d173fn%40googlegroups.com.

------=_Part_46189_192944896.1712065762908
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

&gt;=C2=A0

Does it matter? The number that a proposal gets has no impact on<br />&gt; =
literally anything else. They could do it sequentially and it wouldn't<br /=
>&gt; actually make a difference as long as there are no collisions.<div><b=
r /></div><div>Process followed to assign the number started this whole deb=
ate recently and creation of BINANA. Previous BIP editor refused to assign =
numbers to some BIPs. Kanzure had [tweeted][0] asking users on twitter if a=
 BIP should be assigned number. So I am curious what process exactly would =
be followed by new BIP editors.</div><div><br /></div><div>&gt; For example=
, this was done when Luke was hacked -</div>&gt; all of his permissions wer=
e immediately removed as soon as the news came<br />&gt; out, and were only=
 returned several months later once verified<br />&gt; communication with L=
uke were established and he was certain that his<br />&gt; GitHub account w=
as no longer (at risk of being) compromised.<div><br /></div><div>Thanks fo=
r sharing. I wasn't aware of this.<br /><div><br /></div><div>[0]:=C2=A0htt=
ps://x.com/kanzure/status/1752663903715168280</div><div><br /></div><div>/d=
ev/fd0</div><div>floppy 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"gmai=
l_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>&gt; I think before we decide new BIP editors its important to discuss =
some=20
<br>&gt; things about the process itself:
<br>&gt;=20
<br>&gt; 1. Quoting first paragraph from BIPs repo README: &quot;People wis=
hing to=20
<br>&gt; submit BIPs, first should propose their idea or document to the=20
<br>&gt; <a href data-email-masked rel=3D"nofollow">bitco...@lists.linuxfou=
ndation.org</a> mailing list (do not assign a=20
<br>&gt; number - read BIP 2 for the full process). After discussion, pleas=
e open=20
<br>&gt; a PR. After copy-editing and acceptance, it will be published here=
.&quot;
<br>&gt;=20
<br>&gt; If Kanzure and Ruben are BIP editors, does it mean they can censor=
=20
<br>&gt; someone from submitting BIPs? This question makes sense because th=
ey=20
<br>&gt; will have control over the whole improvement process for &quot;bit=
coin&quot; by=20
<br>&gt; 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&#39;t change that. It&#39;s not clear to me that this requiremen=
t 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&#39;s no different than=
 what=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>&gt; 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&#3=
9;t=20
<br>actually make a difference as long as there are no collisions.
<br>
<br>&gt; 3. Will there be copy of BIPs and pull requests maintained elsewhe=
re=20
<br>&gt; like bitcoin core?
<br>
<br>I&#39;m not sure why this is relevant to this discussion, but presumabl=
y=20
<br>there already are, and if there aren&#39;t, you can do it yourself. It&=
#39;s=20
<br>just like any other repo on GitHub.
<br>
<br>&gt; 4. What are the expectations from new BIP editors? In what situati=
on do=20
<br>&gt; we look for next BIP editors or in other words, what will be the p=
rocess=20
<br>&gt; 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&#39;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&#39;s privileges. This is=
 only=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>&gt;=20
<br>&gt; /dev/fd0
<br>&gt; floppy disk guy
<br>&gt;=20
<br>&gt; On Monday, April 1, 2024 at 9:16:54=E2=80=AFPM UTC David A. Hardin=
g wrote:
<br>&gt;=20
<br>&gt;     On 2024-03-28 10:04, Matt Corallo wrote:
<br>&gt;      &gt; Please provide justification rather than simply saying &=
quot;I like
<br>&gt;     Bob!&quot;.
<br>&gt;=20
<br>&gt;     Using only comments from the mailing list, the following appea=
rs to be
<br>&gt;     the candidate list along with the current support. Asterisks d=
enote
<br>&gt;     candidates who indicated their willingness to accept the role.
<br>&gt;=20
<br>&gt;     - Bryan &quot;Kanzure&quot; Bishop, recommended by Ava Chow[1]=
, Chris Stewart[3],
<br>&gt;     Michael Folkson[6], Peter Todd[9], Matt Corallo[10], Brandon
<br>&gt;     Black[11],
<br>&gt;     Antoine Riard[12], Murch[13], Antoine Poinsot[15], John Carval=
ho[16]
<br>&gt;=20
<br>&gt;     - Ruben Somsen, recommended by Ava Chow[1], Chris Stewart[3], =
Michael
<br>&gt;     Folkson[6], Antoine Riard[12], Murch[13], Antoine Poinsot[15],=
 John
<br>&gt;     Carvalho[16]
<br>&gt;=20
<br>&gt;     - Jon Atack*, recommended by Luke Dashjr[2], Chris Stewart[3],
<br>&gt;     /dev/fd0[5][7],
<br>&gt;     Brandon Black[11], Antoine Riard[12], Ava Chow[14], John Carva=
lho[16]
<br>&gt;=20
<br>&gt;     - Olaoluwa &quot;Roasbeef&quot; Osuntokun, recommended by Chri=
s Stewart[3], John
<br>&gt;     C. Vernaleo[4], /dev/fd0[5][7], Keagan McClelland[8], Antoine
<br>&gt;     Riard[12], Ava Chow[14]
<br>&gt;=20
<br>&gt;     - Mark &quot;Murch&quot; Erhardt*, recommended by Michael Folk=
son[6], Keagan
<br>&gt;     McClelland[8], Matt Corallo[10], Brandon Black[11], Antoine Ri=
ard[12],
<br>&gt;     Ava Chow[14]
<br>&gt;=20
<br>&gt;     - Michael Folkson*
<br>&gt;=20
<br>&gt;     Note: Luke Dashjr proposed[17] Seccour and Greg Tonoski for &q=
uot;non-dev
<br>&gt;     triaging&quot;, Tonoski proposed himself[18] for &quot;BIP edi=
tor&quot;, and Antoine
<br>&gt;     Riard[12] proposed Seccour for &quot;decentralized PM&quot;.
<br>&gt;=20
<br>&gt;     I searched the BIPs repo by commenter to see if any of the abo=
ve
<br>&gt;     candidates had been especially active there, which is listed b=
elow as:
<br>&gt;     total PRs they commented on (number still open/number closed).
<br>&gt;=20
<br>&gt;     - 21 (1/20) commenter:kanzure
<br>&gt;     - 3 (2/1) commenter:rubensomsen
<br>&gt;     - 15 (0/15) commenter:jonatack
<br>&gt;     - 18 (2/16) commenter:roasbeef
<br>&gt;     - 10 (6/4) commenter:Murchandamus
<br>&gt;     - 57 (6/51) commenter:michaelfolkson
<br>&gt;=20
<br>&gt;     I&#39;ll also note that Osuntokun is the only member of the se=
t to have a
<br>&gt;     merged BIP that they co-authored, although I believe there are
<br>&gt;     far-along
<br>&gt;     draft BIPs for both Murch (terminology) and Somsen (Silent Pay=
ments). I
<br>&gt;     don&#39;t think this should be a requirement, but I do think i=
t
<br>&gt;     demonstrates
<br>&gt;     familiarity with the process.
<br>&gt;=20
<br>&gt;     Speaking only for myself, I think all of the candidates above =
with
<br>&gt;     multiple recommendations from other community participants are=
 fully
<br>&gt;     qualified for the role, so I&#39;ll only provide a detailed ju=
stification
<br>&gt;     for the person who would be my first pick: Murch is not only a
<br>&gt;     longstanding and broadly liked Bitcoin contributor, but (as Co=
rallo
<br>&gt;     mentioned) he has worked on standardizing terminology through =
a draft
<br>&gt;     BIP. In addition, he provided an extremely detailed review of =
all 300
<br>&gt;     pages of a draft of Mastering Bitcoin (3rd edition) and has re=
viewed
<br>&gt;     drafts of over 200 weekly Optech newsletters, in both cases
<br>&gt;     significantly improving the accuracy and comprehensibility of =
the
<br>&gt;     documentation. To me, that seems very similar to the work we&#=
39;d ask him
<br>&gt;     to perform as a BIPs editor and it&#39;s something that he&#39=
;s already doing,
<br>&gt;     so I think there&#39;s an excellent fit of person to role.
<br>&gt;=20
<br>&gt;     -Dave
<br>&gt;=20
<br>&gt;     [1]
<br>&gt;     <a href=3D"https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8=
...@achow101.com/" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/2092f7ff-4860-47f8...@achow101.com/&amp;source=3Dgmail&amp;ust=3D17121=
51592705000&amp;usg=3DAOvVaw2HOTHohRHAlQfk2grtSOqA">https://gnusha.org/pi/b=
itcoindev/2092f7ff-4860-47f8...@achow101.com/</a>
<br>&gt;     &lt;<a href=3D"https://gnusha.org/pi/bitcoindev/2092f7ff-4860-=
47f8-ba1a-c9d97927551e@achow101.com/" target=3D"_blank" rel=3D"nofollow" da=
ta-saferedirecturl=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gn=
usha.org/pi/bitcoindev/2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com/&a=
mp;source=3Dgmail&amp;ust=3D1712151592705000&amp;usg=3DAOvVaw1daVPpzmmzI0Bb=
vuyiXItM">https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8...@achow101.c=
om/</a>&gt;
<br>&gt;     [2]
<br>&gt;     <a href=3D"https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106=
...@dashjr.org/" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=3D=
"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bitcoinde=
v/9288df7b-f2e9-4106...@dashjr.org/&amp;source=3Dgmail&amp;ust=3D1712151592=
705000&amp;usg=3DAOvVaw1IgnT1DrLdAMyNkFQyC-T-">https://gnusha.org/pi/bitcoi=
ndev/9288df7b-f2e9-4106...@dashjr.org/</a>
<br>&gt;     &lt;<a href=3D"https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-=
4106-b843-c1ff8f8a62a3@dashjr.org/" target=3D"_blank" rel=3D"nofollow" data=
-saferedirecturl=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnus=
ha.org/pi/bitcoindev/9288df7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org/&amp;s=
ource=3Dgmail&amp;ust=3D1712151592705000&amp;usg=3DAOvVaw33ldMKI7SDh1WwNaC2=
dkJn">https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106...@dashjr.org/</a=
>&gt;
<br>&gt;     [3]
<br>&gt;     <a href=3D"https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a=
...@googlegroups.com/" target=3D"_blank" rel=3D"nofollow" data-saferedirect=
url=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bit=
coindev/d1e7183c-30e6-4f1a...@googlegroups.com/&amp;source=3Dgmail&amp;ust=
=3D1712151592705000&amp;usg=3DAOvVaw3qpPhXq53q63FtVkKaJ9np">https://gnusha.=
org/pi/bitcoindev/d1e7183c-30e6-4f1a...@googlegroups.com/</a> &lt;<a href=
=3D"https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n@=
googlegroups.com/" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n@googlegroups.com/&amp;source=3Dg=
mail&amp;ust=3D1712151592705000&amp;usg=3DAOvVaw3OdU9qI7mRYf-h1cQzFdOY">htt=
ps://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a...@googlegroups.com/</a>&g=
t;
<br>&gt;     [4]
<br>&gt;     <a href=3D"https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333=
...@netpurgatory.com/" target=3D"_blank" rel=3D"nofollow" data-saferedirect=
url=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bit=
coindev/84309c3f-e848-d333...@netpurgatory.com/&amp;source=3Dgmail&amp;ust=
=3D1712151592705000&amp;usg=3DAOvVaw0VgElfiidr0tSNh8PE6Koq">https://gnusha.=
org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.com/</a> &lt;<a href=
=3D"https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333-fd28-bdd55899b713@n=
etpurgatory.com/" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/84309c3f-e848-d333-fd28-bdd55899b713@netpurgatory.com/&amp;source=3Dgm=
ail&amp;ust=3D1712151592705000&amp;usg=3DAOvVaw36gRuCtA4HYCXsqRB0QCVp">http=
s://gnusha.org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.com/</a>&gt=
;
<br>&gt;     [5]
<br>&gt;     <a href=3D"https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36=
...@googlegroups.com/" target=3D"_blank" rel=3D"nofollow" data-saferedirect=
url=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bit=
coindev/4c1462b7-ea1c-4a36...@googlegroups.com/&amp;source=3Dgmail&amp;ust=
=3D1712151592705000&amp;usg=3DAOvVaw3lFoLIUyiLx2SEyAFfr56J">https://gnusha.=
org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.com/</a> &lt;<a href=
=3D"https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36-be81-7c3719157fabn@=
googlegroups.com/" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/4c1462b7-ea1c-4a36-be81-7c3719157fabn@googlegroups.com/&amp;source=3Dg=
mail&amp;ust=3D1712151592705000&amp;usg=3DAOvVaw1OjG-ZiKT0VjgyETp_2EX7">htt=
ps://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.com/</a>&g=
t;
<br>&gt;     [6]
<br>&gt;     <a href=3D"https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2=
...@googlegroups.com/" target=3D"_blank" rel=3D"nofollow" data-saferedirect=
url=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bit=
coindev/a116fba3-5948-48d2...@googlegroups.com/&amp;source=3Dgmail&amp;ust=
=3D1712151592705000&amp;usg=3DAOvVaw2D_01ctfhzqFQ4uhUmlKK0">https://gnusha.=
org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.com/</a> &lt;<a href=
=3D"https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2-a787-639a3564d006n@=
googlegroups.com/" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/a116fba3-5948-48d2-a787-639a3564d006n@googlegroups.com/&amp;source=3Dg=
mail&amp;ust=3D1712151592705000&amp;usg=3DAOvVaw0mSZhWBC6kdUVcDSG7rxr0">htt=
ps://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.com/</a>&g=
t;
<br>&gt;     [7]
<br>&gt;     <a href=3D"https://gnusha.org/pi/bitcoindev/846b668f-8386-4869=
...@googlegroups.com/" target=3D"_blank" rel=3D"nofollow" data-saferedirect=
url=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bit=
coindev/846b668f-8386-4869...@googlegroups.com/&amp;source=3Dgmail&amp;ust=
=3D1712151592705000&amp;usg=3DAOvVaw2qE2d16CCPxd47F3f-Eoi6">https://gnusha.=
org/pi/bitcoindev/846b668f-8386-4869...@googlegroups.com/</a> &lt;<a href=
=3D"https://gnusha.org/pi/bitcoindev/846b668f-8386-4869-a3b1-55d346efbea1n@=
googlegroups.com/" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/846b668f-8386-4869-a3b1-55d346efbea1n@googlegroups.com/&amp;source=3Dg=
mail&amp;ust=3D1712151592705000&amp;usg=3DAOvVaw2D-bGDINhXRKojk4zyNp7L">htt=
ps://gnusha.org/pi/bitcoindev/846b668f-8386-4869...@googlegroups.com/</a>&g=
t;
<br>&gt;     [8]
<br>&gt;     <a href=3D"https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS=
110ut8tX=3DwruqgLEazRA5...@mail.gmail.com/" target=3D"_blank" rel=3D"nofoll=
ow" data-saferedirecturl=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttp=
s://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX%3DwruqgLEazRA5...@m=
ail.gmail.com/&amp;source=3Dgmail&amp;ust=3D1712151592705000&amp;usg=3DAOvV=
aw1ycCcUbq5pQ0gnsC3FJKFR">https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7Y=
RS110ut8tX=3DwruqgLEazRA5...@mail.gmail.com/</a> &lt;<a href=3D"https://gnu=
sha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEazRA5nVw9siYCPj4A=
@mail.gmail.com/" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/CALeFGL1-LKPWd7YRS110ut8tX%3DwruqgLEazRA5nVw9siYCPj4A@mail.gmail.com/&=
amp;source=3Dgmail&amp;ust=3D1712151592705000&amp;usg=3DAOvVaw3c6UwEb1l7Unb=
5lIsJIKFt">https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3Dwr=
uqgLEazRA5...@mail.gmail.com/</a>&gt;
<br>&gt;     [9] <a href=3D"https://gnusha.org/pi/bitcoindev/ZgePPvbf...@pe=
tertodd.org/" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=3D"ht=
tps://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bitcoindev/Z=
gePPvbf...@petertodd.org/&amp;source=3Dgmail&amp;ust=3D1712151592705000&amp=
;usg=3DAOvVaw1dPAcI9_HRJwVyfHDhoK0f">https://gnusha.org/pi/bitcoindev/ZgePP=
vbf...@petertodd.org/</a>
<br>&gt;     &lt;<a href=3D"https://gnusha.org/pi/bitcoindev/ZgePPvbfrr4wZG=
7k@petertodd.org/" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/ZgePPvbfrr4wZG7k@petertodd.org/&amp;source=3Dgmail&amp;ust=3D171215159=
2705000&amp;usg=3DAOvVaw05hvLV_ttUNHeWidusJQ7Y">https://gnusha.org/pi/bitco=
indev/ZgePPvbf...@petertodd.org/</a>&gt;
<br>&gt;     [10]
<br>&gt;     <a href=3D"https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5=
...@mattcorallo.com/" target=3D"_blank" rel=3D"nofollow" data-saferedirectu=
rl=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bitc=
oindev/f9435999-42df-46b5...@mattcorallo.com/&amp;source=3Dgmail&amp;ust=3D=
1712151592705000&amp;usg=3DAOvVaw13whR2yoYxYSpkojZRqkLv">https://gnusha.org=
/pi/bitcoindev/f9435999-42df-46b5...@mattcorallo.com/</a> &lt;<a href=3D"ht=
tps://gnusha.org/pi/bitcoindev/f9435999-42df-46b5-86e2-7ba0336a9bf2@mattcor=
allo.com/" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=3D"https=
://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bitcoindev/f943=
5999-42df-46b5-86e2-7ba0336a9bf2@mattcorallo.com/&amp;source=3Dgmail&amp;us=
t=3D1712151592705000&amp;usg=3DAOvVaw1nWozz0lRjQO3hHLY7SKb2">https://gnusha=
.org/pi/bitcoindev/f9435999-42df-46b5...@mattcorallo.com/</a>&gt;
<br>&gt;     [11] <a href=3D"https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg=
69V@console/" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=3D"ht=
tps://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bitcoindev/Z=
gWRu32FXzqqg69V@console/&amp;source=3Dgmail&amp;ust=3D1712151592705000&amp;=
usg=3DAOvVaw2IbiJZrhzsn-XDyLQkRMP1">https://gnusha.org/pi/bitcoindev/ZgWRu3=
2FXzqqg69V@console/</a>
<br>&gt;     &lt;<a href=3D"https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg6=
9V@console/" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=3D"htt=
ps://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bitcoindev/Zg=
WRu32FXzqqg69V@console/&amp;source=3Dgmail&amp;ust=3D1712151592705000&amp;u=
sg=3DAOvVaw2IbiJZrhzsn-XDyLQkRMP1">https://gnusha.org/pi/bitcoindev/ZgWRu32=
FXzqqg69V@console/</a>&gt;
<br>&gt;     [12]
<br>&gt;     <a href=3D"https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO=
+FiF6+E...@mail.gmail.com/" target=3D"_blank" rel=3D"nofollow" data-safered=
irecturl=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/p=
i/bitcoindev/CALZpt%2BE8DohYEJ9aO%2BFiF6%2BE...@mail.gmail.com/&amp;source=
=3Dgmail&amp;ust=3D1712151592705000&amp;usg=3DAOvVaw19Z5aAyyIeGPCWT91e6k_e"=
>https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+E...@mail.gmail.c=
om/</a> &lt;<a href=3D"https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+=
FiF6+EKMCP5oEbHSKSXpq0VKVBhJLhrw@mail.gmail.com/" target=3D"_blank" rel=3D"=
nofollow" data-saferedirecturl=3D"https://www.google.com/url?hl=3Den&amp;q=
=3Dhttps://gnusha.org/pi/bitcoindev/CALZpt%2BE8DohYEJ9aO%2BFiF6%2BEKMCP5oEb=
HSKSXpq0VKVBhJLhrw@mail.gmail.com/&amp;source=3Dgmail&amp;ust=3D17121515927=
05000&amp;usg=3DAOvVaw0lOqiPQ4jPafD827mqh4wd">https://gnusha.org/pi/bitcoin=
dev/CALZpt+E8DohYEJ9aO+FiF6+E...@mail.gmail.com/</a>&gt;
<br>&gt;     [13]
<br>&gt;     <a href=3D"https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a=
...@murch.one/" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=3D"=
https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bitcoindev=
/53a0015c-b76a-441a...@murch.one/&amp;source=3Dgmail&amp;ust=3D171215159270=
5000&amp;usg=3DAOvVaw1_INikcpRJDSTv419r27Of">https://gnusha.org/pi/bitcoind=
ev/53a0015c-b76a-441a...@murch.one/</a>
<br>&gt;     &lt;<a href=3D"https://gnusha.org/pi/bitcoindev/53a0015c-b76a-=
441a-920b-32bd88d5e778@murch.one/" target=3D"_blank" rel=3D"nofollow" data-=
saferedirecturl=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnush=
a.org/pi/bitcoindev/53a0015c-b76a-441a-920b-32bd88d5e778@murch.one/&amp;sou=
rce=3Dgmail&amp;ust=3D1712151592705000&amp;usg=3DAOvVaw0Gj9BrO2qRgmExHLyhTi=
41">https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a...@murch.one/</a>&g=
t;
<br>&gt;     [14]
<br>&gt;     <a href=3D"https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f=
...@achow101.com/" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/ae482890-bce3-468f...@achow101.com/&amp;source=3Dgmail&amp;ust=3D17121=
51592705000&amp;usg=3DAOvVaw0gQ0qcV_vtPCQj9Nb0XCdS">https://gnusha.org/pi/b=
itcoindev/ae482890-bce3-468f...@achow101.com/</a>
<br>&gt;     &lt;<a href=3D"https://gnusha.org/pi/bitcoindev/ae482890-bce3-=
468f-866d-c555b80b0644@achow101.com/" target=3D"_blank" rel=3D"nofollow" da=
ta-saferedirecturl=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gn=
usha.org/pi/bitcoindev/ae482890-bce3-468f-866d-c555b80b0644@achow101.com/&a=
mp;source=3Dgmail&amp;ust=3D1712151592705000&amp;usg=3DAOvVaw2xDk8BYFZgxq-5=
6jcqguxW">https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f...@achow101.c=
om/</a>&gt;
<br>&gt;     [15]
<br>&gt;     <a href=3D"https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmI=
BVBd0WpT5Wof_oSBXsuizh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH=
4gwU1c2jS4xojo=3D@protonmail.com/" target=3D"_blank" rel=3D"nofollow" data-=
saferedirecturl=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnush=
a.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh7692AUDw2TojfvC=
qvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo%3D@protonmail.com/&amp=
;source=3Dgmail&amp;ust=3D1712151592706000&amp;usg=3DAOvVaw2RTnuV3p7wi_tnE6=
sMt-_e">https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSB=
Xsuizh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=
=3D@protonmail.com/</a> &lt;<a href=3D"https://gnusha.org/pi/bitcoindev/ppB=
S1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWa=
wf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@protonmail.com/" target=3D"_blank" rel=3D"=
nofollow" data-saferedirecturl=3D"https://www.google.com/url?hl=3Den&amp;q=
=3Dhttps://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuiz=
h7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo%3D@pro=
tonmail.com/&amp;source=3Dgmail&amp;ust=3D1712151592706000&amp;usg=3DAOvVaw=
2RTnuV3p7wi_tnE6sMt-_e">https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmI=
BVBd0WpT5Wof_oSBXsuizh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH=
4gwU1c2jS4xojo=3D@protonmail.com/</a>&gt;
<br>&gt;     [16]
<br>&gt;     <a href=3D"https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552=
...@googlegroups.com/" target=3D"_blank" rel=3D"nofollow" data-saferedirect=
url=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bit=
coindev/ad284018-e99c-4552...@googlegroups.com/&amp;source=3Dgmail&amp;ust=
=3D1712151592706000&amp;usg=3DAOvVaw241v_IBt4Gy1QZcd2nyn3_">https://gnusha.=
org/pi/bitcoindev/ad284018-e99c-4552...@googlegroups.com/</a> &lt;<a href=
=3D"https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552-88ca-11b9ed340661n@=
googlegroups.com/" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/pi/bitcoi=
ndev/ad284018-e99c-4552-88ca-11b9ed340661n@googlegroups.com/&amp;source=3Dg=
mail&amp;ust=3D1712151592706000&amp;usg=3DAOvVaw0iy7eXeN8lu7rLivyEprV5">htt=
ps://gnusha.org/pi/bitcoindev/ad284018-e99c-4552...@googlegroups.com/</a>&g=
t;
<br>&gt;     [17]
<br>&gt;     <a href=3D"https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo=
76PdqwJU=3D=3DYJMvd9Qrst+...@mail.gmail.com/" target=3D"_blank" rel=3D"nofo=
llow" data-saferedirecturl=3D"https://www.google.com/url?hl=3Den&amp;q=3Dht=
tps://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU%3D%3DYJMvd9Qrst%2=
B...@mail.gmail.com/&amp;source=3Dgmail&amp;ust=3D1712151592706000&amp;usg=
=3DAOvVaw1EaFDe_6XiG1fC3crlHydQ">https://gnusha.org/pi/bitcoindev/CAMHHROw9=
mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qrst+...@mail.gmail.com/</a> &lt;<a href=3D"ht=
tps://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qrst+n=
myypaedYZgg@mail.gmail.com/" target=3D"_blank" rel=3D"nofollow" data-safere=
directurl=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://gnusha.org/=
pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU%3D%3DYJMvd9Qrst%2BnmyypaedYZgg@mai=
l.gmail.com/&amp;source=3Dgmail&amp;ust=3D1712151592706000&amp;usg=3DAOvVaw=
1OO1NK_IwmrBovebsBzprB">https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo=
76PdqwJU=3D=3DYJMvd9Qrst+...@mail.gmail.com/</a>&gt;
<br>&gt;=20
<br>&gt; --=20
<br>&gt; You received this message because you are subscribed to the Google=
=20
<br>&gt; Groups &quot;Bitcoin Development Mailing List&quot; group.
<br>&gt; To unsubscribe from this group and stop receiving emails from it, =
send=20
<br>&gt; an email to <a href data-email-masked rel=3D"nofollow">bitcoindev+=
...@googlegroups.com</a>=20
<br>&gt; &lt;mailto:<a href data-email-masked rel=3D"nofollow">bitcoindev+.=
..@googlegroups.com</a>&gt;.
<br>&gt; To view this discussion on the web visit=20
<br>&gt; <a href=3D"https://groups.google.com/d/msgid/bitcoindev/cbb0b74f-c=
60b-4c8a-9e97-9b1c0e0eb047n%40googlegroups.com" target=3D"_blank" rel=3D"no=
follow" data-saferedirecturl=3D"https://www.google.com/url?hl=3Den&amp;q=3D=
https://groups.google.com/d/msgid/bitcoindev/cbb0b74f-c60b-4c8a-9e97-9b1c0e=
0eb047n%2540googlegroups.com&amp;source=3Dgmail&amp;ust=3D1712151592706000&=
amp;usg=3DAOvVaw1VVSDiHMpl3n-4sQSoepMA">https://groups.google.com/d/msgid/b=
itcoindev/cbb0b74f-c60b-4c8a-9e97-9b1c0e0eb047n%40googlegroups.com</a> &lt;=
<a href=3D"https://groups.google.com/d/msgid/bitcoindev/cbb0b74f-c60b-4c8a-=
9e97-9b1c0e0eb047n%40googlegroups.com?utm_medium=3Demail&amp;utm_source=3Df=
ooter" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=3D"https://w=
ww.google.com/url?hl=3Den&amp;q=3Dhttps://groups.google.com/d/msgid/bitcoin=
dev/cbb0b74f-c60b-4c8a-9e97-9b1c0e0eb047n%2540googlegroups.com?utm_medium%3=
Demail%26utm_source%3Dfooter&amp;source=3Dgmail&amp;ust=3D1712151592706000&=
amp;usg=3DAOvVaw1nLrrhyYc9nuAFeObX83TE">https://groups.google.com/d/msgid/b=
itcoindev/cbb0b74f-c60b-4c8a-9e97-9b1c0e0eb047n%40googlegroups.com?utm_medi=
um=3Demail&amp;utm_source=3Dfooter</a>&gt;.
<br>
<br></blockquote></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; 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/16a728e9-e987-4e7b-bace-2629143d173fn%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/16a728e9-e987-4e7b-bace-2629143d173fn%40googlegroups.com</a>.=
<br />

------=_Part_46189_192944896.1712065762908--

------=_Part_46188_1726060605.1712065762908--