Delivery-date: Sun, 21 Apr 2024 17:21:03 -0700 Received: from mail-qv1-f57.google.com ([209.85.219.57]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1ryhQa-00064w-Uo for bitcoindev@gnusha.org; Sun, 21 Apr 2024 17:21:03 -0700 Received: by mail-qv1-f57.google.com with SMTP id 6a1803df08f44-6a07a80bb54sf10719196d6.1 for ; Sun, 21 Apr 2024 17:21:00 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1713745255; cv=pass; d=google.com; s=arc-20160816; b=ECE/XUsu3BGMHTIaNH6L2MHKN6ZxAJTul5onqMERY4h+CcVbe3yJJeyl7NejMZ9x1y kqFllDt7X1lLHE3sKS2wLVe7dYnYeYZP4h8XE799Syji9Lpi4QO80sN5wGBwKLyDEUy3 uto/in5IDg+q1yCspH2JDXtm4lOoh8Z9pqXg3YxqgzEeNP59PWmM1E2g8rQRg8MEhxOC DHUbiQI8MGLw1fE+z+k6XHjsijGyiIRlVgrXJwGFIYAB3ZHH60siXceIuixhHwdCeSEu xV2KjZULhPTxIV1XxNxZXa0Ne2NIxuWFqfr/sWT6WJIFpnXUNHvh5RfDiTpVzIszHbMg He3Q== 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:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:sender:dkim-signature :dkim-signature; bh=9wbfFY0AhT40OX8wqX9VokMwBjcAvUBXkM1z9ykVzfQ=; fh=Ql/5z22axOZhZRIVWs+i3QYydtlM0b0ErYKNg4Hc9BE=; b=Bca2Cx0E83WzBH15ur9Ud3H/h119C+10CwfAPOcVHEERPrlFum1MAz+yaiDas7F1qQ rVyOVCCevaAfRQbOijUbP+wFuCnBTwzCP/26dNj4hY9Dg9uQqFYVOUvY+OXSWXiosqwp gnOfieJ08pMSal/n5gGnIy8AtquJKZ2fpdPei7si8fFc0HNq100OTW/b/uaM3aiKerie C1sqKZEwJJ7dQ6mIJkCo0z/XbhBzlSDwRKY6htZrlPLZB2kBs3V98vCcXzMSV/x55Anz AqImjUMIVtjYpBho4hGRpX8NlDrizvGcDHynP1govlMw07GU77RiruhdRvmL8f+V/Lym k+PA==; darn=gnusha.org ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=lwQmDuQT; spf=pass (google.com: domain of antoine.riard@gmail.com designates 2607:f8b0:4864:20::12a as permitted sender) smtp.mailfrom=antoine.riard@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1713745255; x=1714350055; 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:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:sender:from:to:cc:subject:date:message-id :reply-to; bh=9wbfFY0AhT40OX8wqX9VokMwBjcAvUBXkM1z9ykVzfQ=; b=Y1wfwqQudp5K68u9X7hC9xzuXdimfxWqHjhHSRhkXK/UInFYn0yvBZWrkV4KwPacXF Xe6lIQSVZhyyrhnAkmX4T78szzrLGTisp0BHYC7WZQgVejPip/2GbJMtl6g/UhOHsP8z FQtV+HvWzVcdsKYkuUzn3/v4m3+Ti3QIQ8xVgla1ZbXxM3NWslySLuTa0ZhbOzEfRJgB EtyiwFBAJcGQ15S+zGI3w5ooAUnoe7PLzi+yuTDtL6vRMiE35roJu+f2jIQax63bWtkl tSaafNzQzgxyPQJVlzA1Zbc3b/4Fr1AA93YKI6nmKVLaHNs+MNi5TarI8SPZ+ziOihLX isTA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713745255; x=1714350055; 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:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to; bh=9wbfFY0AhT40OX8wqX9VokMwBjcAvUBXkM1z9ykVzfQ=; b=aJCu/WOurj6AG71CzKZWw0MQ/WCegex//Bjeq9xd9Ky7eunDE1jP+Z+HqRr+otsai8 AkHbFvt9DW0Pa6A2ypzdpAHfHprA/B6wZvcDyTZ4nJzr9rD8lNL6bs1MttuNnc5P//ym puZR+TWwWOYtzDYdBSWjS06IyVUkgrnLLbmGXpqHzLXiMGVstJrpJNLHnfy/g5/faqk5 vCUECfviBLwnNBvsoV7gtHynOvQzuPuDEW9VjBk1kSfV9mk8q4KxOt+OdQhITf1cMsyH jMUHwAVnr4E1H7HTIKUn6yz/i9gTLAur0NAItb9bVAtNzn3aEIo2zj2mmduJtgw8YpZ2 rZlA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713745255; x=1714350055; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:x-beenthere:x-gm-message-state:sender:from :to:cc:subject:date:message-id:reply-to; bh=9wbfFY0AhT40OX8wqX9VokMwBjcAvUBXkM1z9ykVzfQ=; b=wtzCuCKrLn690MwweemsbP8QO48pId4z9NlfOk2vHagynpitilNEu8Pk0qjPcwuFtD O1n+BMIxz8Xnx/Oxuknn8M8LuBK4TrRB6tx9Fpt6Udt5ra8ZxF4e0nE20jMyj6WNG7dD Ima/3GElBDRBwV774j/6ZEdQC9gAhYQqX7N1j5YC8dIjuHAgO3IZ571TF+86P7k6Fu3t HPEWz5ct7C5DXmWboG+YDCuJyFxFrlG6mAzmluVK13UivDVVRI1re6pUKfawod8zpkql +e/PdccNI0r9NHg9vOA0FC/b9hNRTCZJsUPvDOyLcgpJz8+xxq0X47G7RTbIeS4VOZXS HoBA== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=2; AJvYcCXp/1KaKdx2l6VVe65gqKRTjZTLclV2EqmBQzYMzTi0rYH2CENkyjYG3SrkG49HIwDkkoiRcO1BI6D4b6OS9slKS8yOHN0= X-Gm-Message-State: AOJu0YyjNEGyoNC8zoLFvHQu1ndEBnzLAO2+r4wXSKCnpZFmWDcuihCw NCfNbhgMr3wY0S3ro9mafN7p0tfCshzhp5jP09g5bZQfvn7kVsZp X-Google-Smtp-Source: AGHT+IFeFWugqIl18ZO1rRga+w5mp3pE34U0JGPYSKEB3sTOUGnW5/f/a2YW4LbrU4uFV7DiptiDWw== X-Received: by 2002:a05:6214:11a3:b0:6a0:6f04:b290 with SMTP id u3-20020a05621411a300b006a06f04b290mr5325470qvv.42.1713745254319; Sun, 21 Apr 2024 17:20:54 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a05:6214:234d:b0:698:ed81:bc0e with SMTP id 6a1803df08f44-6a05d80e938ls53848226d6.1.-pod-prod-06-us; Sun, 21 Apr 2024 17:20:53 -0700 (PDT) X-Forwarded-Encrypted: i=2; AJvYcCWXS3OeiHsbdfwXDe947YcXXwS8tk3ji3EQDM5Qy0oPh/VpEO4ajE1agM2jd6FcxoteZRtCbUN3LSoS6tfRsCCkFBatBvZIvqCw/mQ= X-Received: by 2002:a05:6214:23ca:b0:69b:5d39:ea45 with SMTP id hr10-20020a05621423ca00b0069b5d39ea45mr338853qvb.13.1713745253305; Sun, 21 Apr 2024 17:20:53 -0700 (PDT) Received: by 2002:a05:620a:4710:b0:790:776b:3ab9 with SMTP id af79cd13be357-790776b3b3dms85a; Sun, 21 Apr 2024 13:48:21 -0700 (PDT) X-Forwarded-Encrypted: i=2; AJvYcCWFz42yy/Y9HFzspIMmDyjrFi0SseUzuGa2czHb2BNed098z9+/vZh7Qv6UfUbdOKWH4JYbiK/jVnrUhXH/jtqBKrcd692EaFp+dfs= X-Received: by 2002:ac8:7e94:0:b0:437:c08f:e57d with SMTP id w20-20020ac87e94000000b00437c08fe57dmr11563455qtj.22.1713732500272; Sun, 21 Apr 2024 13:48:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1713732500; cv=none; d=google.com; s=arc-20160816; b=iDQdVrqfiwa4Kx2SALDsrg32PwZmsA293R0GkDR3yC7T5CsuHjsERFLI6xdyWoI4/v 3hgWdZ9VW/SfCu8mSInd21lcFeXm/5On8rYt+vFMq6gWpqdxgV6Veajw05+kkXb5eA8O jReIPo+QVaFV8KRu3hVeD+URyJ/Hzn5N5RNhcYV/NCbmaIRm7mtFTyBZkJZxK9FD0UY4 gooV+9nJhcNMmo3w8B/X0TZbJlehj3muZW1nEdoUGqnFFx3SJP4XatG63GSgtOIq8R3g fWxhc8WX2xe186JfW0Ldr2wvQFgGXVM0oeApIVW9VrmuzKGQAV79h1bd+9sJOOrYk843 /inQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=0Eulf+I+w1OT3UAXGIbjZ3p8XHazHCeqRyio96fVSX4=; fh=jDUajMA/ahiCihOzG/KoAXEHGjYs0ZV0jDC1ILnyhdk=; b=ElNxE1Fjylb+yr4KGWstR2FQFTqd7PK//lffEKvDhUac4m3bmrZ0j70BNmZhZwSXhl JGG6SaQ9e4nOS9t1q6q/9x+2v4twjiDotpsmZN8M3Y3QILzWFZ6wayGpRU0BMIELDYe4 Bf0Ne9/xr9od0p0sNCwjUlVXjEYyaoF73RZwCH20MmSlvh6Ph+uR9ElwsPL2xyFyEUg3 6JLx5MxzSwb/VgZSQUC/PBpymmJEAlrjdVpcg4ItGG3NcQkEDEKtxaFqh5VDAw8juDZS KWzzWScEXAuiD16Mn389aB+UwOSP6awWYNGGF3lTqhBPjeaouD99+jymjkfSccKerbgF 5YrQ==; dara=google.com ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=lwQmDuQT; spf=pass (google.com: domain of antoine.riard@gmail.com designates 2607:f8b0:4864:20::12a as permitted sender) smtp.mailfrom=antoine.riard@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from mail-il1-x12a.google.com (mail-il1-x12a.google.com. [2607:f8b0:4864:20::12a]) by gmr-mx.google.com with ESMTPS id en15-20020a05622a540f00b00439b3dea67dsi97072qtb.4.2024.04.21.13.48.20 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 21 Apr 2024 13:48:20 -0700 (PDT) Received-SPF: pass (google.com: domain of antoine.riard@gmail.com designates 2607:f8b0:4864:20::12a as permitted sender) client-ip=2607:f8b0:4864:20::12a; Received: by mail-il1-x12a.google.com with SMTP id e9e14a558f8ab-36a1b0777b7so15788785ab.0 for ; Sun, 21 Apr 2024 13:48:20 -0700 (PDT) X-Forwarded-Encrypted: i=1; AJvYcCWplgdzBsLA5HBJJInbRvz0MH0sUI0swDwNE/Z+fwXmGhnFCi2dW2+4UFyp58sr9TLp+hD0RCBdaxSJXM+spCgd4KBlb6bwkzyRlCc= X-Received: by 2002:a05:6e02:1541:b0:36b:f8:e884 with SMTP id j1-20020a056e02154100b0036b00f8e884mr12678296ilu.20.1713732499344; Sun, 21 Apr 2024 13:48:19 -0700 (PDT) MIME-Version: 1.0 References: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com> <070755a0-10e9-4903-9524-dd8ef98c1c8b@achow101.com> <0d4d85e3-9fbb-4bd4-af0f-92225e699b63@achow101.com> <97a10141-8847-417a-af11-d95e7d3be064@achow101.com> <0591e62d-12da-48ac-9d19-faea473c647c@achow101.com> <84bb3ca1-a18e-48c8-a934-6fcef5470a36@achow101.com> In-Reply-To: <84bb3ca1-a18e-48c8-a934-6fcef5470a36@achow101.com> From: Antoine Riard Date: Sun, 21 Apr 2024 21:48:07 +0100 Message-ID: Subject: Re: [bitcoindev] Re: Adding New BIP Editors To: Ava Chow Cc: Michael Folkson , bitcoindev@googlegroups.com Content-Type: multipart/alternative; boundary="000000000000dd1aa00616a1703c" X-Original-Sender: antoine.riard@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=lwQmDuQT; spf=pass (google.com: domain of antoine.riard@gmail.com designates 2607:f8b0:4864:20::12a as permitted sender) smtp.mailfrom=antoine.riard@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.5 (/) --000000000000dd1aa00616a1703c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > There has not been any actual objections to the nominees nor have there > been any suggestions on choosing a subset of them since my last email. > As such, there is rough consensus on adding Kanzure, Murch, Jonatack, > Ruben, and Roasbeef as BIP editors, and they will be added on Monday > April 22nd. ACK. Beyond that, I'll stick to my mail of the 1st April and I won't comment further on the subject of nominating new BIP editors. If anyone has thoughts on how to improve the BIP process for the _future_, I think real-or-random started a new thread called "Time for an update to BIP2?". Anyone can express themselves there and then start to champion a new BIP of type "process". Best, Antoine Le dim. 21 avr. 2024 =C3=A0 20:08, 'Ava Chow' via Bitcoin Development Maili= ng List a =C3=A9crit : > On 04/21/2024 01:57 PM, Michael Folkson wrote: > > So once a BIP number is allocated (or before) the BIP author can write > > whatever they like on that BIP? Including false and misleading > > statements? And the BIP editors have to merge it as long as it meets > > formatting requirements? > > I did not say that they can write anything, do not put words in my > mouth. Modifications to a BIP are held to the same standard as when it > is initially proposed. This standard is largely about formatting, but > also about keeping BIPs as actual technical specifications. So long as > the BIP after those modifications meet those requirements, then BIP > editors should merge them. > > > A misleading statement like "This soft fork will definitely activate > > at block X as it has been merged into implementation Y. It hasn't been > > merged into Bitcoin Core yet but Bitcoin Core will merge the soft fork > > after the activation" > > BIPs are specifications. They are not blog posts. They are not the place > for opining about whether or not something will activate. Such > statements would be off topic for a BIP and do not meet the standard for > merging, so no, I do not think that should be merged, and I do not think > any of the proposed BIP editors would merge such a PR. > > > > > This is a step change from before. If we aren't relying on *any* > > judgment then there might as well be 100 BIP editors. Because the > > editors aren't doing anything, each BIP author (or champion) has total > > license to write whatever they like on their BIP. > > > >> They are not arbiters of what is activated on Bitcoin. They are not > gatekeepers of soft forks. > > > > Of course not. The BIP editors do not decide what is activated on > > Bitcoin. But they are gatekeepers on ensuring BIPs are high quality > > and don't include false and misleading statements. Because false and > > misleading statements can impact the evolution of an activation > > process. > > > > I tried. Based on your perspective all we need is one malicious BIP > > author (or champion) and they'll make the entire BIP process a joke > > and the BIP editors won't be able to do anything. > > You are being deliberately obtuse and strawmanning. I did not say that > the BIP editors won't be able to do anything; I did not say that that a > BIP author can put whatever they want once they get a BIP number. > > I suggest that you read the BIP process thread split from this one for > opinions on how to refine the BIPs process to make it clearer as to what > BIP editors should be merging. > > Frankly, I don't understand what it is your are arguing for or trying to > achieve. You make absurd claims, use strawman arguments, and throw out > whataboutisms. This all seems to me to be concern trolling, and as such, > I see no reason to continue responding to you. > > Ava > > > > > Michael > > > > > > > > On Sun, Apr 21, 2024 at 5:39=E2=80=AFPM Ava Chow w= rote: > >> > >> You are misunderstanding the role of BIP editors. They are not arbiter= s > >> of what is activated on Bitcoin. They are not gatekeepers of soft fork= s. > >> If a BIP author proposes or agrees with a change to their BIP and thos= e > >> changes are formatted correctly, it is not the BIP editors' rights nor > >> responsibilities to refuse to merge that change. As with Bitcoin Core > >> maintainers, BIP editing is a largely janitorial role. > >> > >> Just because something is a BIP does not mean it is a good idea. Just > >> because a BIP specifying a fork contains deployment parameters does no= t > >> mean it will actually be deployed. There are several BIPs for both har= d > >> and soft forks that are rejected or withdrawn that have deployment > >> parameters. > >> > >> Furthermore, for myself, I would actually prefer that contentious soft > >> forks for which some people are legitimately attempting to activate ha= ve > >> their deployment parameters be specified in a/the BIP. Having competin= g > >> activation parameters in different BIPs is preferable over the > >> documentation being spread around in many different places. It makes i= t > >> much easier for implementations to inform users what they've actually > >> implemented so that users can make a more informed decision. > >> > >> On 04/21/2024 07:43 AM, Michael Folkson wrote: > >>> Ava > >>> > >>> Thanks for the detailed response, I appreciate the insight. > >>> > >>>>> I'm even more concerned about future soft fork activation attempts. > >>>>> These don't necessarily need to be attempted via a Bitcoin Core > merged > >>>>> pull request hence the BIPs repo could be a key source of informati= on > >>>>> and guidance on this. > >>> > >>>> This concern doesn't make any sense. There are already multiple soft > and > >>>> hard fork BIPs that are not active nor good ideas. A BIP does not ne= ed > >>>> to be a good idea. > >>> > >>> I would hope that a contentious soft fork and activation params for > >>> that contentious soft fork would not be merged into the Bitcoin Core > >>> codebase and up until now it hasn't been. I would hope all the Bitcoi= n > >>> Core maintainers understand that even if they personally think a soft > >>> fork is a good idea (apparently there is nothing to stop them merging > >>> it without discussing it with the other maintainers) that they > >>> shouldn't independently merge it if it is contentious. > >>> > >>> Similarly I would hope that all BIP editors would be careful about > >>> what information gets merged around soft fork activation *attempts* > >>> whether that be activation details on a particular soft fork BIP or o= n > >>> a separate activation BIP. With Taproot there were very strong > >>> disagreements over activation parameters for a non-contentious soft > >>> fork. It would be much messier for a contentious soft fork activation > >>> attempt. I'm not sure all these new BIP editors understand that or > >>> would perhaps even agree with that. For example Laolu is listed as a > >>> supporter of a CTV activation attempt back in 2022 [0] which was > >>> clearly contentious. That doesn't inspire me with confidence that as > >>> soon as he is a BIP editor he won't start merging details on > >>> contentious soft fork activation attempts in BIPs and merging that > >>> soft fork in say btcd. He would need to be removed as a BIP editor if > >>> he were to do something like that. > >>> > >>> Thanks > >>> Michael > >>> > >>> [0]: https://utxos.org/signals/ > >>> > >>> > >>> > >>> On Sun, Apr 21, 2024 at 12:05=E2=80=AFAM Ava Chow wrote: > >>>> > >>>> > >>>> On 04/20/2024 06:21 PM, Michael Folkson wrote: > >>>>> It is inevitable there will be a "revert war" unless they all have = to > >>>>> agree on merge decisions or communicate prior to merging. It is jus= t > a > >>>>> matter of time. Does for example Ordinal Numbers get a BIP number? = I > >>>>> suspect all the new BIP editors won't agree on that. > >>>> > >>>> Why do you think that a revert war is inevitable? > >>>> > >>>> The Bitcoin Core repo operates in a similar way - the maintainers ar= e > >>>> independent and work autonomously. The maintainers do not have to > agree > >>>> on merge decisions nor do they communicate prior to merging. If > there's > >>>> disagreement about a merge decision, we talk to each other about it > like > >>>> adults and come to a mutually agreeable resolution. I don't think > >>>> there's ever been a revert war in the history of Bitcoin. > >>>> > >>>> I would expect that when there is something that is likely to be > >>>> controversial or is ambiguous that it should be a BIP that they woul= d > >>>> then talk to each other about it. It doesn't have to be all or > nothing - > >>>> they can do most work without communicating, but when there's > questions > >>>> or ambiguity, then they communicate. > >>>> > >>>>> Who is to blame in a "revert war" if each editor is free to merge > >>>>> whatever pull request they like? The editor who merged it? Why shou= ld > >>>>> they be removed as an editor for merging a pull request when they > find > >>>>> out later a different editor disagreed with that merge decision and > >>>>> wants to revert the merge? > >>>> > >>>> A revert war would be someone merging a PR that reverts another, the= n > >>>> someone else (opening then) merging a PR that reverts that, and it > goes > >>>> back and forth. It would not be limited to PRs only. This would like= ly > >>>> be super obvious too that they are controversially merging things as= I > >>>> would be surprised if other BIP editors didn't comment on any of tho= se > >>>> actions, besides the fact that many people do also watch the BIPs > repo. > >>>> Regardless, the blame is on those who are doing the reverting, and > would > >>>> be both sides. > >>>> > >>>>> I'm even more concerned about future soft fork activation attempts. > >>>>> These don't necessarily need to be attempted via a Bitcoin Core > merged > >>>>> pull request hence the BIPs repo could be a key source of informati= on > >>>>> and guidance on this. > >>>> > >>>> This concern doesn't make any sense. There are already multiple soft > and > >>>> hard fork BIPs that are not active nor good ideas. A BIP does not ne= ed > >>>> to be a good idea. > >>>> > >>>>> I've seen Wladimir is contributing again to Core. Is there a plan t= o > >>>>> give him commit access again? > >>>> > >>>> It would have to be through the typical maintainer process, although= I > >>>> doubt that he even wants it. But that's completely orthogonal to the > >>>> BIPs repo discussion. > >>>> > >>>>> I'd be more comfortable with him > >>>>> overseeing things in the various repos under the Bitcoin Core > >>>>> (/bitcoin) GitHub org as it sounds like you don't really care if th= e > >>>>> BIPs repo degenerates into a free for all. > >>>> > >>>> I don't understand why you assume that. > >>>> > >>>> I've said this before, but if I see a revert war going on in the BIP= s > >>>> repo, I will remove those involved immediately and make a thread on > the > >>>> list to discuss what to do about them. But I doubt that's a scenario > >>>> that will actually come to pass. > >>>> > >>>> Ava > >>>> > >>>>> > >>>>> Thanks > >>>>> Michael > >>>>> > >>>>> On Sat, Apr 20, 2024 at 10:15=E2=80=AFPM 'Ava Chow' via Bitcoin Dev= elopment > >>>>> Mailing List wrote: > >>>>>> > >>>>>> On 04/20/2024 04:46 PM, Steve Lee wrote: > >>>>>>> Wasn't there evidence provided that Kanzure does not want this > >>>>>>> responsibility without being paid? > >>>>>> > >>>>>> I am not aware of that, and it hasn't come up when I've talked to > him > >>>>>> about being a BIPs editor. > >>>>>> > >>>>>>> I'm confused by this process that we don't even ask the people if > they > >>>>>>> want the responsibility? I think only Laolu has chimed in to > commit to it? > >>>>>> > >>>>>> Personally, I've spoken to all 5 privately and they've all > confirmed to > >>>>>> me that they are willing to be BIPs editors. Jonatack[1] and > Murch[2] > >>>>>> have also replied to this thread about this. > >>>>>> > >>>>>> Ava > >>>>>> > >>>>>> [1]: > >>>>>> > https://gnusha.org/pi/bitcoindev/83b69000-ca1e-4a58-90b5-114cb09ac0bbn@go= oglegroups.com/ > >>>>>> [2]: > >>>>>> > https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a-920b-32bd88d5e778@mur= ch.one/ > >>>>>> > >>>>>>> > >>>>>>> On Sat, Apr 20, 2024 at 12:30=E2=80=AFPM 'Ava Chow' via Bitcoin D= evelopment > >>>>>>> Mailing List >>>>>>> > wrote: > >>>>>>> > >>>>>>> Since we're now past the deadline of April 19th, I'd like > to inform > >>>>>>> everyone of what will happen on Monday. > >>>>>>> > >>>>>>> There has not been any actual objections to the nominees > nor have there > >>>>>>> been any suggestions on choosing a subset of them since my > last email. > >>>>>>> As such, there is rough consensus on adding Kanzure, Murch= , > Jonatack, > >>>>>>> Ruben, and Roasbeef as BIP editors, and they will be added > on Monday > >>>>>>> April 22nd. > >>>>>>> > >>>>>>> Ava > >>>>>>> > >>>>>>> On 04/16/2024 01:08 PM, 'Ava Chow' via Bitcoin Development > Mailing List > >>>>>>> wrote: > >>>>>>> > While I don't disagree that 5 or 6 people seems like a > lot to add at > >>>>>>> > once, it's not clear to me how we should decide which > subset of the > >>>>>>> > nominees should be added. As it is now, I have only see= n > an actual > >>>>>>> > objection to Kanzure and Ruben from /dev/fd0, and no > explicit > >>>>>>> objections > >>>>>>> > to anyone else. It seems like the vast majority of > people don't share > >>>>>>> > their concerns either as both Kanzure and Ruben continu= e > to be > >>>>>>> endorsed > >>>>>>> > by many others. > >>>>>>> > > >>>>>>> > Looking at the endorsements each candidate has received= , > the current > >>>>>>> > counts are: > >>>>>>> > * Kanzure - 17 for, 1 against > >>>>>>> > * Murch - 13 for > >>>>>>> > * Jonatack - 13 for > >>>>>>> > * Ruben - 12 for, 1 against > >>>>>>> > * Roasbeef - 9 for > >>>>>>> > * Michael Folkson - none > >>>>>>> > > >>>>>>> > However, I don't want this process to become a > popularity contest and > >>>>>>> > require some kind of formal voting. Rather I'd prefer > that this > >>>>>>> process > >>>>>>> > be something more like how Bitcoin Core maintainers are > added - by > >>>>>>> > achieving rough consensus. Without any explicit > objections to any of > >>>>>>> > these candidates, I'm inclined to move forward with > adding the 5 who > >>>>>>> > have received endorsements. Having to pick "winners" > from this list > >>>>>>> > seems like a quick way to stir up drama that I don't > think anyone > >>>>>>> really > >>>>>>> > wants to deal with. > >>>>>>> > > >>>>>>> > I do want to note that neither Kanzure, Ruben, nor > Roasbeef have > >>>>>>> posted > >>>>>>> > on this list that they are willing to be BIP editors. I > have > >>>>>>> reached out > >>>>>>> > to all 3 of them privately, and received responses from > Kanzure and > >>>>>>> > Ruben that indicate that they probably are willing, but > public > >>>>>>> > confirmation from them on this list would also be nice. > I have not > >>>>>>> > received a response from Roasbeef. > >>>>>>> > > >>>>>>> > Ava > >>>>>>> > > >>>>>>> > On 04/11/2024 10:22 AM, Sergi Delgado Segura wrote: > >>>>>>> >> > I would prefer having more (9+?) than less folks o= n > this > >>>>>>> task, so > >>>>>>> >> personal preferences are easily ignored and overwritte= n > by the group > >>>>>>> >> majority. > >>>>>>> >> > >>>>>>> >> I disagree with that, the more doesn't really the > better here. > >>>>>>> Having > >>>>>>> >> too many editors may result in a tragedy of the > commons, in > >>>>>>> which people > >>>>>>> >> just commit to the job because many others do, and the= y > do not > >>>>>>> end up > >>>>>>> >> doing as much because they expect others to do the it. > This does not > >>>>>>> >> only make the process look bad but may burnout the one= s > that end up > >>>>>>> >> doing the job, given their time commitment ends up > being too far > >>>>>>> from > >>>>>>> >> their expectations. > >>>>>>> >> > >>>>>>> >> I think being more moderate with the amount of people > is better, and > >>>>>>> >> gives us leeway in case the workload ends up being > excessive and > >>>>>>> we need > >>>>>>> >> to add more people (plus discourage people from joinin= g > and > >>>>>>> slacking off). > >>>>>>> >> > >>>>>>> >> I think 3 more people should be a good number to start > from. > >>>>>>> >> I'd personally vouch for Murch, Kanzure, and Ruben > based on > >>>>>>> their track > >>>>>>> >> record in the space > >>>>>>> >> > >>>>>>> >> On Tue, Apr 2, 2024 at 4:30=E2=80=AFPM nvk >>>>>>> > >>>>>>> >> >> > wrote: > >>>>>>> >> > >>>>>>> >> +1 for > >>>>>>> >> Kanzure > >>>>>>> >> RubenSomsen > >>>>>>> >> Seccour > >>>>>>> >> Jon Atack > >>>>>>> >> Roasbeef > >>>>>>> >> > >>>>>>> >> I would prefer having more (9+?) than less folks on > this task, so > >>>>>>> >> personal preferences are easily ignored and overwritte= n > by the group > >>>>>>> >> majority. > >>>>>>> >> > >>>>>>> >> BIPs were intended as a means to collect ideas, not > enforce ideas. > >>>>>>> >> > >>>>>>> >> I'd like to return to that. > >>>>>>> >> > >>>>>>> >> - NVK (temp gmail account) > >>>>>>> >> > >>>>>>> >> On Monday, April 1, 2024 at 5:16:54=E2=80=AFPM UT= C-4 David > A. > >>>>>>> Harding wrote: > >>>>>>> >> > >>>>>>> >> On 2024-03-28 10:04, Matt Corallo wrote: > >>>>>>> >> > Please provide justification rather than > simply > >>>>>>> saying "I > >>>>>>> >> like Bob!". > >>>>>>> >> > >>>>>>> >> Using only comments from the mailing list, th= e > >>>>>>> following appears > >>>>>>> >> to be > >>>>>>> >> the candidate list along with the current > support. > >>>>>>> Asterisks denote > >>>>>>> >> candidates who indicated their willingness to > accept > >>>>>>> the role. > >>>>>>> >> > >>>>>>> >> - 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] > >>>>>>> >> > >>>>>>> >> - Ruben Somsen, recommended by Ava Chow[1], > Chris > >>>>>>> Stewart[3], > >>>>>>> >> Michael > >>>>>>> >> Folkson[6], Antoine Riard[12], Murch[13], > Antoine > >>>>>>> Poinsot[15], John > >>>>>>> >> Carvalho[16] > >>>>>>> >> > >>>>>>> >> - 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] > >>>>>>> >> > >>>>>>> >> - 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] > >>>>>>> >> > >>>>>>> >> - Mark "Murch" Erhardt*, recommended by Micha= el > >>>>>>> Folkson[6], Keagan > >>>>>>> >> McClelland[8], Matt Corallo[10], Brandon > Black[11], Antoine > >>>>>>> >> Riard[12], > >>>>>>> >> Ava Chow[14] > >>>>>>> >> > >>>>>>> >> - Michael Folkson* > >>>>>>> >> > >>>>>>> >> 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". > >>>>>>> >> > >>>>>>> >> 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). > >>>>>>> >> > >>>>>>> >> - 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 > >>>>>>> >> > >>>>>>> >> 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. > >>>>>>> >> > >>>>>>> >> 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 somethin= g > that > >>>>>>> he's already > >>>>>>> >> doing, > >>>>>>> >> so I think there's an excellent fit of person > to role. > >>>>>>> >> > >>>>>>> >> -Dave > >>>>>>> >> > >>>>>>> >> [1] > >>>>>>> >> > >>>>>>> > https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8...@achow101.com/ > >>>>>>> < > https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8...@achow101.com/> < > https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8-ba1a-c9d97927551e@ach= ow101.com/ > < > https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8-ba1a-c9d97927551e@ach= ow101.com/ > >> > >>>>>>> >> [2] > >>>>>>> >> > >>>>>>> > https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106...@dashjr.org/ > >>>>>>> < > https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106...@dashjr.org/> > >>>>>>> < > https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106-b843-c1ff8f8a62a3@das= hjr.org/ > < > https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106-b843-c1ff8f8a62a3@das= hjr.org/ > >> > >>>>>>> >> [3] > >>>>>>> >> > >>>>>>> > https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a...@googlegroups.com/ = < > https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a...@googlegroups.com/> > < > https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n@go= oglegroups.com/ > < > https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n@go= oglegroups.com/ > >> > >>>>>>> >> [4] > >>>>>>> >> > >>>>>>> > https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.com/ = < > https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.com/> > < > https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333-fd28-bdd55899b713@net= purgatory.com/ > < > https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333-fd28-bdd55899b713@net= purgatory.com/ > >> > >>>>>>> >> [5] > >>>>>>> >> > >>>>>>> > https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.com/ = < > https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.com/> > < > https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36-be81-7c3719157fabn@go= oglegroups.com/ > < > https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36-be81-7c3719157fabn@go= oglegroups.com/ > >> > >>>>>>> >> [6] > >>>>>>> >> > >>>>>>> > https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.com/ = < > https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.com/> > < > https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2-a787-639a3564d006n@go= oglegroups.com/ > < > https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2-a787-639a3564d006n@go= oglegroups.com/ > >> > >>>>>>> >> [7] > >>>>>>> >> > >>>>>>> > https://gnusha.org/pi/bitcoindev/846b668f-8386-4869...@googlegroups.com/ = < > https://gnusha.org/pi/bitcoindev/846b668f-8386-4869...@googlegroups.com/> > < > https://gnusha.org/pi/bitcoindev/846b668f-8386-4869-a3b1-55d346efbea1n@go= oglegroups.com/ > < > https://gnusha.org/pi/bitcoindev/846b668f-8386-4869-a3b1-55d346efbea1n@go= oglegroups.com/ > >> > >>>>>>> >> [8] > >>>>>>> >> > >>>>>>> > https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEazRA= 5...@mail.gmail.com/ > < > https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEazRA= 5...@mail.gmail.com/> > < > https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEazRA= 5nVw9siYCPj4A@mail.gmail.com/ > < > https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEazRA= 5nVw9siYCPj4A@mail.gmail.com/ > >> > >>>>>>> >> [9] > >>>>>>> https://gnusha.org/pi/bitcoindev/ZgePPvbf...@petertodd.org= / > >>>>>>> < > https://gnusha.org/pi/bitcoindev/ZgePPvbf...@petertodd.org/> > >>>>>>> >> > >>>>>>> < > https://gnusha.org/pi/bitcoindev/ZgePPvbfrr4wZG7k@petertodd.org/ > >>>>>>> < > https://gnusha.org/pi/bitcoindev/ZgePPvbfrr4wZG7k@petertodd.org/>> > >>>>>>> >> [10] > >>>>>>> >> > >>>>>>> > https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5...@mattcorallo.com/ < > https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5...@mattcorallo.com/> = < > https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5-86e2-7ba0336a9bf2@mat= tcorallo.com/ > < > https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5-86e2-7ba0336a9bf2@mat= tcorallo.com/ > >> > >>>>>>> >> [11] > >>>>>>> https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg69V@console/ > >>>>>>> > > >>>>>>> >> > >>>>>>> >>>>>>> >> > >>>>>>> >> [12] > >>>>>>> >> > >>>>>>> > https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+E...@mail.gmail.= com/ > < > https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+E...@mail.gmail.= com/> > < > https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+EKMCP5oEbHSKSXpq= 0VKVBhJLhrw@mail.gmail.com/ > < > https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+EKMCP5oEbHSKSXpq= 0VKVBhJLhrw@mail.gmail.com/ > >> > >>>>>>> >> [13] > >>>>>>> >> > >>>>>>> > https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a...@murch.one/ > >>>>>>> < > https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a...@murch.one/> > >>>>>>> < > https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a-920b-32bd88d5e778@mur= ch.one/ > < > https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a-920b-32bd88d5e778@mur= ch.one/ > >> > >>>>>>> >> [14] > >>>>>>> >> > >>>>>>> > https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f...@achow101.com/ > >>>>>>> < > https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f...@achow101.com/> < > https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f-866d-c555b80b0644@ach= ow101.com/ > < > https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f-866d-c555b80b0644@ach= ow101.com/ > >> > >>>>>>> >> [15] > >>>>>>> >> > >>>>>>> > https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh= 7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@prot= onmail.com/ > < > https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh= 7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@prot= onmail.com/> > < > https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh= 7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@prot= onmail.com/ > < > https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh= 7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@prot= onmail.com/ > >> > >>>>>>> >> [16] > >>>>>>> >> > >>>>>>> > https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552...@googlegroups.com/ = < > https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552...@googlegroups.com/> > < > https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552-88ca-11b9ed340661n@go= oglegroups.com/ > < > https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552-88ca-11b9ed340661n@go= oglegroups.com/ > >> > >>>>>>> >> [17] > >>>>>>> >> > >>>>>>> > https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qr= st+...@mail.gmail.com/ > < > https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qr= st+...@mail.gmail.com/> > < > https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qr= st+nmyypaedYZgg@mail.gmail.com/ > < > https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qr= st+nmyypaedYZgg@mail.gmail.com/ > >> > >>>>>>> >> > >>>>>>> >> -- > >>>>>>> >> 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/7b4e2223-0b96-4ca0-a441-aebc= fc7b0bben%40googlegroups.com > < > https://groups.google.com/d/msgid/bitcoindev/7b4e2223-0b96-4ca0-a441-aebc= fc7b0bben%40googlegroups.com> > < > https://groups.google.com/d/msgid/bitcoindev/7b4e2223-0b96-4ca0-a441-aebc= fc7b0bben%40googlegroups.com?utm_medium=3Demail&utm_source=3Dfooter > < > https://groups.google.com/d/msgid/bitcoindev/7b4e2223-0b96-4ca0-a441-aebc= fc7b0bben%40googlegroups.com?utm_medium=3Demail&utm_source=3Dfooter > >>. > >>>>>>> >> > >>>>>>> >> > >>>>>>> >> > >>>>>>> >> -- > >>>>>>> >> Sergi. > >>>>>>> >> > >>>>>>> >> -- > >>>>>>> >> You received this message because you are subscribed t= o > 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/CAEYHFxV_8_Jw61tysL_cV_xiXBc= RyA3e%3DCGHGuSCgm%2B-4WxT9w%40mail.gmail.com > < > https://groups.google.com/d/msgid/bitcoindev/CAEYHFxV_8_Jw61tysL_cV_xiXBc= RyA3e%3DCGHGuSCgm%2B-4WxT9w%40mail.gmail.com> > < > https://groups.google.com/d/msgid/bitcoindev/CAEYHFxV_8_Jw61tysL_cV_xiXBc= RyA3e%3DCGHGuSCgm%2B-4WxT9w%40mail.gmail.com?utm_medium=3Demail&utm_source= =3Dfooter > < > https://groups.google.com/d/msgid/bitcoindev/CAEYHFxV_8_Jw61tysL_cV_xiXBc= RyA3e%3DCGHGuSCgm%2B-4WxT9w%40mail.gmail.com?utm_medium=3Demail&utm_source= =3Dfooter > >>. > >>>>>>> > > >>>>>>> > -- > >>>>>>> > 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 email= s > 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/fb52ccb5-9942-4db8-b880-3c06= ebc47cd1%40achow101.com > < > https://groups.google.com/d/msgid/bitcoindev/fb52ccb5-9942-4db8-b880-3c06= ebc47cd1%40achow101.com > >. > >>>>>>> > >>>>>>> -- > >>>>>>> You received this message because you are subscribed to th= e > 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/070755a0-10e9-4903-9524-dd8e= f98c1c8b%40achow101.com > < > https://groups.google.com/d/msgid/bitcoindev/070755a0-10e9-4903-9524-dd8e= f98c1c8b%40achow101.com > >. > >>>>>>> > >>>>>> > >>>>>> -- > >>>>>> 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/0d4d85e3-9fbb-4bd4-af0f-9222= 5e699b63%40achow101.com > . > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> Michael Folkson > >>>>> Personal email: michaelfolkson@gmail.com > >>>> > >>> > >>> > >>> -- > >>> Michael Folkson > >>> Personal email: michaelfolkson@gmail.com > >> > > > > > > -- > > Michael Folkson > > Personal email: michaelfolkson@gmail.com > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Bitcoin Development Mailing List" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/bitcoindev/cuMZ77KEQAA/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > bitcoindev+unsubscribe@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/bitcoindev/84bb3ca1-a18e-48c8-a934-6fce= f5470a36%40achow101.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/CALZpt%2BHdRQEewsy08ezcGU38Gr0N%2BCwYgRr1CbRNsDGEM_UThQ%40mail.g= mail.com. --000000000000dd1aa00616a1703c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> There has not been any actual objections to the nomin= ees nor have there=C2=A0=
> been any suggestions on choosing a subset of them since my last em= ail.=C2=A0
> As su= ch, there is rough consensus on adding Kanzure, Murch, Jonatack,=C2=A0
> Ruben, and Roasbeef = as BIP editors, and they will be added on Monday=C2=A0
> April 22nd.

A= CK.

Beyond that, I'll stick to my mail of the = 1st April and I won't comment further on the subject of nominating new = BIP editors.
If anyone has thoughts on how to improve the BIP pro= cess for the _future_, I think real-or-random started a new thread called &= quot;Time for an update to BIP2?".
Anyone can express themse= lves there and then start to champion a new BIP of type "process"= .

Best,
Antoine

Le=C2=A0dim. 21 avr= . 2024 =C3=A0=C2=A020:08, 'Ava Chow' via Bitcoin Development Mailin= g List <bitcoindev@google= groups.com> a =C3=A9crit=C2=A0:
On 04/21/2= 024 01:57 PM, Michael Folkson wrote:
> So once a BIP number is allocated (or before) the BIP author can write=
> whatever they like on that BIP? Including false and misleading
> statements? And the BIP editors have to merge it as long as it meets > formatting requirements?

I did not say that they can write anything, do not put words in my
mouth. Modifications to a BIP are held to the same standard as when it
is initially proposed. This standard is largely about formatting, but
also about keeping BIPs as actual technical specifications. So long as
the BIP after those modifications meet those requirements, then BIP
editors should merge them.

> A misleading statement like "This soft fork will definitely activ= ate
> at block X as it has been merged into implementation Y. It hasn't = been
> merged into Bitcoin Core yet but Bitcoin Core will merge the soft fork=
> after the activation"

BIPs are specifications. They are not blog posts. They are not the place for opining about whether or not something will activate. Such
statements would be off topic for a BIP and do not meet the standard for merging, so no, I do not think that should be merged, and I do not think any of the proposed BIP editors would merge such a PR.

>
> This is a step change from before. If we aren't relying on *any* > judgment then there might as well be 100 BIP editors. Because the
> editors aren't doing anything, each BIP author (or champion) has t= otal
> license to write whatever they like on their BIP.
>
>> They are not arbiters of what is activated on Bitcoin. They are no= t gatekeepers of soft forks.
>
> Of course not. The BIP editors do not decide what is activated on
> Bitcoin. But they are gatekeepers on ensuring BIPs are high quality > and don't include false and misleading statements. Because false a= nd
> misleading statements can impact the evolution of an activation
> process.
>
> I tried. Based on your perspective all we need is one malicious BIP > author (or champion) and they'll make the entire BIP process a jok= e
> and the BIP editors won't be able to do anything.

You are being deliberately obtuse and strawmanning. I did not say that
the BIP editors won't be able to do anything; I did not say that that a=
BIP author can put whatever they want once they get a BIP number.

I suggest that you read the BIP process thread split from this one for
opinions on how to refine the BIPs process to make it clearer as to what BIP editors should be merging.

Frankly, I don't understand what it is your are arguing for or trying t= o
achieve. You make absurd claims, use strawman arguments, and throw out
whataboutisms. This all seems to me to be concern trolling, and as such, I see no reason to continue responding to you.

Ava

>
> Michael
>
>
>
> On Sun, Apr 21, 2024 at 5:39=E2=80=AFPM Ava Chow <lists@achow101.com> wrote: >>
>> You are misunderstanding the role of BIP editors. They are not arb= iters
>> of what is activated on Bitcoin. They are not gatekeepers of soft = forks.
>> If a BIP author proposes or agrees with a change to their BIP and = those
>> changes are formatted correctly, it is not the BIP editors' ri= ghts nor
>> responsibilities to refuse to merge that change. As with Bitcoin C= ore
>> maintainers, BIP editing is a largely janitorial role.
>>
>> Just because something is a BIP does not mean it is a good idea. J= ust
>> because a BIP specifying a fork contains deployment parameters doe= s not
>> mean it will actually be deployed. There are several BIPs for both= hard
>> and soft forks that are rejected or withdrawn that have deployment=
>> parameters.
>>
>> Furthermore, for myself, I would actually prefer that contentious = soft
>> forks for which some people are legitimately attempting to activat= e have
>> their deployment parameters be specified in a/the BIP. Having comp= eting
>> activation parameters in different BIPs is preferable over the
>> documentation being spread around in many different places. It mak= es it
>> much easier for implementations to inform users what they've a= ctually
>> implemented so that users can make a more informed decision.
>>
>> On 04/21/2024 07:43 AM, Michael Folkson wrote:
>>> Ava
>>>
>>> Thanks for the detailed response, I appreciate the insight. >>>
>>>>> I'm even more concerned about future soft fork act= ivation attempts.
>>>>> These don't necessarily need to be attempted via a= Bitcoin Core merged
>>>>> pull request hence the BIPs repo could be a key source= of information
>>>>> and guidance on this.
>>>
>>>> This concern doesn't make any sense. There are already= multiple soft and
>>>> hard fork BIPs that are not active nor good ideas. A BIP d= oes not need
>>>> to be a good idea.
>>>
>>> I would hope that a contentious soft fork and activation param= s for
>>> that contentious soft fork would not be merged into the Bitcoi= n Core
>>> codebase and up until now it hasn't been. I would hope all= the Bitcoin
>>> Core maintainers understand that even if they personally think= a soft
>>> fork is a good idea (apparently there is nothing to stop them = merging
>>> it without discussing it with the other maintainers) that they=
>>> shouldn't independently merge it if it is contentious.
>>>
>>> Similarly I would hope that all BIP editors would be careful a= bout
>>> what information gets merged around soft fork activation *atte= mpts*
>>> whether that be activation details on a particular soft fork B= IP or on
>>> a separate activation BIP. With Taproot there were very strong=
>>> disagreements over activation parameters for a non-contentious= soft
>>> fork. It would be much messier for a contentious soft fork act= ivation
>>> attempt. I'm not sure all these new BIP editors understand= that or
>>> would perhaps even agree with that. For example Laolu is liste= d as a
>>> supporter of a CTV activation attempt back in 2022 [0] which w= as
>>> clearly contentious. That doesn't inspire me with confiden= ce that as
>>> soon as he is a BIP editor he won't start merging details = on
>>> contentious soft fork activation attempts in BIPs and merging = that
>>> soft fork in say btcd. He would need to be removed as a BIP ed= itor if
>>> he were to do something like that.
>>>
>>> Thanks
>>> Michael
>>>
>>> [0]: https://utxos.org/signals/
>>>
>>>
>>>
>>> On Sun, Apr 21, 2024 at 12:05=E2=80=AFAM Ava Chow <lists@achow101.com>= wrote:
>>>>
>>>>
>>>> On 04/20/2024 06:21 PM, Michael Folkson wrote:
>>>>> It is inevitable there will be a "revert war"= ; unless they all have to
>>>>> agree on merge decisions or communicate prior to mergi= ng. It is just a
>>>>> matter of time. Does for example Ordinal Numbers get a= BIP number? I
>>>>> suspect all the new BIP editors won't agree on tha= t.
>>>>
>>>> Why do you think that a revert war is inevitable?
>>>>
>>>> The Bitcoin Core repo operates in a similar way - the main= tainers are
>>>> independent and work autonomously. The maintainers do not = have to agree
>>>> on merge decisions nor do they communicate prior to mergin= g. If there's
>>>> disagreement about a merge decision, we talk to each other= about it like
>>>> adults and come to a mutually agreeable resolution. I don&= #39;t think
>>>> there's ever been a revert war in the history of Bitco= in.
>>>>
>>>> I would expect that when there is something that is likely= to be
>>>> controversial or is ambiguous that it should be a BIP that= they would
>>>> then talk to each other about it. It doesn't have to b= e all or nothing -
>>>> they can do most work without communicating, but when ther= e's questions
>>>> or ambiguity, then they communicate.
>>>>
>>>>> Who is to blame in a "revert war" if each ed= itor is free to merge
>>>>> whatever pull request they like? The editor who merged= it? Why should
>>>>> they be removed as an editor for merging a pull reques= t when they find
>>>>> out later a different editor disagreed with that merge= decision and
>>>>> wants to revert the merge?
>>>>
>>>> A revert war would be someone merging a PR that reverts an= other, then
>>>> someone else (opening then) merging a PR that reverts that= , and it goes
>>>> back and forth. It would not be limited to PRs only. This = would likely
>>>> be super obvious too that they are controversially merging= things as I
>>>> would be surprised if other BIP editors didn't comment= on any of those
>>>> actions, besides the fact that many people do also watch t= he BIPs repo.
>>>> Regardless, the blame is on those who are doing the revert= ing, and would
>>>> be both sides.
>>>>
>>>>> I'm even more concerned about future soft fork act= ivation attempts.
>>>>> These don't necessarily need to be attempted via a= Bitcoin Core merged
>>>>> pull request hence the BIPs repo could be a key source= of information
>>>>> and guidance on this.
>>>>
>>>> This concern doesn't make any sense. There are already= multiple soft and
>>>> hard fork BIPs that are not active nor good ideas. A BIP d= oes not need
>>>> to be a good idea.
>>>>
>>>>> I've seen Wladimir is contributing again to Core. = Is there a plan to
>>>>> give him commit access again?
>>>>
>>>> It would have to be through the typical maintainer process= , although I
>>>> doubt that he even wants it. But that's completely ort= hogonal to the
>>>> BIPs repo discussion.
>>>>
>>>>> I'd be more comfortable with him
>>>>> overseeing things in the various repos under the Bitco= in Core
>>>>> (/bitcoin) GitHub org as it sounds like you don't = really care if the
>>>>> BIPs repo degenerates into a free for all.
>>>>
>>>> I don't understand why you assume that.
>>>>
>>>> I've said this before, but if I see a revert war going= on in the BIPs
>>>> repo, I will remove those involved immediately and make a = thread on the
>>>> list to discuss what to do about them. But I doubt that= 9;s a scenario
>>>> that will actually come to pass.
>>>>
>>>> Ava
>>>>
>>>>>
>>>>> Thanks
>>>>> Michael
>>>>>
>>>>> On Sat, Apr 20, 2024 at 10:15=E2=80=AFPM 'Ava Chow= ' via Bitcoin Development
>>>>> Mailing List <bitcoindev@googlegroups.com> wrote:
>>>>>>
>>>>>> On 04/20/2024 04:46 PM, Steve Lee wrote:
>>>>>>> Wasn't there evidence provided that Kanzur= e does not want this
>>>>>>> responsibility without being paid?
>>>>>>
>>>>>> I am not aware of that, and it hasn't come up = when I've talked to him
>>>>>> about being a BIPs editor.
>>>>>>
>>>>>>> I'm confused by this process that we don&#= 39;t even ask the people if they
>>>>>>> want the responsibility? I think only Laolu ha= s chimed in to commit to it?
>>>>>>
>>>>>> Personally, I've spoken to all 5 privately and= they've all confirmed to
>>>>>> me that they are willing to be BIPs editors. Jonat= ack[1] and Murch[2]
>>>>>> have also replied to this thread about this.
>>>>>>
>>>>>> Ava
>>>>>>
>>>>>> [1]:
>>>>>> https://gnusha.org/pi/bitcoindev/83b69000-ca1e-4a58-90b5-114cb= 09ac0bbn@googlegroups.com/
>>>>>> [2]:
>>>>>> https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a-920b-32bd88d5e778@= murch.one/
>>>>>>
>>>>>>>
>>>>>>> On Sat, Apr 20, 2024 at 12:30=E2=80=AFPM '= Ava Chow' via Bitcoin Development
>>>>>>> Mailing List <bitcoindev@googlegroups.com
>>>>>>> <mailto:bitcoindev@googlegroups.com>> wrote= :
>>>>>>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Since we're now= past the deadline of April 19th, I'd like to inform
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 everyone of what wi= ll happen on Monday.
>>>>>>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 There has not been = any actual objections to the nominees nor have there
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 been any suggestion= s on choosing a subset of them since my last email.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 As such, there is r= ough consensus on adding Kanzure, Murch, Jonatack,
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Ruben, and Roasbeef= as BIP editors, and they will be added on Monday
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 April 22nd.
>>>>>>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Ava
>>>>>>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 On 04/16/2024 01:08= PM, 'Ava Chow' via Bitcoin Development Mailing List
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 wrote:
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> While I = don't disagree that 5 or 6 people seems like a lot to add at
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> once, it= 's not clear to me how we should decide which subset of the
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> nominees= should be added. As it is now, I have only seen an actual
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> objectio= n to Kanzure and Ruben from /dev/fd0, and no explicit
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 objections
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> to anyon= e else. It seems like the vast majority of people don't share
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> their co= ncerns either as both Kanzure and Ruben continue to be
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 endorsed
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> by many = others.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> Looking = at the endorsements each candidate has received, the current
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> counts a= re:
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> * Kanzur= e - 17 for, 1 against
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> * Murch = - 13 for
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> * Jonata= ck - 13 for
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> * Ruben = - 12 for, 1 against
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> * Roasbe= ef - 9 for
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> * Michae= l Folkson - none
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> However,= I don't want this process to become a popularity contest and
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> require = some kind of formal voting. Rather I'd prefer that this
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 process
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> be somet= hing more like how Bitcoin Core maintainers are added - by
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> achievin= g rough consensus. Without any explicit objections to any of
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> these ca= ndidates, I'm inclined to move forward with adding the 5 who
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> have rec= eived endorsements. Having to pick "winners" from this list
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> seems li= ke a quick way to stir up drama that I don't think anyone
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 really
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> wants to= deal with.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> I do wan= t to note that neither Kanzure, Ruben, nor Roasbeef have
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 posted
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> on this = list that they are willing to be BIP editors. I have
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 reached out
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> to all 3= of them privately, and received responses from Kanzure and
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> Ruben th= at indicate that they probably are willing, but public
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> confirma= tion from them on this list would also be nice. I have not
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> received= a response from Roasbeef.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> Ava
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> On 04/11= /2024 10:22 AM, Sergi Delgado Segura wrote:
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0> I would prefer having more (9+?) than less folks on this
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 task, so
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> pers= onal preferences are easily ignored and overwritten by the group
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> majo= rity.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> I di= sagree with that, the more doesn't really the better here.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Having
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> too = many editors may result in a tragedy of the commons, in
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 which people
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> just= commit to the job because many others do, and they do not
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 end up
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> doin= g as much because they expect others to do the it. This does not
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> only= make the process look bad but may burnout the ones that end up
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> doin= g the job, given their time commitment ends up being too far
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 from
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> thei= r expectations.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> I th= ink being more moderate with the amount of people is better, and
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> give= s us leeway in case the workload ends up being excessive and
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 we need
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> to a= dd more people (plus discourage people from joining and
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 slacking off).
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> I th= ink 3 more people should be a good number to start from.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> I= 9;d personally vouch for Murch, Kanzure, and Ruben based on
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 their track
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> reco= rd in the space
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> On T= ue, Apr 2, 2024 at 4:30=E2=80=AFPM nvk <rdlfnvk@gmail.com
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <mailto:rdlfnvk@gmail.com> >>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> <= mailto:rdlfnvk@gmail= .com <mailto:= rdlfnvk@gmail.com>>> wrote:
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> +1 f= or
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> Kanz= ure
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> Rube= nSomsen
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> Secc= our
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> Jon = Atack
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> Roas= beef
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> I wo= uld prefer having more (9+?) than less folks on this task, so
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> pers= onal preferences are easily ignored and overwritten by the group
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> majo= rity.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> BIPs= were intended as a means to collect ideas, not enforce ideas.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> I= 9;d like to return to that.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> - NV= K (temp gmail account)
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 On Monday, April 1, 2024 at 5:16:54=E2=80=AFPM UTC-4 Davi= d A.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Harding wrote:
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 On 2024-03-28 10:04, Matt Corallo wrote: >>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> Please provide justification rat= her than simply
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 saying "I
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 like Bob!".
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Using only comments from the mailing list, = the
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 following appears >>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 to be
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 the candidate list along with the current s= upport.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Asterisks denote >>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 candidates who indicated their willingness = to accept
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 the role.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - Bryan "Kanzure" Bishop, recomme= nded by Ava Chow[1], Chris
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Stewart[3],
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Michael Folkson[6], Peter Todd[9], Matt Cor= allo[10],
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Brandon
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Black[11],
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Antoine Riard[12], Murch[13], Antoine Poins= ot[15], John
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Carvalho[16]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - Ruben Somsen, recommended by Ava Chow[1],= Chris
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Stewart[3],
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Michael
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Folkson[6], Antoine Riard[12], Murch[13], A= ntoine
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Poinsot[15], John >>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Carvalho[16]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - Jon Atack*, recommended by Luke Dashjr[2]= , Chris
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Stewart[3],
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /dev/fd0[5][7],
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Brandon Black[11], Antoine Riard[12], Ava C= how[14], John
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Carvalho[16]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - Olaoluwa "Roasbeef" Osuntokun, = recommended by Chris
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Stewart[3], John
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 C. Vernaleo[4], /dev/fd0[5][7], Keagan McCl= elland[8],
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Antoine
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Riard[12], Ava Chow[14]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - Mark "Murch" Erhardt*, recommen= ded by Michael
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Folkson[6], Keagan<= br> >>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 McClelland[8], Matt Corallo[10], Brandon Bl= ack[11], Antoine
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Riard[12],
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Ava Chow[14]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - Michael Folkson*
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Note: Luke Dashjr proposed[17] Seccour and = Greg Tonoski for
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 "non-dev
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 triaging", Tonoski proposed himself[18= ] for "BIP
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 editor", and >>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Antoine
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Riard[12] proposed Seccour for "decent= ralized PM".
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 I searched the BIPs repo by commenter to se= e if any of
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 the above
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 candidates had been especially active there= , which is
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 listed
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 below as:
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 total PRs they commented on (number still o= pen/number
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 closed).
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - 21 (1/20) commenter:kanzure
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - 3 (2/1) commenter:rubensomsen
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - 15 (0/15) commenter:jonatack
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - 18 (2/16) commenter:roasbeef
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - 10 (6/4) commenter:Murchandamus
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - 57 (6/51) commenter:michaelfolkson
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 I'll also note that Osuntokun is the on= ly member of the
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 set to
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 have a
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 merged BIP that they co-authored, although = I believe
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 there are
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 far-along
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 draft BIPs for both Murch (terminology) and= Somsen (Silent
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Payments). I
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 don't think this should be a requiremen= t, but I do think it
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 demonstrates
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 familiarity with the process.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Speaking only for myself, I think all of th= e candidates
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 above with
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 multiple recommendations from other communi= ty
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 participants are >>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 fully
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 qualified for the role, so I'll only pr= ovide a detailed
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 justification
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 for the person who would be my first pick: = Murch is not
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 only a
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 longstanding and broadly liked Bitcoin cont= ributor, but
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 (as Corallo
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 mentioned) he has worked on standardizing t= erminology
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 through a
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 draft
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 BIP. In addition, he provided an extremely = detailed
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 review of
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 all 300
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 pages of a draft of Mastering Bitcoin (3rd = edition) and has
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 reviewed
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 drafts of over 200 weekly Optech newsletter= s, in both cases
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 significantly improving the accuracy and >>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 comprehensibility o= f the
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 documentation. To me, that seems very simil= ar to the
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 work we'd
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ask him
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 to perform as a BIPs editor and it's so= mething that
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 he's already >>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 doing,
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 so I think there's an excellent fit of = person to role.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -Dave
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [1]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8= ...@achow101.com/
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <https://gnusha.org/pi/bitcoindev/2092f7ff-4860-= 47f8...@achow101.com/> <https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8-ba1a-c= 9d97927551e@achow101.com/ <https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8-ba1a-c= 9d97927551e@achow101.com/>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [2]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106..= .@dashjr.org/
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-41= 06...@dashjr.org/>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <https://gnusha.org/pi/bitcoindev/9= 288df7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org/ <https://gnusha.org/pi/bitcoindev/9288d= f7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org/>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [3]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-= 4f1a...@googlegroups.com/ <https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a...@googlegroups.c= om/> <https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n@= googlegroups.com/ <https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a-8fd6-cddc= 46f129a2n@googlegroups.com/>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [4]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://gnusha.org/pi/bitcoindev/84309c3f-e848-= d333...@netpurgatory.com/ <https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.c= om/> <https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333-fd28-bdd55899b713@ne= tpurgatory.com/ <https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333-fd28-bdd558= 99b713@netpurgatory.com/>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [5]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-= 4a36...@googlegroups.com/ <https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.c= om/> <https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36-be81-7c3719157fabn@= googlegroups.com/ <https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36-be81-7c37= 19157fabn@googlegroups.com/>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [6]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://gnusha.org/pi/bitcoindev/a116fba3-5948-= 48d2...@googlegroups.com/ <https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.c= om/> <https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2-a787-639a3564d006n@= googlegroups.com/ <https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2-a787-639a= 3564d006n@googlegroups.com/>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [7]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://gnusha.org/pi/bitcoindev/846b668f-8386-= 4869...@googlegroups.com/ <https://gnusha.org/pi/bitcoindev/846b668f-8386-4869...@googlegroups.c= om/> <https://gnusha.org/pi/bitcoindev/846b668f-8386-4869-a3b1-55d346efbea1n@= googlegroups.com/ <https://gnusha.org/pi/bitcoindev/846b668f-8386-4869-a3b1-55d3= 46efbea1n@googlegroups.com/>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [8]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://gnusha.org/pi/bitc= oindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEazRA5...@mail.gmail.com/ <= ;https:= //gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEazRA5...@mai= l.gmail.com/> <https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7= YRS110ut8tX=3DwruqgLEazRA5nVw9siYCPj4A@mail.gmail.com/ <https://gn= usha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEazRA5nVw9siYCPj4= A@mail.gmail.com/>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [9]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://gnusha.org/pi/bitcoindev/ZgePPvbf...@petertodd.org/<= /a>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <https://gnusha.org/pi/bitcoindev/ZgePPvbf...@petertodd.o= rg/>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <https://gnusha.org/pi/bitcoindev/ZgePPvbfrr4wZG7k@p= etertodd.org/
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <https://gnusha.org/pi/bitcoindev/ZgePPvbfrr4wZG7k@p= etertodd.org/>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [10]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://gnusha.org/pi/bitcoindev/f9435999-42df-4= 6b5...@mattcorallo.com/ <https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5...@mattcorallo.com/<= /a>> <ht= tps://gnusha.org/pi/bitcoindev/f9435999-42df-46b5-86e2-7ba0336a9bf2@mattcor= allo.com/ <https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5-86e2-7ba0336a9bf2@m= attcorallo.com/>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [11]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg69V@console/
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg69V@console= />
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg69V@console= /
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg69V@console= />>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [12]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://gnusha.org/pi/bitcoindev/CALZpt+E= 8DohYEJ9aO+FiF6+E...@mail.gmail.com/ <https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+F= iF6+E...@mail.gmail.com/> <https://gnusha.org/pi/bitcoindev/CALZp= t+E8DohYEJ9aO+FiF6+EKMCP5oEbHSKSXpq0VKVBhJLhrw@mail.gmail.com/ <http= s://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+EKMCP5oEbHSKSXpq0VKVBh= JLhrw@mail.gmail.com/>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [13]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a...= @murch.one/
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441= a...@murch.one/>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <https://gnusha.org/pi/bitcoindev/53= a0015c-b76a-441a-920b-32bd88d5e778@murch.one/ <https://gnusha.org/pi/bitcoindev/53a0015c= -b76a-441a-920b-32bd88d5e778@murch.one/>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [14]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f= ...@achow101.com/
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <https://gnusha.org/pi/bitcoindev/ae482890-bce3-= 468f...@achow101.com/> <https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f-866d-c= 555b80b0644@achow101.com/ <https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f-866d-c= 555b80b0644@achow101.com/>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [15]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://gnusha.org/pi/bitcoindev/pp= BS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZW= awf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@protonmail.com/ <https://gnusha.org/pi/bitcoindev/= ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-U= ZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@protonmail.com/> <https://gnusha.org/pi/bitco= indev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh7692AUDw2TojfvCqvcvlmsy9E69qf= WMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@protonmail.com/ <https://gnusha.org/pi/b= itcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh7692AUDw2TojfvCqvcvlmsy9E= 69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@protonmail.com/>> >>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [16]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://gnusha.org/pi/bitcoindev/ad284018-e99c-= 4552...@googlegroups.com/ <https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552...@googlegroups.c= om/> <https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552-88ca-11b9ed340661n@= googlegroups.com/ <https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552-88ca-11b9= ed340661n@googlegroups.com/>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [17]
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://gnusha.org/pi/bi= tcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qrst+...@mail.gmail.com/= <= https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qrst= +...@mail.gmail.com/> <https://gnusha.org/pi/bitcoindev/CAMHH= ROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qrst+nmyypaedYZgg@mail.gmail.com/ <= https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMv= d9Qrst+nmyypaedYZgg@mail.gmail.com/>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 --
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 You received this message because you are subscribed to t= he
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Google
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 Groups "Bitcoin Development Mailing List" group= .
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 To unsubscribe from this group and stop receiving emails<= br> >>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 from it,
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 send an email to bitcoindev+unsubscribe@googlegroups.= com
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <mailto:b= itcoindev%2Bunsubscribe@googlegroups.com>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 <mailto:bitcoindev+unsubscribe@googlegroups.com
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <mailto:b= itcoindev%2Bunsubscribe@googlegroups.com>>.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>=C2= =A0 =C2=A0 =C2=A0 To view this discussion on the web visit
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://groups.goo= gle.com/d/msgid/bitcoindev/7b4e2223-0b96-4ca0-a441-aebcfc7b0bben%40googlegr= oups.com <https://groups.google.com/d/msgid/bitcoindev/7b4e2223-0b9= 6-4ca0-a441-aebcfc7b0bben%40googlegroups.com> <https://groups.google.com/d/msgid/bitcoindev/7b4e= 2223-0b96-4ca0-a441-aebcfc7b0bben%40googlegroups.com?utm_medium=3Demail&= ;utm_source=3Dfooter <ht= tps://groups.google.com/d/msgid/bitcoindev/7b4e2223-0b96-4ca0-a441-aebcfc7b= 0bben%40googlegroups.com?utm_medium=3Demail&utm_source=3Dfooter>= >.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> -- >>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> Serg= i.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> -- >>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> You = received this message because you are subscribed to the Google
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> Grou= ps "Bitcoin Development Mailing List" group.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> To u= nsubscribe from this group and stop receiving emails from
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 it, send
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> an e= mail to bitcoindev+unsubscribe@googlegroups.com
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <mailto:b= itcoindev%2Bunsubscribe@googlegroups.com>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> <= mailto:bitcoindev+unsubscribe@googlegroups.com
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <mailto:b= itcoindev%2Bunsubscribe@googlegroups.com>>.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>> To v= iew this discussion on the web visit
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 ht= tps://groups.google.com/d/msgid/bitcoindev/CAEYHFxV_8_Jw61tysL_cV_xiXBcRyA3= e%3DCGHGuSCgm%2B-4WxT9w%40mail.gmail.com <https://g= roups.google.com/d/msgid/bitcoindev/CAEYHFxV_8_Jw61tysL_cV_xiXBcRyA3e%3DCGH= GuSCgm%2B-4WxT9w%40mail.gmail.com> <https://groups.google.com/d/msgid/bitcoindev= /CAEYHFxV_8_Jw61tysL_cV_xiXBcRyA3e%3DCGHGuSCgm%2B-4WxT9w%40mail.gmail.com?u= tm_medium=3Demail&utm_source=3Dfooter <https://groups.google.com/d/msgid/bitcoi= ndev/CAEYHFxV_8_Jw61tysL_cV_xiXBcRyA3e%3DCGHGuSCgm%2B-4WxT9w%40mail.gmail.c= om?utm_medium=3Demail&utm_source=3Dfooter>>.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> --
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> You rece= ived this message because you are subscribed to the
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Google Groups "= ;Bitcoin Development Mailing List" group.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> To unsub= scribe from this group and stop receiving emails from it,
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 send an email to bitcoindev+unsubscribe@googlegroups.com
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <mailto:b= itcoindev%2Bunsubscribe@googlegroups.com>.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> To view = this discussion on the web visit
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://groups.google.c= om/d/msgid/bitcoindev/fb52ccb5-9942-4db8-b880-3c06ebc47cd1%40achow101.com <https://groups.google.com/d/msgid/bitcoindev/fb52ccb5-9942-4db8-b880-3c0= 6ebc47cd1%40achow101.com>.
>>>>>>>
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 --
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 You received this m= essage because you are subscribed to the Google
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Groups "Bitcoi= n Development Mailing List" group.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 To unsubscribe from= this group and stop receiving emails from it,
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 send an email to bitcoindev+unsubscribe@googlegroups.com
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <mailto:b= itcoindev%2Bunsubscribe@googlegroups.com>.
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 To view this discus= sion on the web visit
>>>>>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://groups.google.c= om/d/msgid/bitcoindev/070755a0-10e9-4903-9524-dd8ef98c1c8b%40achow101.com <https://groups.google.com/d/msgid/bitcoindev/070755a0-10e9-4903-9524-dd8= ef98c1c8b%40achow101.com>.
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscrib= ed 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.co= m.
>>>>>> To view this discussion on the web visit https://gro= ups.google.com/d/msgid/bitcoindev/0d4d85e3-9fbb-4bd4-af0f-92225e699b63%40ac= how101.com.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Michael Folkson
>>>>> Personal email: michaelfolkson@gmail.com
>>>>
>>>
>>>
>>> --
>>> Michael Folkson
>>> Personal email: michaelfolkson@gmail.com
>>
>
>
> --
> Michael Folkson
> Personal email: michaelfolkson@gmail.com

--
You received this message because you are subscribed to a topic in the Goog= le Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bitcoindev/cuMZ77KEQAA/unsubscribe<= /a>.
To unsubscribe from this group and all its topics, send an email to bit= coindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitc= oindev/84bb3ca1-a18e-48c8-a934-6fcef5470a36%40achow101.com.

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.= google.com/d/msgid/bitcoindev/CALZpt%2BHdRQEewsy08ezcGU38Gr0N%2BCwYgRr1CbRN= sDGEM_UThQ%40mail.gmail.com.
--000000000000dd1aa00616a1703c--