Delivery-date: Sat, 27 Sep 2025 18:38:09 -0700
Sender: bitcoindev@googlegroups.com
Received-SPF: pass (google.com: domain of alicexbtong@gmail.com designates 2607:f8b0:4864:20::22d as permitted sender) client-ip=2607:f8b0:4864:20::22d;
MIME-Version: 1.0
References: <cbdab6fa-93bc-44c9-80f0-6c68c6554f56n@googlegroups.com>
In-Reply-To: <cbdab6fa-93bc-44c9-80f0-6c68c6554f56n@googlegroups.com>
From: "/dev /fd0" <alicexbtong@gmail.com>
Date: Sun, 28 Sep 2025 06:52:28 +0530
Message-ID: <CALiT-ZqFhMV8VfgOdNyamG4oLgyCL5E7W8s3F9gB_k0ihyUAgA@mail.gmail.com>
Subject: Re: [bitcoindev] [BIP Proposal] Mempool Validation and Relay Policies
 via User-Defined Scripts
To: me@drbonez.dev
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Content-Type: multipart/alternative; boundary="000000000000dc5363063fd25aeb"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

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

Hi Aiden,

There is an easy solution based on my understanding of [transaction
validation][0] although I have not tested it:

1. Add a config option `txnotify` similar to `blocknotify` that executes
commands or script when a new transaction is received from a peer.
2. Add a function `ExecuteTxNotify()` that will run the script provided by
the user in step 1. Script should either return 'accept' for 'reject' and
function would return true/false accordingly.
3. Call `ExecuteTxNotify()` in ` AcceptToMemoryPool()` so that rejected
transactions do not enter the mempool.

[0]: https://bitcoincore.academy/transaction-validation.html

/dev/fd0
floppy disk guy

On Thu, Sep 25, 2025 at 12:00=E2=80=AFAM Aiden McClelland <me@drbonez.dev> =
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 around
> 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 i=
t
> 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+unsubscribe@googlegroups.com.
> To view this discussion visit
> https://groups.google.com/d/msgid/bitcoindev/cbdab6fa-93bc-44c9-80f0-6c68=
c6554f56n%40googlegroups.com
> <https://groups.google.com/d/msgid/bitcoindev/cbdab6fa-93bc-44c9-80f0-6c6=
8c6554f56n%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/=
CALiT-ZqFhMV8VfgOdNyamG4oLgyCL5E7W8s3F9gB_k0ihyUAgA%40mail.gmail.com.

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

<div dir=3D"ltr">Hi Aiden,<div><br></div><div>There is an easy solution bas=
ed on my understanding of [transaction validation][0] although I have not t=
ested it:<br><br>1. Add a config option `txnotify` similar to `blocknotify`=
 that executes commands or script when a new transaction is received from a=
 peer.</div><div>2. Add a function `ExecuteTxNotify()` that will run the sc=
ript provided by the user in step 1. Script should either return &#39;accep=
t&#39; for &#39;reject&#39; and function would return true/false accordingl=
y.</div><div>3. Call `ExecuteTxNotify()` in `

AcceptToMemoryPool()` so that rejected transactions do not enter the mempoo=
l.</div><div><br></div><div>[0]:=C2=A0<a href=3D"https://bitcoincore.academ=
y/transaction-validation.html" target=3D"_blank">https://bitcoincore.academ=
y/transaction-validation.html</a><br><br>/dev/fd0<br>floppy disk guy</div><=
/div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">O=
n Thu, Sep 25, 2025 at 12:00=E2=80=AFAM Aiden McClelland &lt;<a href=3D"mai=
lto:me@drbonez.dev" target=3D"_blank">me@drbonez.dev</a>&gt; wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Hi all,</div><div>=
<br></div><div>I&#39;d like to share for discussion a draft BIP to allow fo=
r a modular mempool/relay policy: <a href=3D"https://github.com/bitcoin/bip=
s/pull/1985" target=3D"_blank">https://github.com/bitcoin/bips/pull/1985</a=
><br><br></div><div>I think it could potentially reduce conflict within the=
 community around relay policy, as an alternative to running lots of differ=
ent node implementations/forks when there are disagreements.</div><div><br>=
</div><div>I am working on a reference implementation using Bellard&#39;s Q=
uickJS, 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>Thanks,</div=
><div>Aiden McClelland<br></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/cbdab6fa-93bc-44c9-80f0-6c68c6554f56n%40googlegroups.com?utm_med=
ium=3Demail&amp;utm_source=3Dfooter" target=3D"_blank">https://groups.googl=
e.com/d/msgid/bitcoindev/cbdab6fa-93bc-44c9-80f0-6c68c6554f56n%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/CALiT-ZqFhMV8VfgOdNyamG4oLgyCL5E7W8s3F9gB_k0ihyUAgA%40mail.gmail=
.com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/ms=
gid/bitcoindev/CALiT-ZqFhMV8VfgOdNyamG4oLgyCL5E7W8s3F9gB_k0ihyUAgA%40mail.g=
mail.com</a>.<br />

--000000000000dc5363063fd25aeb--