From: Michael Tidwell <mtidwell021@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Motion to remove Luke Dashjr from BIP Editors
Date: Sun, 9 Aug 2026 13:42:58 -0700 (PDT) [thread overview]
Message-ID: <3341dee7-216d-40e6-b1b5-dfd32b3ccb1dn@googlegroups.com> (raw)
In-Reply-To: <9e5a9595-d719-436b-ada0-a09900f1fcb9@mattcorallo.com>
[-- 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 --]
next prev parent reply other threads:[~2026-08-09 22:35 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 [this message]
2026-08-09 20:56 ` Olaoluwa Osuntokun
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=3341dee7-216d-40e6-b1b5-dfd32b3ccb1dn@googlegroups.com \
--to=mtidwell021@gmail.com \
--cc=bitcoindev@googlegroups.com \
/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