From: Jonas Nick <jonasd.nick@gmail.com>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Motion to remove Luke Dashjr from BIP Editors
Date: Mon, 10 Aug 2026 08:08:39 +0000 [thread overview]
Message-ID: <cb930bf6-985c-47f1-bf99-0bc9ebd650b9@gmail.com> (raw)
In-Reply-To: <ad36522e-f479-4ac3-9904-cf00cfa8ec46@murch.one>
I support this motion.
BIP editors should actively review BIP drafts, apply the BIP process neutrally,
and provide technically precise feedback.
Inactive editors do not need editorial permissions. This is even more true if
their main activity in the last two years is using the role to advance a
proposal they personally support while bypassing the established process, as
Murch described.
The basic duties of BIP editors require precise use of established technical
terminology and good judgment. Luke routinely uses technical terms in ways that
are incompatible with their established meanings. Recent examples of such misuse
and poor judgment include saying that "BIP110 is Bitcoin," that "BIP110 has
consensus," and that "Activation is certain" [1].
I find it particularly concerning that Luke, in his recent advocacy for BIP 110,
irresponsibly misled users by repeatedly calling it "zero risk" [2].
The BIPs repository deserves editors who can communicate effectively and
maintain a basic working relationship with the other editors. Calling Murch, one
of the most productive BIP editors, "a liar" without even identifying what he
allegedly lied about does not meet that standard [3].
[1] https://x.com/LukeDashjr/status/2082795948648919419
https://x.com/LukeDashjr/status/2081971093292662882
https://x.com/LukeDashjr/status/2086121519315374526
[2] https://x.com/LukeDashjr/status/2030565712629035382
https://x.com/LukeDashjr/status/2081086470194860053
https://x.com/LukeDashjr/status/2067690041669832963
[3] https://x.com/LukeDashjr/status/2046598586494857478
--
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/cb930bf6-985c-47f1-bf99-0bc9ebd650b9%40gmail.com.
next prev parent reply other threads:[~2026-08-10 9:38 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
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 [this message]
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=cb930bf6-985c-47f1-bf99-0bc9ebd650b9@gmail.com \
--to=jonasd.nick@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