From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Sun, 09 Aug 2026 15:35:26 -0700 Received: from mail-ot1-f63.google.com ([209.85.210.63]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1wtC73-0002S9-Jv for bitcoindev@gnusha.org; Sun, 09 Aug 2026 15:35:26 -0700 Received: by mail-ot1-f63.google.com with SMTP id 46e09a7af769-7f18aff8226sf1383829a34.2 for ; Sun, 09 Aug 2026 15:35:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20251104; t=1786314919; x=1786919719; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:content-type :mime-version:subject:references:in-reply-to:message-id:to:from:date :sender:from:to:cc:subject:date:message-id:reply-to:content-type; bh=UErIScH6uw9cDvZIfUZBvvk6VtjCmcXplOij8+MeKQw=; b=kMg8TjmvrcZJClEk961ceFgoiPOdmY2V/Yf/Vgepmkax2d2v9O9GYKN6ir0ofAkxOE YQvVcHN22yyrjUDIDY7DuKOwT0YSx0LHNWDZy793ufTpEmA5Z5P5TUBUVumWBpGZhR4w EMwKtNGbJMo0fQysAP0oJFPsxLH6E3kFspXK2plt6kzaO4336GLlVnnf5h6M1NOXQRAh 4XYnWRpmwp2wMutBK9jUAQn3SnSiXQWdVrSt/PMwPXTOsj0XdE73wt5ZUq9SjRusNLuX i3QNvyg/SKdpAXnxaVeUNXWLk4k54hiduihFgw0zq7/DTkl72xL7B3ofVFRqC6kEmeJz DamQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1786314919; x=1786919719; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:content-type :mime-version:subject:references:in-reply-to:message-id:to:from:date :from:to:cc:subject:date:message-id:reply-to:content-type; bh=UErIScH6uw9cDvZIfUZBvvk6VtjCmcXplOij8+MeKQw=; b=omyMXoztKLNZrZtrKyATY3DBMiv0AIOuxNztUil+aNFGwXQpwS0e3w0f6p5wOMXc5G xhALLQ7Dr/bkJ6EsPDD07C5fP1oNEhmKt04lKPuLBd2siZlaMR828XvrafzN8P90Cl2u /JM1/0Zuta8NkYQCTjVxltvrabeuBxTQ/IJ14a1Hd9rqxGI2nmyF+HpPsmArIa8WCCS1 zAkdGtQtNHmew7XgbnD6eht4tgJjGemo64t8elLgih3Sr0E2p4sKJjix8aRv1JT4OqxI /PmgOUnznnZG0SGxSBkhSW+fialPWU048qc54HacFPYNzZivVjKFE6UUVxU5TXXT+NJC uWlg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1786314919; x=1786919719; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:content-type :mime-version:subject:references:in-reply-to:message-id:to:from:date :x-beenthere:x-gm-message-state:sender:from:to:cc:subject:date :message-id:reply-to:content-type; bh=UErIScH6uw9cDvZIfUZBvvk6VtjCmcXplOij8+MeKQw=; b=jlJuL4TUkCa9eEAormm8H7AlODoMEK6jBW7SrrGLneFKn+bGvqyEdI0YgUd6dGgmbo 39Yy/gI24jv+S9wrSQz/ydEjlyyWD40GcNFM4Ehn97qzvg1leI4gIqkr0rNESS/Ajjnx MpeW8oAj96c1pVTzXHUCQ/csyL2Qk8OCERPd2OaaKkVfDdRY1bLJ2Xx4i2WXFxruSm6f cAIlxrfO9nwGiWM4ZnKEwPdiSBw5eKNi7coH29PP4h1Pqac2wRBT+U0sTU9Km4gtfqvM GvoNoV3k9OOJzR1DoNtuWYtaMt25XjA/RBb4yf4NpDn9T8LSn9gg4Vzrxn5dyjah7/qc In6Q== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AHgh+Rr2SUangSgai3RgPFnV9qdQsBmw47VUQodw5pGbVbR3wJY61iRY1E+v2zygSjwDLyF9WUPoy4aES8s2@gnusha.org X-Gm-Message-State: AOJu0Yy8gOizUnwXTCeSWDZm5URip0qqDoIT7NBs720+Rr8aS8rKBJM+ LfQxGDFtmcyxliHCSkQT8Ynbyt7XEG1TbZ8pEviAxb+3iVwTHPCcycmg X-Received: by 2002:a05:6820:1792:b0:6a3:a335:1ccd with SMTP id 006d021491bc7-6ae96c7e7c5mr21034741eaf.8.1786314919213; Sun, 09 Aug 2026 15:35:19 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="Aa7YSPSJfa6+rm0oBBCIF+r96SVkuo+5v5uRXU1f8ieJJLaG+g==" Received: by 2002:a05:6870:65a8:b0:456:d5f3:3538 with SMTP id 586e51a60fabf-459cd04c8b8ls2049121fac.0.-pod-prod-03-us; Sun, 09 Aug 2026 15:35:13 -0700 (PDT) X-Received: by 2002:a05:6808:23c1:b0:4a1:296:adec with SMTP id 5614622812f47-4afae1299c7mr22073942b6e.15.1786314913469; Sun, 09 Aug 2026 15:35:13 -0700 (PDT) Received: by 2002:a05:690c:e194:20b0:81e:11b4:1172 with SMTP id 00721157ae682-82325401bbems7b3; Sun, 9 Aug 2026 13:42:59 -0700 (PDT) X-Received: by 2002:a05:690c:c4e9:b0:814:7238:390f with SMTP id 00721157ae682-820222beca5mr234645477b3.10.1786308179306; Sun, 09 Aug 2026 13:42:59 -0700 (PDT) Date: Sun, 9 Aug 2026 13:42:58 -0700 (PDT) From: Michael Tidwell To: Bitcoin Development Mailing List Message-Id: <3341dee7-216d-40e6-b1b5-dfd32b3ccb1dn@googlegroups.com> In-Reply-To: <9e5a9595-d719-436b-ada0-a09900f1fcb9@mattcorallo.com> References: <9e5a9595-d719-436b-ada0-a09900f1fcb9@mattcorallo.com> Subject: Re: [bitcoindev] Motion to remove Luke Dashjr from BIP Editors MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_38426_733937742.1786308178922" X-Original-Sender: mtidwell021@gmail.com 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: -0.5 (/) ------=_Part_38426_733937742.1786308178922 Content-Type: multipart/alternative; boundary="----=_Part_38427_635227902.1786308178922" ------=_Part_38427_635227902.1786308178922 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Luke,=20 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=20 down yourself than get forced out through this informal process (Frankly=20 it's embarrassing that this seems appropriate given your historic=20 contributions). I believe it's apparent to most, (and I hope to you), that= =20 it's unlikely you would be working effectively with Core from here. There=E2=80=99s going to be a need for strong technical leader around decen= tralized=20 mining at Ocean, and for a solid BIP editor if that new PoW chain happens.= =20 Whoever takes that on is going to need real conviction. Good luck with=20 whatever comes next and whatever happens. Looking forward to what you=20 building more amazing things at Ocean (again being genuine), so far y'all= =20 have made a splash, looking forward to the waves! (get it? because water=20 and ocean.. anyways). Anyways for "communication", make sure you haven't accidentally blocked=20 someone who you think has stopped communicating with you.. for instance if= =20 I wasn't blocked, I would have just sent this as a DM. Thanks, Tidwell On Sunday, August 9, 2026 at 3:50:52=E2=80=AFPM 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, > >=20 > > I recommend that Luke Dashjr be removed from the position of BIP Editor= . > >=20 > > Over the past several years, Luke has been at the center of many=20 > contentious disputes within the=20 > > Bitcoin ecosystem, and this week a new forkcoin spun out of Bitcoin=20 > under his leadership. > >=20 > > More specifically, Luke was heavily involved in the creation and=20 > implementation of BIP110, the=20 > > proposal that led to the fork. During that process, he also exercised= =20 > his authority as a BIP Editor=20 > > inconsistently with the established editorial process unfairly favoring= =20 > the proposal he was involved=20 > > in. For example, he attempted to assign a BIP number to the draft=20 > publicly on Twitter before the=20 > > proposal had been discussed on the mailing list, and he merged a PR=20 > updating the BIP within minutes=20 > > of the PR being opened. > >=20 > > The latter is particularly notable given that Luke has otherwise made= =20 > hardly any contributions to=20 > > the day-to-day work of the BIP Editors since the additional editors=20 > began serving in April 2024: he=20 > > left fewer than 1% of the BIP Editor comments in the repository since= =20 > then, and the merge action of=20 > > this PR was his first since May 2024. > >=20 > > Communication between Luke and other BIP Editors had already broken dow= n=20 > last year, following a=20 > > discussion about his attempt to side-step the process by prematurely=20 > assigning a BIP number out of=20 > > band. > >=20 > > Taken together, I believe these circumstances raise serious concerns=20 > about Luke continuing to hold=20 > > editorial authority. In particular: > >=20 > > - he has exercised his editorial privileges in a manner that raises=20 > 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= =20 > evolve into a hard fork=20 > > represents a complete departure from the Bitcoin development ecosystem;= =20 > and > > - trust, communication, and coordination with the other BIP Editors hav= e=20 > broken down. > >=20 > > For these reasons, I motion that Luke be removed as a BIP Editor. > >=20 > > Murch > >=20 > > --=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/= 3341dee7-216d-40e6-b1b5-dfd32b3ccb1dn%40googlegroups.com. ------=_Part_38427_635227902.1786308178922 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Luke,

Thanks for the years of hard work. Genuinely appreciat= ed.

It's my opinion this is the right move. And, it would be bet= ter 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.
<= br />There=E2=80=99s going to be a need for strong technical leader around = decentralized mining at Ocean, and for a solid BIP editor if that new PoW c= hain 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 wate= r and ocean.. anyways).

