Delivery-date: Wed, 24 Sep 2025 15:51:06 -0700
Sender: bitcoindev@googlegroups.com
Received-SPF: pass (google.com: domain of gmaxwell@gmail.com designates 2607:f8b0:4864:20::630 as permitted sender) client-ip=2607:f8b0:4864:20::630;
MIME-Version: 1.0
References: <cbdab6fa-93bc-44c9-80f0-6c68c6554f56n@googlegroups.com>
 <CAAS2fgRFP+BJUZR7h01=7=qamD5qEW6OYJikTMR=5RkxTCEMZg@mail.gmail.com> <de4dae19-86f4-4d7a-a895-b48664babbfcn@googlegroups.com>
In-Reply-To: <de4dae19-86f4-4d7a-a895-b48664babbfcn@googlegroups.com>
From: Greg Maxwell <gmaxwell@gmail.com>
Date: Wed, 24 Sep 2025 22:49:11 +0000
Message-ID: <CAAS2fgRABqRe1j6xzW0uhVrDiQnL6x1X6ALzfsJ7w4GztWVeNA@mail.gmail.com>
Subject: Re: [bitcoindev] [BIP Proposal] Mempool Validation and Relay Policies
 via User-Defined Scripts
To: Aiden McClelland <me@drbonez.dev>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Content-Type: multipart/alternative; boundary="000000000000268fd7063f93ddd3"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

--000000000000268fd7063f93ddd3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

So that when the "consistent state" changes as a result of some issue you
can update configs instead of having to update software-- which has
considerable more costs and risks, especially if you're carrying local
customizations as many miners do.


On Wed, Sep 24, 2025 at 8:47=E2=80=AFPM Aiden McClelland <me@drbonez.dev> w=
rote:

> If mempool consistency across the network is all that is important, why
> allow any configuration of mempool relay policies at all?
>
> On Wednesday, September 24, 2025 at 12:47:28=E2=80=AFPM UTC-6 Greg Maxwel=
l wrote:
>
>> This appears to substantially misunderstands the purpose of the mempool
>> broadly in the network-- it's purpose is to model what will get mined.  =
If
>> you're not doing that you might as well set blocks only.
>> Significant discrepancies are harmful to the system and promote
>> centralization and fail to achieve a useful purpose in any case.  What
>> marginal benefits might be provided do not justify building and deployin=
g
>> the technological infrastructure for massive censorship.
>>
>> If you think this is important, I advise you to select another
>> cryptocurrency which is compatible with such authoritarian leanings.  --
>> though I am unsure if any exist since it is such a transparently pointle=
ss
>> direction.
>>
>>
>> On Wed, Sep 24, 2025 at 6:30=E2=80=AFPM Aiden McClelland <m...@drbonez.d=
ev>
>> wrote:
>>
>>> Hi all,
>>>
>>> I'd like to share for discussion a draft BIP to allow for a modular
>>> mempool/relay policy: https://github.com/bitcoin/bips/pull/1985
>>>
>>> I think it could potentially reduce conflict within the community aroun=
d
>>> relay policy, as an alternative to running lots of different node
>>> implementations/forks when there are disagreements.
>>>
>>> I am working on a reference implementation using Bellard's QuickJS, but
>>> it has been almost a decade since I've written C++, so it's slow going =
and
>>> I'm sure doesn't follow best-practices. Once it's working, it can be
>>> cleaned up.
>>>
>>> Thanks,
>>> Aiden McClelland
>>>
>>> --
>>> 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+...@googlegroups.com.
>>> To view this discussion visit
>>> https://groups.google.com/d/msgid/bitcoindev/cbdab6fa-93bc-44c9-80f0-6c=
68c6554f56n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/bitcoindev/cbdab6fa-93bc-44c9-80f0-6=
c68c6554f56n%40googlegroups.com?utm_medium=3Demail&utm_source=3Dfooter>
>>> .
>>>
>> --
> 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/de4dae19-86f4-4d7a-a895-b486=
64babbfcn%40googlegroups.com
> <https://groups.google.com/d/msgid/bitcoindev/de4dae19-86f4-4d7a-a895-b48=
664babbfcn%40googlegroups.com?utm_medium=3Demail&utm_source=3Dfooter>
> .
>

--=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/=
CAAS2fgRABqRe1j6xzW0uhVrDiQnL6x1X6ALzfsJ7w4GztWVeNA%40mail.gmail.com.

--000000000000268fd7063f93ddd3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>So that when the &quot;consistent state&quot; changes=
 as a result of some issue you can update configs instead of having to upda=
te software-- which has considerable more costs and risks, especially if yo=
u&#39;re carrying local customizations as many miners do.</div><div><br></d=
iv></div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"l=
tr" class=3D"gmail_attr">On Wed, Sep 24, 2025 at 8:47=E2=80=AFPM Aiden McCl=
elland &lt;<a href=3D"mailto:me@drbonez.dev">me@drbonez.dev</a>&gt; wrote:<=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex">If mempool consi=
stency across the network is all that is important, why allow any configura=
tion of mempool relay policies at all?<br><br><div class=3D"gmail_quote"><d=
iv dir=3D"auto" class=3D"gmail_attr">On Wednesday, September 24, 2025 at 12=
:47:28=E2=80=AFPM UTC-6 Greg Maxwell wrote:<br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex"><div dir=3D"ltr"><div>This appears to substanti=
ally=C2=A0misunderstands the purpose of the mempool broadly in the network-=
- it&#39;s purpose is to model what will get mined.=C2=A0 If you&#39;re not=
 doing that you might as well set blocks only.=C2=A0 Significant=C2=A0discr=
epancies=C2=A0are harmful to the system and promote centralization=C2=A0and=
 fail to achieve a useful purpose in any case.=C2=A0 What marginal benefits=
 might be provided do not justify=C2=A0building and deploying the technolog=
ical=C2=A0infrastructure=C2=A0for massive censorship.</div><div><br></div><=
div>If you think this is important, I advise you to select another cryptocu=
rrency which is compatible with such authoritarian=C2=A0leanings.=C2=A0 -- =
though I am unsure if any exist since it is such a transparently pointless =
direction.</div><div><br></div></div><br><div class=3D"gmail_quote"></div><=
div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Sep=
 24, 2025 at 6:30=E2=80=AFPM Aiden McClelland &lt;<a rel=3D"nofollow">m...@=
drbonez.dev</a>&gt; wrote:<br></div></div><div class=3D"gmail_quote"><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><div>Hi all,</div><div><br></di=
v><div>I&#39;d like to share for discussion a draft BIP to allow for a modu=
lar mempool/relay policy: <a href=3D"https://github.com/bitcoin/bips/pull/1=
985" rel=3D"nofollow" target=3D"_blank">https://github.com/bitcoin/bips/pul=
l/1985</a><br><br></div><div>I think it could potentially reduce conflict w=
ithin the community around relay policy, as an alternative to running lots =
of different node implementations/forks when there are disagreements.</div>=
<div><br></div><div>I am working on a reference implementation using Bellar=
d&#39;s QuickJS, but it has been almost a decade since I&#39;ve written C++=
, so it&#39;s slow going and I&#39;m sure doesn&#39;t follow best-practices=
. Once it&#39;s working, it can be cleaned up.</div><div><br></div><div>Tha=
nks,</div><div>Aiden McClelland<br></div>

<p></p></blockquote></div><div class=3D"gmail_quote"><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a rel=3D"nofollow">bitcoindev+...@googlegroups.com</a>.<br>
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/cbdab6fa-93bc-44c9-80f0-6c68c6554f56n%40googlegroups.com?utm_med=
ium=3Demail&amp;utm_source=3Dfooter" rel=3D"nofollow" target=3D"_blank">htt=
ps://groups.google.com/d/msgid/bitcoindev/cbdab6fa-93bc-44c9-80f0-6c68c6554=
f56n%40googlegroups.com</a>.<br>
</blockquote></div>
</blockquote></div>

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com" target=
=3D"_blank">bitcoindev+unsubscribe@googlegroups.com</a>.<br>
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/de4dae19-86f4-4d7a-a895-b48664babbfcn%40googlegroups.com?utm_med=
ium=3Demail&amp;utm_source=3Dfooter" target=3D"_blank">https://groups.googl=
e.com/d/msgid/bitcoindev/de4dae19-86f4-4d7a-a895-b48664babbfcn%40googlegrou=
ps.com</a>.<br>
</blockquote></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/CAAS2fgRABqRe1j6xzW0uhVrDiQnL6x1X6ALzfsJ7w4GztWVeNA%40mail.gmail=
.com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/ms=
gid/bitcoindev/CAAS2fgRABqRe1j6xzW0uhVrDiQnL6x1X6ALzfsJ7w4GztWVeNA%40mail.g=
mail.com</a>.<br />

--000000000000268fd7063f93ddd3--