Bitcoin Development Mailinglist
 help / color / mirror / Atom feed
From: Murch <murch@murch.one>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Motion to remove Luke Dashjr from BIP Editors
Date: Mon, 10 Aug 2026 08:20:26 -0700	[thread overview]
Message-ID: <e066814f-451c-46f0-bf54-bbcdcff6fcf3@murch.one> (raw)
In-Reply-To: <7f146572-8b49-4a73-9e03-3d9131226126@dashjr.org>

Thanks for the reply, Luke.

On 2026-08-09 12:35, Luke Dashjr wrote:
> 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.

You argue like my friend’s five-year-old: “Liar.” “No, you.”

Your history of toxic behavior has been well established since Gavin 
Andresen’s tenure.¹ You assert things without evidence, fail to explain 
your point of view, and revise history when doing so makes you look less 
likely to have been wrong.

You have tried to pass off a modified fork² as the Bitcoin Core package 
for Gentoo. You tried to block³ Taproot’s authors from documenting their 
preferred deployment mechanism, attempting instead to supersede it with 
your personal preference. You tried to use Bitcoin Core’s translation 
resources for your personal fork and, when asked to stop, attempted a 
hostile takeover⁴ of the repository.

You have baselessly accused fellow Bitcoin Core contributors of 
stealing⁵ from you. You have filed CVEs against the judgment of other 
contributors. You call Bitcoin Core a malware project and an attack on 
Bitcoin when you disagree with its decisions, while simultaneously 
presenting Bitcoin Knots as merely another release of Bitcoin Core, 
associating it with Bitcoin Core’s reputation and making it appear that 
everyone who works on Bitcoin Core is also a Knots contributor.

Especially over the last few months, you have deliberately 
misrepresented the prospects of your soft fork on an almost daily basis.

People have been making excuses for you for over a decade: “Luke is the 
tenth man,” “Luke’s unique point of view is valuable,” “Luke is socially 
awkward and confuses personal perception with objective reality,” and so on.

I’m tired of people giving you a pass for unacceptable behavior simply 
because everyone has become accustomed to it. I’m fed up with your 
instigation of harassment campaigns, bullying, and name-calling. I no 
longer want to work with someone who either pretends not to recognize, 
or genuinely cannot recognize, that other people can disagree with him 
and still have a valid point of view.

You have contributed very little to the BIPs repository in half a 
decade, causing the work in the repository to stall twice in the last 
few years. At the same time, you have happily taken credit⁵ for the work 
of others. You have been a net-negative contributor to Bitcoin for 
years. Whatever you contributed in the past, it is past time that we 
stop associating with you.

Now that people have made you king of your own forkcoin, please let us 
take you at your word when you write, “Bpedo is not Bitcoin” and “Yes, I 
have no interest in having anything to do with Bpedo.

Godspeed,
Murch

¹ https://bitcointalk.org/index.php?topic=62037.0
² 
https://www.reddit.com/r/Bitcoin/comments/2pfgjg/exposed_lukejr_plans_on_forcing_blacklists_on_all/
³ 
https://bitcoinmagazine.com/technical/lottrue-or-lotfalse-this-is-the-last-hurdle-before-taproot-activationhttps://www.erisian.com.au/bitcoin-core-dev/log-2024-05-02.html#l-573https://xcom/LukeDashjr/status/1921571463343055003https://x.com/murchandamus/status/19865630014037773913

-- 
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/e066814f-451c-46f0-bf54-bbcdcff6fcf3%40murch.one.


  reply	other threads:[~2026-08-10 15:29 UTC|newest]

Thread overview: 12+ 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-10 15:20   ` Murch [this message]
2026-08-09 19:47 ` Jameson Lopp
2026-08-09 19:48 ` Matt Corallo
2026-08-09 20:42   ` Michael Tidwell
2026-08-10  1:40     ` Antoine Riard
2026-08-09 20:56 ` Olaoluwa Osuntokun
2026-08-10  8:08 ` Jonas Nick
2026-08-10 15:05 ` Anthony Towns
2026-08-10 15:30 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2026-08-10 20:51 ` Bryan Bishop

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=e066814f-451c-46f0-bf54-bbcdcff6fcf3@murch.one \
    --to=murch@murch.one \
    --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