Anyways for "communication", make sure y= ou haven't accidentally blocked someone who you think has stopped communica= ting=C2=A0with you.. for instance if I wasn't blocked, I would have just se= nt this as a DM.

Thanks,
Tidwell

On Sunday, August 9, 2026 at 3:5= 0:52=E2=80=AFPM 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,
>=20
> I recommend that Luke Dashjr be removed from the position of BIP E= ditor.
>=20
> Over the past several years, Luke has been at the center of many c= ontentious disputes within the=20
> Bitcoin ecosystem, and this week a new forkcoin spun out of Bitcoi= n under his leadership.
>=20
> More specifically, Luke was heavily involved in the creation and i= mplementation of BIP110, the=20
> proposal that led to the fork. During that process, he also exerci= sed his authority as a BIP Editor=20
> inconsistently with the established editorial process unfairly fav= oring the proposal he was involved=20
> in. For example, he attempted to assign a BIP number to the draft = publicly on Twitter before the=20
> proposal had been discussed on the mailing list, and he merged a P= R updating the BIP within minutes=20
> of the PR being opened.
>=20
> The latter is particularly notable given that Luke has otherwise m= ade hardly any contributions to=20
> the day-to-day work of the BIP Editors since the additional editor= s began serving in April 2024: he=20
> left fewer than 1% of the BIP Editor comments in the repository si= nce then, and the merge action of=20
> this PR was his first since May 2024.
>=20
> Communication between Luke and other BIP Editors had already broke= n down last year, following a=20
> discussion about his attempt to side-step the process by premature= ly assigning a BIP number out of=20
> band.
>=20
> Taken together, I believe these circumstances raise serious concer= ns about Luke continuing to hold=20
> editorial authority. In particular:
>=20
> - he has exercised his editorial privileges in a manner that raise= s conflict-of-interest concerns;
> - he has contributed little to the ongoing workload of the BIP Edi= tors;
> - his recent championing of a contentious soft fork that now appea= rs to evolve into a hard fork=20
> represents a complete departure from the Bitcoin development ecosy= stem; and
> - trust, communication, and coordination with the other BIP Editor= s have broken down.
>=20
> For these reasons, I motion that Luke be removed as a BIP Editor.
>=20
> Murch
>=20

--
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/bitcoind= ev/3341dee7-216d-40e6-b1b5-dfd32b3ccb1dn%40googlegroups.com.
------=_Part_38427_635227902.1786308178922-- ------=_Part_38426_733937742.1786308178922--