From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Mon, 10 Aug 2026 08:32:51 -0700 Received: from mail-oa1-f58.google.com ([209.85.160.58]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1wtRze-0003Vz-96 for bitcoindev@gnusha.org; Mon, 10 Aug 2026 08:32:51 -0700 Received: by mail-oa1-f58.google.com with SMTP id 586e51a60fabf-4566537e644sf2514104fac.0 for ; Mon, 10 Aug 2026 08:32:50 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1786375964; cv=pass; d=google.com; s=arc-20260327; b=jly+2zauQ12AVgSWgZRboCZP4HTWFIHVGELQlNRxhZ0ykFPaa1UasKSGZAGlXH4q8O lNFCrXOguQ+fIgBr13Fan2QhofCSjMJQTLuN/ozuBTLq0SbONmHDFDTjbpmENBOcFYQG QKdymMcpOlfp/5pj9fFbmZysYzXpHJvNomTsmf2O9QW6h61L8q4efhopUco/y6Iayp57 mNG9LpFS3Ids6EAjqatyGdzyarwX0CRQ7h3KVyL4jZAQ2lrE3WO7vrYkGg6m8caKFJxh zhTMfHb+stHx5qU/5a/GOBk8/8itwHjzt6lRsXRk3bf+ZHOQ29b1G4VBmTgTTzWtjeIq JkIA== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to:mime-version:feedback-id :references:in-reply-to:message-id:subject:cc:from:to:date :dkim-signature; bh=byS7zfV9ZjkxEWCxl3XC0gIIPTbWJVMXhr5tdgyM1M0=; fh=c6/JdcPc7+CBhbAhlq3jgJ0O6bgM0cleYSY27RSI/nc=; b=eipsihUhFoMxaJr7iWkUNc/eYTZcK723O3M5IKzCqkevoqThN5gO7S7V7HJaoe2Ob9 b6xn/0nuJIUSXZhnxggku6Q1mzctL9GoP07UQQIFGp3e67qE8mHTvLEN5khK8S6B0j33 AZPdtHBZjvRA/rC9heeVG+ttHWQD6CQWMPRpo1Bk0RYxnm93jauEwDAzAjl+5Abi4cZX oPyaRbwrCzhDBlnFBkECnfeO+zE1THDxvQsW4u5gZ40XyFLO2i259jJSEcBo4IctqVjS 6bU0pI/nmgzdAdyW1r7hUKOO86kCM77VCgtabt6z+xjoxnF+DDTjalzq1aFVvFdaOSeV OAdQ==; darn=gnusha.org ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@protonmail.com header.s=protonmail3 header.b=viKpuuwP; spf=pass (google.com: domain of darosior@protonmail.com designates 109.224.244.17 as permitted sender) smtp.mailfrom=darosior@protonmail.com; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=protonmail.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20251104; t=1786375964; x=1786980764; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to :x-original-authentication-results:x-original-sender:content-type :mime-version:feedback-id:references:in-reply-to:message-id:subject :cc:from:to:date:from:to:cc:subject:date:message-id:reply-to :content-type; bh=byS7zfV9ZjkxEWCxl3XC0gIIPTbWJVMXhr5tdgyM1M0=; b=EQbapyT+SJ1Mpp5pGuTD3ej+xPAG3YFsn/ZMm7jVttHfQLY8eFTjQ6/dSerhf2CWn9 2zbpcEye5OA8wKtbfAgCIb55bbOxvr+oyFsGfEt3MOX2Rr2vz35LgArbcO2VoFC/2YDf rAuuo9iKT0ofKsAOFXgEF6btLtCjp+3vI2rI4PU3mhniegt2DFNaJUgK8FnZO5F1491J VAEsqHHwi3yqEBmOEoKLZoDpXIzTcbKJ2vY3MlxQB97WUksm91MvyVQo8WbomzYLiErF OXGc9Xv7D6O/FdpySeBaYilLRxhyqA+U9LYQCKXZXwWxK3uVlV7oRRJ9oRVNcu22XFfI iyVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1786375964; x=1786980764; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to :x-original-authentication-results:x-original-sender:content-type :mime-version:feedback-id:references:in-reply-to:message-id:subject :cc:from:to:date:x-beenthere:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to:content-type; bh=byS7zfV9ZjkxEWCxl3XC0gIIPTbWJVMXhr5tdgyM1M0=; b=fMdeJgMgdPa/ilrJEAQeiNb0QxG+J4MXdwf0Oh6D11YxM0PDT5VqCJrt+fj6l6yPcq BdeXoAhgmlqbtVXFZVtmEINDT2mbvAp9RTpqhy+vcYJphDR8ZD/Cp2PN0z7gF0MOGcPZ +DBxYb1YzNRi938erElRbKuNt6p65X81ntTc0G07OHrUYCWj7e1ivqS4C6tRAoU2ku1u dgytKLPR+XO0fLaaymMwCpiIswodA5X/dT+yk342cNaIWQ0HY5QlXlQFJHAkPBDSgOB0 OAikesPfpH9SecVWs38QQ/o2gF79Dwpcl6MlyMFU5zDtTb/xPao4kkDQBjtf1qt0Figf GL+Q== X-Forwarded-Encrypted: i=2; AHgh+RoVWX5y7wMKwEA/HE9Zb5I1khwYIxbQTV5gEva/8vfDSbBxbvvLIolYxRIOveso/H2u3uUMk5wY1uVn@gnusha.org X-Gm-Message-State: AOJu0YzwJ8YfjaTXKuClA8qLqLltmM5gwP6q0Qojv4vYe7lHAC/ExUA+ qm5MNUkXAT2UhWxh3MZoUpRhZLAZ8RM0OYKwCylblJ94dRL9BLbtnssX X-Received: by 2002:a05:6871:c928:b0:459:f9c0:995a with SMTP id 586e51a60fabf-45e0605d6a4mr1198552fac.14.1786375964218; Mon, 10 Aug 2026 08:32:44 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="Aa7YSPQFdOYS5fzWpy89NwAOqxS3tzaxT7IBNFtDehvj2TGHqg==" Received: by 2002:a05:6871:a903:b0:448:7b8c:24ee with SMTP id 586e51a60fabf-459cd1b6accls2451278fac.0.-pod-prod-05-us; Mon, 10 Aug 2026 08:32:38 -0700 (PDT) X-Received: by 2002:a05:6808:c1f3:b0:4a4:9e18:607a with SMTP id 5614622812f47-4b1e7976f58mr1379944b6e.21.1786375958229; Mon, 10 Aug 2026 08:32:38 -0700 (PDT) Received: by 2002:a05:6808:1dcc:b0:495:e116:a399 with SMTP id 5614622812f47-4b197189d26msb6e; Mon, 10 Aug 2026 08:31:07 -0700 (PDT) X-Received: by 2002:a17:90b:3f8d:b0:38f:de97:b06 with SMTP id 98e67ed59e1d1-392cc9048ccmr2617951a91.5.1786375865762; Mon, 10 Aug 2026 08:31:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1786375865; cv=none; d=google.com; s=arc-20260327; b=HuyiFyVEqQYfFmkVCMgY0lYHjSWSzSfXHlG1Yko1PdXaJiLJ8njjpa2o4GlqdAvFo1 GSJ0QXMGrkdt5Dgsb6g4/dfSQ5ELk5x7apxvGVyDcm/cxzfAG0b3iYOjrdtigOPOTO2B WHJi1GBnyUYWDnRsaW5A2tNbC8flKIiaqBH8TjrEQQ1dvbkgjAQbErZLJvjwI1HyxvVa 24/8DtskZxMJeFtNN/cco0LCHQGonBHeXLR/KEvk9PHHDPzQb6ywLG6wQnpgMkG0a1e1 c4R0iSP2rjkt9IVqohI+dK5bV74nKImp5nyjNs8TZrj3a/rdpE/0JuYh/2p85GU+TE0p Ed6Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=mime-version:feedback-id:references:in-reply-to:message-id:subject :cc:from:to:date:dkim-signature; bh=jNdnvAT/Y/C4C3fLenZxES8cq014Q9GXiQb79Czm1Q8=; fh=VafBKbm81sMdCBhZa8cNxSRP186+dHuRkgnGxcDOwXg=; b=ieXBnXIyBAWMjcFsDBNwJaqTl58+bDVWLfYOumuxoIAILrc58MfP4adZeeLn5MjCBk O2r/9JqJTJe1l35V3jhxNgjq8XQT8d9hIREiXSz9LPmismLfN2CBZ9jAfo1X+x13lLmd Zqx1QkZY1gFRNTsvj3jGcN5E38/XgQrqWDUh9AY7wq7gdoToVJx60bx6xL7A/2MwIDax cCj9Sq3VDZDGtCWeSi9Pb7ziUgDyt1ODLOR533gfYzRSMijcTInjlKhdo15h+A8Nodzx sH11C55vG64TX0L5+EO0A18AUl6zPh0cRe7fgYjT1PYDyo1p4yjShqbsS1ZOFasNq3D7 JKzQ==; dara=google.com ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@protonmail.com header.s=protonmail3 header.b=viKpuuwP; spf=pass (google.com: domain of darosior@protonmail.com designates 109.224.244.17 as permitted sender) smtp.mailfrom=darosior@protonmail.com; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=protonmail.com Received: from mail-24417.protonmail.ch (mail-24417.protonmail.ch. [109.224.244.17]) by gmr-mx.google.com with ESMTPS id 98e67ed59e1d1-390b136b4e7si264694a91.0.2026.08.10.08.31.05 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 10 Aug 2026 08:31:05 -0700 (PDT) Received-SPF: pass (google.com: domain of darosior@protonmail.com designates 109.224.244.17 as permitted sender) client-ip=109.224.244.17; Date: Mon, 10 Aug 2026 15:30:57 +0000 To: Murch From: "'Antoine Poinsot' via Bitcoin Development Mailing List" Cc: Bitcoin Development Mailing List Subject: Re: [bitcoindev] Motion to remove Luke Dashjr from BIP Editors Message-ID: In-Reply-To: References: Feedback-ID: 7060259:user:proton X-Pm-Message-ID: 2f64aa25a362328e2425cf88dcb122be8d64edf7 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="b1=_UAFbrVb7MjHQEmt5S93GkiR5IYulD41j4NWUlWoT4" X-Original-Sender: darosior@protonmail.com X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@protonmail.com header.s=protonmail3 header.b=viKpuuwP; spf=pass (google.com: domain of darosior@protonmail.com designates 109.224.244.17 as permitted sender) smtp.mailfrom=darosior@protonmail.com; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=protonmail.com X-Original-From: Antoine Poinsot Reply-To: Antoine Poinsot Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -1.0 (-) --b1=_UAFbrVb7MjHQEmt5S93GkiR5IYulD41j4NWUlWoT4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Murch, I support this. Luke has a long history of abusing whatever position of inf= luence he finds himself in, whether formal or informal. I believe he should= be nowhere near a position of privileged access. Here are a few examples: - In 2014, Luke abused his position as maintainer of the Bitcoin Core packa= ge for Gentoo, silently distributing a modified Bitcoin Core software that = blacklists some addresses. https://bugs.gentoo.org/524512 - In 2021, Luke abused his position as sole maintainer of the BIPs reposito= ry to stall the inclusion of activation parameters for Taproot, with which = he personally disagreed. https://github.com/bitcoin/bips/pull/1104 ; https:= //gnusha.org/taproot-activation/2021-04-18.log - In 2024, Luke abused his position as maintainer of Bitcoin Core's transla= tion platform to sneak in Bitcoin Knots strings, which contributors to the = translation platform complained about. "If the bitcoin-knots ressources are= supposed to belong the a forked project of bitcoin-core (bitcoin-knots), i= would prefer a new project being setup here on Transifex, since its kinda = hijacking the main bitcoin core project and binding translation effort from= members who want to support the bitcoin core project from my impression." = When pushed to stop abusing Bitcoin Core translation contributors' time for= his own project, Luke started claiming that "Bitcoin Knots is part of the = Bitcoin Core project". https://gnusha.org/bitcoin-core-dev/2024-05-02.log - In 2025, Luke abused his position as co-maintainer of the BIPs repository= to fast-track a consensus change proposal he supported (and largely drafte= d the specification of) by unilaterally assigning it a BIP number, after a = long period of inactivity. https://x.com/LukeDashjr/status/1982986197006987= 725 That is more than enough ground to bar him from any privileged position, ye= t there is more. Luke has also been continuously using deceptive language t= o push his own agenda. Besides the examples Jonas Nick already gave in this= thread, Luke claimed his personal Bitcoin Knots fork is part of the Bitcoi= n Core project and ["is produced with the same development process/contribu= tors as Core"](https://gnusha.org/bitcoin-core-dev/2024-05-02.log). He also= claimed the same Bitcoin Core project is malicious and anybody opposing hi= s controversial consensus change is [a supporter of child pornography](http= s://x.com/LukeDashjr/status/2080030401507012841). Removing this person from the position of BIP editor is long overdue. Best regards, Antoine Poinsot On Sunday, August 9th, 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/bitcoinde= v/ad36522e-f479-4ac3-9904-cf00cfa8ec46%40murch.one. --=20 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 e= mail to bitcoindev+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/= AIKO9ttH5zlU3HPFdNEGTKyrPZyjk30rnlBKAszABoIvcHC4t7akCcjwS79XClG7GomNpOSqATM= 8eEQxnj4qx7z8S4I5i-A5BDMoP9VGFJE%3D%40protonmail.com. --b1=_UAFbrVb7MjHQEmt5S93GkiR5IYulD41j4NWUlWoT4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi Murch,
=

<= div style=3D"font-family: Arial, sans-serif; font-size: 14px;">I support th= is. Luke has a long history of abusing whatever position of influence= he finds himself in, whether formal or informal. I believe he should be no= where near a position of privileged access.

Here are a f= ew examples:
  • In 2014, Luke= abused his position as maintainer of the Bitcoin Core package for Gentoo, = silently distributing a modified Bitcoin Core software that blacklists some= addresses. https://bugs.gentoo.org/52451= 2
  • In 2021, Luke abused his position as sole maintainer of the = BIPs repository to stall the inclusion of activation parameters for Taproot= , with which he personally disagreed. https://github.com/bitcoin/bips/pull/1104 ; = https://gnusha.org/tapro= ot-activation/2021-04-18.log
  • In 2024, Luke abused his po= sition as maintainer of Bitcoin Core's translation platform to sneak in Bit= coin Knots strings, which contributors to the translation platform complain= ed about. "If the bitcoin-knots ressources are supposed to belon= g the a forked project of bitcoin-core (bitcoin-knots), i would prefer a ne= w project being setup here on Transifex, since its kinda hijacking the main= bitcoin core project and binding translation effort from members who want = to support the bitcoin core project from my impression." When pushed to sto= p abusing Bitcoin Core translation contributors' time for his own project, = Luke started claiming that "Bitcoin Knots is part of the Bitcoin Core= project". htt= ps://gnusha.org/bitcoin-core-dev/2024-05-02.log
  • = In 2025, Luke abused his position as co-maintainer of the= BIPs repository to fast-track a consensus change proposal he supported (an= d largely drafted the specification of) by unilaterally assigning it a BIP = number, after a long period of inactivity. https://x.com/LukeDashjr/status/1982986197006987725<= /a>
=20
=20
=20

That is more than enough ground to bar him from any privileged position= , yet there is more. Luke has also been continuously using deceptive langua= ge to push his own agenda. Besides the examples Jonas Nick already gave in = this thread, Luke claimed his personal Bitcoin Knots fork is part of the Bi= tcoin Core project and "is produced with the same develop= ment process/contributors as Core". He also claimed the same Bit= coin Core project is malicious and anybody opposing his controversial conse= nsus change is a supporter of child porn= ography.

Removing this person from the position of BIP editor is long overdue.=

<= /div>
Best r= egards,
Antoine Poinsot

On Sunday, August 9th, 2026 at 2:53 PM, M= urch 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 e= mail to bitcoind= ev+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 &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/= AIKO9ttH5zlU3HPFdNEGTKyrPZyjk30rnlBKAszABoIvcHC4t7akCcjwS79XClG7GomNpOSqATM= 8eEQxnj4qx7z8S4I5i-A5BDMoP9VGFJE%3D%40protonmail.com.
--b1=_UAFbrVb7MjHQEmt5S93GkiR5IYulD41j4NWUlWoT4--