From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Sun, 09 Aug 2026 19:40:05 -0700 Received: from mail-oa1-f58.google.com ([209.85.160.58]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1wtFvo-0004Ou-CR for bitcoindev@gnusha.org; Sun, 09 Aug 2026 19:40:05 -0700 Received: by mail-oa1-f58.google.com with SMTP id 586e51a60fabf-455d6f14efesf386738fac.3 for ; Sun, 09 Aug 2026 19:40:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20251104; t=1786329598; x=1786934398; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:content-type :mime-version:subject:references:in-reply-to:message-id:to:from:date :sender:from:to:cc:subject:date:message-id:reply-to:content-type; bh=V9794uRNlYa07Zz7gHe4jzM62xGVyNYreykURQC1JDc=; b=Crt32jJUnnjXFi4Oz9s1rhJ1YXsDaCsKmhhm6h4wDa8r3quBVB3gslhpfpfBBP0EXW TcrY5aWxb1Q8y8AuWCbsq1S8J06wtoyCrfUyqKsrzLg5/+m60z989H8ZIEcRekGtZfBa 2rg8Rp0iSJrTemm/4aNEmB97DD4heuW0WPoZvo6emOl+l05uotJTZ/70oUpuWp2qOkBA MZL90ryu4tGazR/q7t5fpQqUidm2eqORLuFWU3Q3OyBYwT3dpSJB9/M15bcCmzHeqVEb 38IesxZu3+mHcDMKwcqzC7Vdm0wbtGDp4AzDFx8OqLghcHMVCtvWhmHpsie+xbCGlDOZ mzJg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1786329598; x=1786934398; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:content-type :mime-version:subject:references:in-reply-to:message-id:to:from:date :from:to:cc:subject:date:message-id:reply-to:content-type; bh=V9794uRNlYa07Zz7gHe4jzM62xGVyNYreykURQC1JDc=; b=pWbxdWWscUdt+dt/ruPnZW9garJ1dq2AR5YdU2xt3YhK0Lcc0tAj86iYwi39m+IbkA xT9OLBMpJb+iYg7w51ia1eMrO5I9D089YK7kGx2ItSI95RNeObbnNnKmvzgB4a+WZcOU C2YqIJtCcQRRu4D3U1AvJQQebnNXPH9QZByp8bUt/g5ghuXqJQPoRo7tCBP8bx59XWmV dGt0nTjPrdKMzLMilklgAecIrDKHjaYIFkJjzpCx8Pim8rqbVd2044SnwxKFgSl0ymvm zdDdH+qhR4hE9nlP0UJ+N4NsirRGsYR1ejd74lLXN4LQpKJeiPOLg6vdByMNGbNoouIP WMAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1786329598; x=1786934398; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:content-type :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:content-type; bh=V9794uRNlYa07Zz7gHe4jzM62xGVyNYreykURQC1JDc=; b=E4tdpafkDT4EkAV6qNZ5UhablFTCV15YS9ouKlVIHXf9tuY5+s5I7OnNSiiWKYv5Fw DHU+UrIR0o3vE1TkMfXqVknKFZ6V1IIjtGGbyIuA5BhQjknrBTHzJWQ+sKpvM6/QRn8J +GpEWqzJQ7wbwv37aMbpvVi1MMNpC+xDyknlWo/uAAzIH27lj1xAhy4Np3A2O6vaZRHd Ex0I1RwY8GS1dAE4Ht1lwMeyN/LkgHGKDrIJLVbZLoWfJV1llsGf8k8m65n3jRIylrja rWJBx7ewXaK5Ni+4k+jE113Bn+bG5gBeRpK3U4UIccHfvpOwAlF3jsO8MrB7Ncc6bb4W M+/g== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AHgh+Rqf20F/q0jkl2pbEbr/lmzaTlIbNZHwAL/vasayiBu5E3qtfxQrn3FqvEM8MEXBDSM6hUd99R7dJGB3@gnusha.org X-Gm-Message-State: AOJu0Yxps54Ax2fy+Xvs+jQ1No9C6K+gWCcQzKUWqct53bDBJz3j22kB qt9+9rl8rDKqh4F6MeG9qmFe97Rhu4ZFi6FbyuuQ69dtbQ4zsN08y+HA X-Received: by 2002:a05:6870:b2c4:b0:447:7db4:d287 with SMTP id 586e51a60fabf-45a0f36db22mr8738373fac.16.1786329597991; Sun, 09 Aug 2026 19:39:57 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="Aa7YSPQsRC1GmtICQ5wTdxOrz3Cwa1Yfdtefqz0e3f0ROYF4Ag==" Received: by 2002:a05:6870:51f:b0:459:1566:9e14 with SMTP id 586e51a60fabf-459cda63dd8ls1713255fac.2.-pod-prod-04-us; Sun, 09 Aug 2026 19:39:52 -0700 (PDT) X-Received: by 2002:a05:6808:c2b4:b0:495:da89:c578 with SMTP id 5614622812f47-4afadd162d5mr22246937b6e.9.1786329592296; Sun, 09 Aug 2026 19:39:52 -0700 (PDT) Received: by 2002:a05:690c:e194:20b0:81e:11b4:1172 with SMTP id 00721157ae682-82325401bbems7b3; Sun, 9 Aug 2026 18:40:29 -0700 (PDT) X-Received: by 2002:a05:690c:b85:b0:81e:6cd1:5329 with SMTP id 00721157ae682-8202275ac60mr233451287b3.34.1786326029109; Sun, 09 Aug 2026 18:40:29 -0700 (PDT) Date: Sun, 9 Aug 2026 18:40:28 -0700 (PDT) From: Antoine Riard To: Bitcoin Development Mailing List Message-Id: <43fa13f1-00bc-47e0-8a46-0668fd435e97n@googlegroups.com> In-Reply-To: <3341dee7-216d-40e6-b1b5-dfd32b3ccb1dn@googlegroups.com> References: <9e5a9595-d719-436b-ada0-a09900f1fcb9@mattcorallo.com> <3341dee7-216d-40e6-b1b5-dfd32b3ccb1dn@googlegroups.com> Subject: Re: [bitcoindev] Motion to remove Luke Dashjr from BIP Editors MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_175790_754015216.1786326028539" X-Original-Sender: antoine.riard@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 (/) ------=_Part_175790_754015216.1786326028539 Content-Type: multipart/alternative; boundary="----=_Part_175791_167164268.1786326028539" ------=_Part_175791_167164268.1786326028539 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =20 Hello I think it's the best move for Luke to remove himself from the BIP editorship, even if it's temporary. If he's not blocked from the github, nothing prevent him to contribute to the review work of the BIPs in a good spirit in the future and regain his BIP editor role. I have very been little been involved in all this OP_RETURN mess, whatever side one has taken in this discussion, so I hope and aim to hold an objective tone, in what I'm saying there after. I do have a very mixed opinion of the Luke's persona himself. On one hand, I respect the years of hard work and dedication invested in the bitcoin project. He has been technically contributing more longer than I had. On the other hand, for someone who is spending his time questioning the morality of his technical peers, I always been a bit cold about his professional ethics, given how he did behave repeatedly few times, especially with what did happen with coredev atlanta '22. As a former coreDev co-organizer, I very coldly appreciated that he went to the FBI to accuse coredev meeting participants to have been involved in any manner with the loss of his coins at the end of '22 and put the organizers in a situation where they legally had to reveal the names of *all* the participants in the meeting in an *indiscriminate* fashion. Rat'ing out your bitcoin core devs colleagues to a domestic intel agency to have a case build on all of them is very not okay, and I would say this whatever the jurisdiction that would be involved. Beyond, once the FBI subpoena was public, I reached out privately to Luke in April '24 to have more clarifications on this affair, as a former coredev co-organizer. Neither Luke, neither the FBI went back to me and as far as I know no participant was ever worried or more questioned about this Luke claim, so it tells you a lot about the seriousness of the ungrounded accusations that were made on the coredev participants as an indiscriminate group. If you have ever a problem with someone in this space, keep it contained and stay professional. There is a sense of measure and balance to have. On the removal of Luke, if it has been to be done by using the github administrative permission, as far as I know there is no mention in BIP1 or BIP2 or BIP3 about what is a formal process to remove someone from a BIP editor role, against her or his consent. Short of that, in my opinion if there is a wish to make the removal happening on bright lines, I would suggest to follow the following formalities: - in the lack of a clear organ deciding the removal of the BIP editor, have all existent BIP editors giving their public says on this and their own motivations - the BIP process is not a democracy, though everyone that has ever contributed to the repository and who is still broadly active in=20 bitcoin has a material interest in the resolution of this issue. if we check the gitlog there are like ~531 individual contributors to the git tree. if we had people who are credited or thanks in the BIPs documents we might have a rough 100 more people. it would be legitimate to have the ones who have contributed, at least significantly or meaningfully to have as say, without putting the process in a situation of functional paralysis. - give a chance to Luke or someone taking his defense to answer point by point in public what are the motivations justifying his removal of his BIP editor role, based on evidences if needed. giving him at least= =20 2 weeks or even a full month would legitimate. he can always be temporarily removed until there is a legit justification that has been answered from= =20 his side. - Murch was mentioning Luke's conflict of interest as a motivation to remove him from his BIP editor. nothing says in BIP3 editor's responsibilities that they should stay free from "conflict of interest". however the very goal the BIP process is to have implementation inter- compatibility therefore a shared set of logical rules executed the same by all the implementation to have a common network. it would appear to me that it's in the "spirit" of the BIP process that BIP editors have a duty of neutrality with regards to how they fulfill their editors role On this last point, I would strongly suggest to amend the BIP3 document to underscore that editors have an explicit duty of neutrality, and that under this duty they should not engage in the promotion of contentious fork, even under one of their other hats (be it the maintainer of a=20 full-node implementation or whatever). Otherwise it's lacking the good faith they owe to the community under their BIP editor roles. Bitcoin is at its heart a scientific project, science and engineering made progress by the rationalized discussion of contradictory viewpoints. No one can claim to have papal infaillability in this space, though if you do so you're always free to go to build your own fork and church and not to try to coerce people under your religion. By education, I'm sensible in matters of freedom of consciousness. I respect Luke's historical contributions in this space, so it's better for the community to tread him with respect and fairness on this aspect, even i= f it means taking a bit more time to resolve this issue and following more formalities. We should not race to the bottom in matters of procedural standards, and somehow acting in such a way it's closing surface for ulterior contestations. Finally, I would underscore we're in the middle of the month of August, at a period where people can be in vacations, it's okay to be more lenient on the time granted to resolute this issue. Some people might be on the road for vacations, or between two transport (like me) and be usually a bit less on their keyboard. All my take and humble opinion only. Best, Antoine OTS hash: 2dd0347a79c77bd2e56fa9587d0099baa9fcebccc688732e23c38fb4d99044fe Le Sunday, August 9, 2026 =C3=A0 11:35:19=E2=80=AFPM UTC+1, Michael Tidwell= a =C3=A9crit : > Luke,=20 > > Thanks for the years of hard work. Genuinely appreciated. > > It's my opinion this is the right move. And, it would be better to step= =20 > down yourself than get forced out through this informal process (Frankly= =20 > it's embarrassing that this seems appropriate given your historic=20 > contributions). I believe it's apparent to most, (and I hope to you), tha= t=20 > it's unlikely you would be working effectively with Core from here. > > There=E2=80=99s going to be a need for strong technical leader around=20 > decentralized mining at Ocean, and for a solid BIP editor if that new PoW= =20 > chain happens. Whoever takes that on is going to need real conviction. Go= od=20 > luck with whatever comes next and whatever happens. Looking forward to wh= at=20 > you building more amazing things at Ocean (again being genuine), so far= =20 > y'all have made a splash, looking forward to the waves! (get it? because= =20 > water and ocean.. anyways). > > Anyways for "communication", make sure you haven't accidentally blocked= =20 > someone who you think has stopped communicating with you.. for instance i= f=20 > I wasn't blocked, I would have just sent this as a DM. > > Thanks, > Tidwell > On Sunday, August 9, 2026 at 3:50:52=E2=80=AFPM UTC-4 Matt Corallo wrote: > >> I see no reason why he should not be removed.=20 >> >> Matt=20 >> >> On 8/9/26 2:29 PM, Murch wrote:=20 >> > Hello everyone,=20 >> >=20 >> > I recommend that Luke Dashjr be removed from the position of BIP=20 >> Editor.=20 >> >=20 >> > Over the past several years, Luke has been at the center of many=20 >> contentious disputes within the=20 >> > Bitcoin ecosystem, and this week a new forkcoin spun out of Bitcoin=20 >> under his leadership.=20 >> >=20 >> > More specifically, Luke was heavily involved in the creation and=20 >> implementation of BIP110, the=20 >> > proposal that led to the fork. During that process, he also exercised= =20 >> his authority as a BIP Editor=20 >> > inconsistently with the established editorial process unfairly favorin= g=20 >> the proposal he was involved=20 >> > in. For example, he attempted to assign a BIP number to the draft=20 >> publicly on Twitter before the=20 >> > proposal had been discussed on the mailing list, and he merged a PR=20 >> updating the BIP within minutes=20 >> > of the PR being opened.=20 >> >=20 >> > The latter is particularly notable given that Luke has otherwise made= =20 >> hardly any contributions to=20 >> > the day-to-day work of the BIP Editors since the additional editors=20 >> began serving in April 2024: he=20 >> > left fewer than 1% of the BIP Editor comments in the repository since= =20 >> then, and the merge action of=20 >> > this PR was his first since May 2024.=20 >> >=20 >> > Communication between Luke and other BIP Editors had already broken=20 >> down last year, following a=20 >> > discussion about his attempt to side-step the process by prematurely= =20 >> assigning a BIP number out of=20 >> > band.=20 >> >=20 >> > Taken together, I believe these circumstances raise serious concerns= =20 >> about Luke continuing to hold=20 >> > editorial authority. In particular:=20 >> >=20 >> > - he has exercised his editorial privileges in a manner that raises=20 >> conflict-of-interest concerns;=20 >> > - he has contributed little to the ongoing workload of the BIP Editors= ;=20 >> > - his recent championing of a contentious soft fork that now appears t= o=20 >> evolve into a hard fork=20 >> > represents a complete departure from the Bitcoin development ecosystem= ;=20 >> and=20 >> > - trust, communication, and coordination with the other BIP Editors=20 >> have broken down.=20 >> >=20 >> > For these reasons, I motion that Luke be removed as a BIP Editor.=20 >> >=20 >> > Murch=20 >> >=20 >> >> --=20 You received this message because you are subscribed to the Google Groups "= Bitcoin Development Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoindev+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/= 43fa13f1-00bc-47e0-8a46-0668fd435e97n%40googlegroups.com. ------=_Part_175791_167164268.1786326028539 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hello

I think it's the best move for Luke to remove himself f= rom the BIP
editorship, even if it's temporary. If he's not blocked fr= om the
github, nothing prevent him to contribute to the review work of=
the BIPs in a good spirit in the future and regain his BIP editor
role.

I have very been little been involved in all this OP_RET= URN mess,
whatever side one has taken in this discussion, so I hope an= d aim
to hold an objective tone, in what I'm saying there after.
=
I do have a very mixed opinion of the Luke's persona himself. On
one hand, I respect the years of hard work and dedication invested
in= the bitcoin project. He has been technically contributing more
longer= than I had. On the other hand, for someone who is spending
his time q= uestioning the morality of his technical peers, I always
been a bit co= ld about his professional ethics, given how he did
behave repeatedly f= ew times, especially with what did happen with
coredev atlanta '22.
As a former coreDev co-organizer, I very coldly appreciated that h= e
went to the FBI to accuse coredev meeting participants to have been<= br />involved in any manner with the loss of his coins at the end of '22and put the organizers in a situation where they legally had to
rev= eal the names of *all* the participants in the meeting in an
*indiscri= minate* fashion.

Rat'ing out your bitcoin core devs colleagues t= o a domestic intel
agency to have a case build on all of them is very = not okay, and I
would say this whatever the jurisdiction that would be= involved.
Beyond, once the FBI subpoena was public, I reached out pri= vately
to Luke in April '24 to have more clarifications on this affair= ,
as a former coredev co-organizer.

Neither Luke, neither t= he FBI went back to me and as far as I know
no participant was ever wo= rried or more questioned about this Luke
claim, so it tells you a lot = about the seriousness of the ungrounded
accusations that were made on = the coredev participants as an indiscriminate
group. If you have ever = a problem with someone in this space, keep it
contained and stay profe= ssional. There is a sense of measure and
balance to have.

O= n the removal of Luke, if it has been to be done by using the
github a= dministrative permission, as far as I know there is no
mention in BIP1= or BIP2 or BIP3 about what is a formal process
to remove someone from= a BIP editor role, against her or his consent.

Short of that, i= n my opinion if there is a wish to make the removal
happening on brigh= t lines, I would suggest to follow the following
formalities:
- i= n the lack of a clear organ deciding the removal of the BIP editor,
= =C2=A0 have all existent BIP editors giving their public says on this
= =C2=A0 and their own motivations
- the BIP process is not a democracy,= though everyone that has ever
=C2=A0 contributed to the repository an= d who is still broadly active in
=C2=A0 bitcoin has a material intere= st in the resolution of this issue.
=C2=A0 if we check the gitlog ther= e are like ~531 individual contributors
=C2=A0 to the git tree. if we = had people who are credited or thanks in the
=C2=A0 BIPs documents we = might have a rough 100 more people. it would be
=C2=A0 legitimate to h= ave the ones who have contributed, at least significantly
=C2=A0 or me= aningfully to have as say, without putting the process in a
=C2=A0 sit= uation of functional paralysis.
- give a chance to Luke or someone tak= ing his defense to answer point
=C2=A0 by point in public what are the= motivations justifying his removal
=C2=A0 of his BIP editor role, bas= ed on evidences if needed. giving him at least 2
=C2=A0 weeks or even = a full month would legitimate. he can always be temporarily
=C2=A0 rem= oved until there is a legit justification that has been answered from his s= ide.
- Murch was mentioning Luke's conflict of interest as a motivatio= n to
=C2=A0 remove him from his BIP editor. nothing says in BIP3 edito= r's
=C2=A0 responsibilities that they should stay free from "conflict = of interest".
=C2=A0 however the very goal the BIP process is to have = implementation inter-
=C2=A0 compatibility therefore a shared set of l= ogical rules executed the same
=C2=A0 by all the implementation to hav= e a common network. it would appear to
=C2=A0 me that it's in the "spi= rit" of the BIP process that BIP editors have
=C2=A0 a duty of neutral= ity with regards to how they fulfill their editors role

On this = last point, I would strongly suggest to amend the BIP3 document
to und= erscore that editors have an explicit duty of neutrality, and that
und= er this duty they should not engage in the promotion of contentious
fo= rk, even under one of their other hats (be it the maintainer of a full-node=
implementation or whatever). Otherwise it's lacking the good faith th= ey
owe to the community under their BIP editor roles.

Bitco= in is at its heart a scientific project, science and engineering
made = progress by the rationalized discussion of contradictory viewpoints.
N= o one can claim to have papal infaillability in this space, though if
= you do so you're always free to go to build your own fork and church andnot to try to coerce people under your religion. By education, I'm sensi= ble
in matters of freedom of consciousness.

I respect Luke'= s historical contributions in this space, so it's better for
the commu= nity to tread him with respect and fairness on this aspect, even if
it= means taking a bit more time to resolve this issue and following more
formalities. We should not race to the bottom in matters of procedural
standards, and somehow acting in such a way it's closing surface for
ulterior contestations.

Finally, I would underscore we're in th= e middle of the month of August,
at a period where people can be in va= cations, it's okay to be more lenient
on the time granted to resolute = this issue. Some people might be on the
road for vacations, or between= two transport (like me) and be usually a
bit less on their keyboard.<= br />
All my take and humble opinion only.

Best,
Antoi= ne
OTS hash: 2dd0347a79c77bd2e56fa9587d0099baa9fcebccc688732e23c38fb4d= 99044fe


Le Sunday, August 9, 2026 =C3=A0 11:35:19=E2=80=AFPM UTC+1, Michael= Tidwell a =C3=A9crit=C2=A0:

Luke,

Thanks for the years of hard work. Genuine= ly appreciated.

It's my opinion this is the right move. And, it = would be better to step down yourself than get forced out through this info= rmal process (Frankly it's embarrassing that this seems appropriate giv= en your historic contributions). I believe it's apparent to most, (and = I hope to you), that it's unlikely you would be working effectively wit= h Core from here.

There=E2=80=99s going to be a need for strong tech= nical leader around decentralized mining at Ocean, and for a solid BIP edit= or if that new PoW chain happens. Whoever takes that on is going to need re= al conviction. Good luck with whatever comes next and whatever happens. Loo= king forward to what you building more amazing things at Ocean (again being= genuine), so far y'all have made a splash, looking forward to the wave= s! (get it? because water and ocean.. anyways).

Anyways for "co= mmunication", make sure you haven't accidentally blocked someone w= ho you think has stopped communicating=C2=A0with you.. for instance if I wa= sn't blocked, I would have just sent this as a DM.

Thanks,
Ti= dwell

= On Sunday, August 9, 2026 at 3:50:52=E2=80=AFPM UTC-4 Matt Corallo wrote:
I see no reason why he = should not be removed.

Matt

On 8/9/26 2:29 PM, Murch wrote:
> Hello everyone,
>=20
> I recommend that Luke Dashjr be removed from the position of BIP E= ditor.
>=20
> Over the past several years, Luke has been at the center of many c= ontentious disputes within the=20
> Bitcoin ecosystem, and this week a new forkcoin spun out of Bitcoi= n under his leadership.
>=20
> More specifically, Luke was heavily involved in the creation and i= mplementation of BIP110, the=20
> proposal that led to the fork. During that process, he also exerci= sed his authority as a BIP Editor=20
> inconsistently with the established editorial process unfairly fav= oring the proposal he was involved=20
> in. For example, he attempted to assign a BIP number to the draft = publicly on Twitter before the=20
> proposal had been discussed on the mailing list, and he merged a P= R updating the BIP within minutes=20
> of the PR being opened.
>=20
> The latter is particularly notable given that Luke has otherwise m= ade hardly any contributions to=20
> the day-to-day work of the BIP Editors since the additional editor= s began serving in April 2024: he=20
> left fewer than 1% of the BIP Editor comments in the repository si= nce then, and the merge action of=20
> this PR was his first since May 2024.
>=20
> Communication between Luke and other BIP Editors had already broke= n down last year, following a=20
> discussion about his attempt to side-step the process by premature= ly assigning a BIP number out of=20
> band.
>=20
> Taken together, I believe these circumstances raise serious concer= ns about Luke continuing to hold=20
> editorial authority. In particular:
>=20
> - he has exercised his editorial privileges in a manner that raise= s conflict-of-interest concerns;
> - he has contributed little to the ongoing workload of the BIP Edi= tors;
> - his recent championing of a contentious soft fork that now appea= rs to evolve into a hard fork=20
> represents a complete departure from the Bitcoin development ecosy= stem; and
> - trust, communication, and coordination with the other BIP Editor= s have broken down.
>=20
> For these reasons, I motion that Luke be removed as a BIP Editor.
>=20
> Murch
>=20

--
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 visit https://groups.google.com/d/msgid/bitcoind= ev/43fa13f1-00bc-47e0-8a46-0668fd435e97n%40googlegroups.com.
------=_Part_175791_167164268.1786326028539-- ------=_Part_175790_754015216.1786326028539--