* [bitcoindev] Motion to remove Luke Dashjr from BIP Editors
@ 2026-08-09 18:29 Murch
2026-08-09 19:35 ` Luke Dashjr
` (3 more replies)
0 siblings, 4 replies; 6+ messages in thread
From: Murch @ 2026-08-09 18:29 UTC (permalink / raw)
To: Bitcoin Development Mailing List
Hello everyone,
I recommend that Luke Dashjr be removed from the position of BIP Editor.
Over the past several years, Luke has been at the center of many
contentious disputes within the Bitcoin ecosystem, and this week a new
forkcoin spun out of Bitcoin under his leadership.
More specifically, Luke was heavily involved in the creation and
implementation of BIP110, the proposal that led to the fork. During that
process, he also exercised his authority as a BIP Editor inconsistently
with the established editorial process unfairly favoring the proposal he
was involved in. For example, he attempted to assign a BIP number to the
draft publicly on Twitter before the proposal had been discussed on the
mailing list, and he merged a PR updating the BIP within minutes of the
PR being opened.
The latter is particularly notable given that Luke has otherwise made
hardly any contributions to the day-to-day work of the BIP Editors since
the additional editors began serving in April 2024: he left fewer than
1% of the BIP Editor comments in the repository since then, and the
merge action of this PR was his first since May 2024.
Communication between Luke and other BIP Editors had already broken down
last year, following a discussion about his attempt to side-step the
process by prematurely assigning a BIP number out of band.
Taken together, I believe these circumstances raise serious concerns
about Luke continuing to hold editorial authority. In particular:
- he has exercised his editorial privileges in a manner that raises
conflict-of-interest concerns;
- he has contributed little to the ongoing workload of the BIP Editors;
- his recent championing of a contentious soft fork that now appears to
evolve into a hard fork represents a complete departure from the Bitcoin
development ecosystem; and
- trust, communication, and coordination with the other BIP Editors have
broken down.
For these reasons, I motion that Luke be removed as a BIP Editor.
Murch
--
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 visit https://groups.google.com/d/msgid/bitcoindev/ad36522e-f479-4ac3-9904-cf00cfa8ec46%40murch.one.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [bitcoindev] Motion to remove Luke Dashjr from BIP Editors
2026-08-09 18:29 [bitcoindev] Motion to remove Luke Dashjr from BIP Editors Murch
@ 2026-08-09 19:35 ` Luke Dashjr
2026-08-09 19:47 ` Jameson Lopp
` (2 subsequent siblings)
3 siblings, 0 replies; 6+ messages in thread
From: Luke Dashjr @ 2026-08-09 19:35 UTC (permalink / raw)
To: bitcoindev, Murch
These are false accusations. I have followed the BIP process
consistently for years. Your novice opinions alone do not establish new
processes.
You are the one who stopped communicating, not I.
You are the one who should be removed.
Luke
On 8/9/26 14:29, Murch wrote:
> Hello everyone,
>
> I recommend that Luke Dashjr be removed from the position of BIP Editor.
>
> Over the past several years, Luke has been at the center of many
> contentious disputes within the Bitcoin ecosystem, and this week a new
> forkcoin spun out of Bitcoin under his leadership.
>
> More specifically, Luke was heavily involved in the creation and
> implementation of BIP110, the proposal that led to the fork. During
> that process, he also exercised his authority as a BIP Editor
> inconsistently with the established editorial process unfairly
> favoring the proposal he was involved in. For example, he attempted to
> assign a BIP number to the draft publicly on Twitter before the
> proposal had been discussed on the mailing list, and he merged a PR
> updating the BIP within minutes of the PR being opened.
>
> The latter is particularly notable given that Luke has otherwise made
> hardly any contributions to the day-to-day work of the BIP Editors
> since the additional editors began serving in April 2024: he left
> fewer than 1% of the BIP Editor comments in the repository since then,
> and the merge action of this PR was his first since May 2024.
>
> Communication between Luke and other BIP Editors had already broken
> down last year, following a discussion about his attempt to side-step
> the process by prematurely assigning a BIP number out of band.
>
> Taken together, I believe these circumstances raise serious concerns
> about Luke continuing to hold editorial authority. In particular:
>
> - he has exercised his editorial privileges in a manner that raises
> conflict-of-interest concerns;
> - he has contributed little to the ongoing workload of the BIP Editors;
> - his recent championing of a contentious soft fork that now appears
> to evolve into a hard fork represents a complete departure from the
> Bitcoin development ecosystem; and
> - trust, communication, and coordination with the other BIP Editors
> have broken down.
>
> For these reasons, I motion that Luke be removed as a BIP Editor.
>
> Murch
>
--
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 visit https://groups.google.com/d/msgid/bitcoindev/7f146572-8b49-4a73-9e03-3d9131226126%40dashjr.org.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [bitcoindev] Motion to remove Luke Dashjr from BIP Editors
2026-08-09 18:29 [bitcoindev] Motion to remove Luke Dashjr from BIP Editors Murch
2026-08-09 19:35 ` Luke Dashjr
@ 2026-08-09 19:47 ` Jameson Lopp
2026-08-09 19:48 ` Matt Corallo
2026-08-09 20:56 ` Olaoluwa Osuntokun
3 siblings, 0 replies; 6+ messages in thread
From: Jameson Lopp @ 2026-08-09 19:47 UTC (permalink / raw)
To: Murch; +Cc: Bitcoin Development Mailing List
[-- Attachment #1: Type: text/plain, Size: 4086 bytes --]
This is unprecedented because there is, to my knowledge, no formal
governance structure or policy around management of BIP Editors.
I see no need to rehash the lengthy list of disputes in which Luke has been
involved; it seems to me that ultimately this comes down to reputation.
In my view, Luke has proven himself to be poorly suited to working well
with others. It's nearly impossible for him to communicate clearly because
he often operates under completely different definitions of terms than are
standard, and this twisting of terminology seems to be his modus operandi
for remaining "honest" (in his view) while making outrageous statements.
Beyond that, his open hostility and animosity toward fellow contributors
and often even the whole of Bitcoin Core as an organization make it
incredibly puzzling to me why he should have any association with it
whatsoever.
This isn't a democracy and I have no vote. But it seems to me that if the
other BIP Editors are uninterested in continuing to work with Luke, they
are under no obligation to leave privileged access open for him to
potentially abuse.
On Sun, Aug 9, 2026 at 2:53 PM Murch <murch@murch.one> wrote:
> Hello everyone,
>
> I recommend that Luke Dashjr be removed from the position of BIP Editor.
>
> Over the past several years, Luke has been at the center of many
> contentious disputes within the Bitcoin ecosystem, and this week a new
> forkcoin spun out of Bitcoin under his leadership.
>
> More specifically, Luke was heavily involved in the creation and
> implementation of BIP110, the proposal that led to the fork. During that
> process, he also exercised his authority as a BIP Editor inconsistently
> with the established editorial process unfairly favoring the proposal he
> was involved in. For example, he attempted to assign a BIP number to the
> draft publicly on Twitter before the proposal had been discussed on the
> mailing list, and he merged a PR updating the BIP within minutes of the
> PR being opened.
>
> The latter is particularly notable given that Luke has otherwise made
> hardly any contributions to the day-to-day work of the BIP Editors since
> the additional editors began serving in April 2024: he left fewer than
> 1% of the BIP Editor comments in the repository since then, and the
> merge action of this PR was his first since May 2024.
>
> Communication between Luke and other BIP Editors had already broken down
> last year, following a discussion about his attempt to side-step the
> process by prematurely assigning a BIP number out of band.
>
> Taken together, I believe these circumstances raise serious concerns
> about Luke continuing to hold editorial authority. In particular:
>
> - he has exercised his editorial privileges in a manner that raises
> conflict-of-interest concerns;
> - he has contributed little to the ongoing workload of the BIP Editors;
> - his recent championing of a contentious soft fork that now appears to
> evolve into a hard fork represents a complete departure from the Bitcoin
> development ecosystem; and
> - trust, communication, and coordination with the other BIP Editors have
> broken down.
>
> For these reasons, I motion that Luke be removed as a BIP Editor.
>
> Murch
>
> --
> 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 visit
> https://groups.google.com/d/msgid/bitcoindev/ad36522e-f479-4ac3-9904-cf00cfa8ec46%40murch.one
> .
>
--
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 visit https://groups.google.com/d/msgid/bitcoindev/CADL_X_e-vFu-HDmMhbkY55myh%3DihOJ2J9WpzMvf1X8aDmnQdrg%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 5028 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [bitcoindev] Motion to remove Luke Dashjr from BIP Editors
2026-08-09 18:29 [bitcoindev] Motion to remove Luke Dashjr from BIP Editors Murch
2026-08-09 19:35 ` Luke Dashjr
2026-08-09 19:47 ` Jameson Lopp
@ 2026-08-09 19:48 ` Matt Corallo
2026-08-09 20:42 ` Michael Tidwell
2026-08-09 20:56 ` Olaoluwa Osuntokun
3 siblings, 1 reply; 6+ messages in thread
From: Matt Corallo @ 2026-08-09 19:48 UTC (permalink / raw)
To: Murch, Bitcoin Development Mailing List
I see no reason why he should not be removed.
Matt
On 8/9/26 2:29 PM, Murch wrote:
> Hello everyone,
>
> I recommend that Luke Dashjr be removed from the position of BIP Editor.
>
> Over the past several years, Luke has been at the center of many contentious disputes within the
> Bitcoin ecosystem, and this week a new forkcoin spun out of Bitcoin under his leadership.
>
> More specifically, Luke was heavily involved in the creation and implementation of BIP110, the
> proposal that led to the fork. During that process, he also exercised his authority as a BIP Editor
> inconsistently with the established editorial process unfairly favoring the proposal he was involved
> in. For example, he attempted to assign a BIP number to the draft publicly on Twitter before the
> proposal had been discussed on the mailing list, and he merged a PR updating the BIP within minutes
> of the PR being opened.
>
> The latter is particularly notable given that Luke has otherwise made hardly any contributions to
> the day-to-day work of the BIP Editors since the additional editors began serving in April 2024: he
> left fewer than 1% of the BIP Editor comments in the repository since then, and the merge action of
> this PR was his first since May 2024.
>
> Communication between Luke and other BIP Editors had already broken down last year, following a
> discussion about his attempt to side-step the process by prematurely assigning a BIP number out of
> band.
>
> Taken together, I believe these circumstances raise serious concerns about Luke continuing to hold
> editorial authority. In particular:
>
> - he has exercised his editorial privileges in a manner that raises conflict-of-interest concerns;
> - he has contributed little to the ongoing workload of the BIP Editors;
> - his recent championing of a contentious soft fork that now appears to evolve into a hard fork
> represents a complete departure from the Bitcoin development ecosystem; and
> - trust, communication, and coordination with the other BIP Editors have broken down.
>
> For these reasons, I motion that Luke be removed as a BIP Editor.
>
> Murch
>
--
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 visit https://groups.google.com/d/msgid/bitcoindev/9e5a9595-d719-436b-ada0-a09900f1fcb9%40mattcorallo.com.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [bitcoindev] Motion to remove Luke Dashjr from BIP Editors
2026-08-09 19:48 ` Matt Corallo
@ 2026-08-09 20:42 ` Michael Tidwell
0 siblings, 0 replies; 6+ messages in thread
From: Michael Tidwell @ 2026-08-09 20:42 UTC (permalink / raw)
To: Bitcoin Development Mailing List
[-- Attachment #1.1: Type: text/plain, Size: 3940 bytes --]
Luke,
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
down yourself than get forced out through this informal process (Frankly
it's embarrassing that this seems appropriate given your historic
contributions). I believe it's apparent to most, (and I hope to you), that
it's unlikely you would be working effectively with Core from here.
There’s going to be a need for strong technical leader around decentralized
mining at Ocean, and for a solid BIP editor if that new PoW chain happens.
Whoever takes that on is going to need real conviction. Good luck with
whatever comes next and whatever happens. Looking 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 waves! (get it? because water
and ocean.. anyways).
Anyways for "communication", make sure you haven't accidentally blocked
someone who you think has stopped communicating with you.. for instance if
I wasn't blocked, I would have just sent this as a DM.
Thanks,
Tidwell
On Sunday, August 9, 2026 at 3:50:52 PM 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,
> >
> > I recommend that Luke Dashjr be removed from the position of BIP Editor.
> >
> > Over the past several years, Luke has been at the center of many
> contentious disputes within the
> > Bitcoin ecosystem, and this week a new forkcoin spun out of Bitcoin
> under his leadership.
> >
> > More specifically, Luke was heavily involved in the creation and
> implementation of BIP110, the
> > proposal that led to the fork. During that process, he also exercised
> his authority as a BIP Editor
> > inconsistently with the established editorial process unfairly favoring
> the proposal he was involved
> > in. For example, he attempted to assign a BIP number to the draft
> publicly on Twitter before the
> > proposal had been discussed on the mailing list, and he merged a PR
> updating the BIP within minutes
> > of the PR being opened.
> >
> > The latter is particularly notable given that Luke has otherwise made
> hardly any contributions to
> > the day-to-day work of the BIP Editors since the additional editors
> began serving in April 2024: he
> > left fewer than 1% of the BIP Editor comments in the repository since
> then, and the merge action of
> > this PR was his first since May 2024.
> >
> > Communication between Luke and other BIP Editors had already broken down
> last year, following a
> > discussion about his attempt to side-step the process by prematurely
> assigning a BIP number out of
> > band.
> >
> > Taken together, I believe these circumstances raise serious concerns
> about Luke continuing to hold
> > editorial authority. In particular:
> >
> > - he has exercised his editorial privileges in a manner that raises
> conflict-of-interest concerns;
> > - he has contributed little to the ongoing workload of the BIP Editors;
> > - his recent championing of a contentious soft fork that now appears to
> evolve into a hard fork
> > represents a complete departure from the Bitcoin development ecosystem;
> and
> > - trust, communication, and coordination with the other BIP Editors have
> broken down.
> >
> > For these reasons, I motion that Luke be removed as a BIP Editor.
> >
> > Murch
> >
>
>
--
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 visit https://groups.google.com/d/msgid/bitcoindev/3341dee7-216d-40e6-b1b5-dfd32b3ccb1dn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 4554 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [bitcoindev] Motion to remove Luke Dashjr from BIP Editors
2026-08-09 18:29 [bitcoindev] Motion to remove Luke Dashjr from BIP Editors Murch
` (2 preceding siblings ...)
2026-08-09 19:48 ` Matt Corallo
@ 2026-08-09 20:56 ` Olaoluwa Osuntokun
3 siblings, 0 replies; 6+ messages in thread
From: Olaoluwa Osuntokun @ 2026-08-09 20:56 UTC (permalink / raw)
To: Murch; +Cc: Bitcoin Development Mailing List
[-- Attachment #1: Type: text/plain, Size: 4385 bytes --]
Hi Murch,
I second this motion.
Luke put forth a proposal, then went on to receive direct and substantial
technical feedback from all across the ecosystem, but rather than faithfully
engaging with such feedback (we're all liars ofc), he used his position as a
BIP editor to fast track the proposal anyway, assigning it a number out of
band
(thereby side stepping the normal procedure), all while contributing next to
nothing to the day-to-day work of the other BIP editors.
I think it's worth being very explicit w.r.t this motion. This isn't about
"punishing" a developer for advocating a fork. Devs are ofc free to champion
any idea, no matter how dumb or contentious they are, forking if they deem
it
necessary. Rather this is about whether someone who bypasses all editorial
processes when it benefits them, cannot maintain a normal working
relationship
with his co-editors, and now is the head of a project hellbent on creating a
new alt-coin (after their failed fork) can be trusted with an editorial
position within Bitcoin's standard process. It should be clear to anyone
reading this, that he cannot.
His persistent fork also creates a clear conflict of interest: Luke is now
the
leader of a project that seeks to undermine Bitcoin itself (you fool, don't
you
see, bcash jr is the real Bitcoin!), a standing BIP editor shouldn't have a
direct stake in such a project.
-- Laolu
On Sun, Aug 9, 2026 at 11:53 AM Murch <murch@murch.one> wrote:
> Hello everyone,
>
> I recommend that Luke Dashjr be removed from the position of BIP Editor.
>
> Over the past several years, Luke has been at the center of many
> contentious disputes within the Bitcoin ecosystem, and this week a new
> forkcoin spun out of Bitcoin under his leadership.
>
> More specifically, Luke was heavily involved in the creation and
> implementation of BIP110, the proposal that led to the fork. During that
> process, he also exercised his authority as a BIP Editor inconsistently
> with the established editorial process unfairly favoring the proposal he
> was involved in. For example, he attempted to assign a BIP number to the
> draft publicly on Twitter before the proposal had been discussed on the
> mailing list, and he merged a PR updating the BIP within minutes of the
> PR being opened.
>
> The latter is particularly notable given that Luke has otherwise made
> hardly any contributions to the day-to-day work of the BIP Editors since
> the additional editors began serving in April 2024: he left fewer than
> 1% of the BIP Editor comments in the repository since then, and the
> merge action of this PR was his first since May 2024.
>
> Communication between Luke and other BIP Editors had already broken down
> last year, following a discussion about his attempt to side-step the
> process by prematurely assigning a BIP number out of band.
>
> Taken together, I believe these circumstances raise serious concerns
> about Luke continuing to hold editorial authority. In particular:
>
> - he has exercised his editorial privileges in a manner that raises
> conflict-of-interest concerns;
> - he has contributed little to the ongoing workload of the BIP Editors;
> - his recent championing of a contentious soft fork that now appears to
> evolve into a hard fork represents a complete departure from the Bitcoin
> development ecosystem; and
> - trust, communication, and coordination with the other BIP Editors have
> broken down.
>
> For these reasons, I motion that Luke be removed as a BIP Editor.
>
> Murch
>
> --
> 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 visit
> https://groups.google.com/d/msgid/bitcoindev/ad36522e-f479-4ac3-9904-cf00cfa8ec46%40murch.one
> .
>
--
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 visit https://groups.google.com/d/msgid/bitcoindev/CAO3Pvs8hjB%3D8fd5%3DNGCxWWpvT7Qcy%2Bnf26RDcVVvG-M1jA5HFw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 5352 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2026-08-09 22:35 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-08-09 18:29 [bitcoindev] Motion to remove Luke Dashjr from BIP Editors Murch
2026-08-09 19:35 ` Luke Dashjr
2026-08-09 19:47 ` Jameson Lopp
2026-08-09 19:48 ` Matt Corallo
2026-08-09 20:42 ` Michael Tidwell
2026-08-09 20:56 ` Olaoluwa Osuntokun
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox