From: Olaoluwa Osuntokun <laolu32@gmail.com>
To: Murch <murch@murch.one>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Motion to remove Luke Dashjr from BIP Editors
Date: Sun, 9 Aug 2026 13:56:13 -0700 [thread overview]
Message-ID: <CAO3Pvs8hjB=8fd5=NGCxWWpvT7Qcy+nf26RDcVVvG-M1jA5HFw@mail.gmail.com> (raw)
In-Reply-To: <ad36522e-f479-4ac3-9904-cf00cfa8ec46@murch.one>
[-- 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 --]
prev parent reply other threads:[~2026-08-09 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAO3Pvs8hjB=8fd5=NGCxWWpvT7Qcy+nf26RDcVVvG-M1jA5HFw@mail.gmail.com' \
--to=laolu32@gmail.com \
--cc=bitcoindev@googlegroups.com \
--cc=murch@murch.one \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox