Delivery-date: Mon, 29 Sep 2025 23:22:18 -0700
Received-SPF: pass (google.com: domain of me@drbonez.dev designates 198.54.127.87 as permitted sender) client-ip=198.54.127.87;
Date: Mon, 29 Sep 2025 22:21:37 -0600
From: "'Aiden McClelland' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: /dev /fd0 <alicexbtong@gmail.com>
CC: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] [BIP Proposal] Mempool Validation and Relay Policies
 via User-Defined Scripts
User-Agent: K-9 Mail for Android
In-Reply-To: <CALiT-ZqFhMV8VfgOdNyamG4oLgyCL5E7W8s3F9gB_k0ihyUAgA@mail.gmail.com>
References: <cbdab6fa-93bc-44c9-80f0-6c68c6554f56n@googlegroups.com> <CALiT-ZqFhMV8VfgOdNyamG4oLgyCL5E7W8s3F9gB_k0ihyUAgA@mail.gmail.com>
Message-ID: <E0178F1A-F2D7-4787-BF52-FA75BFC43EE7@drbonez.dev>
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary=----P2AXTRH4BLPNC787Y02D94XDLYV4AC
Content-Transfer-Encoding: 7bit
Autocrypt: addr=me@drbonez.dev; prefer-encrypt=mutual; keydata=
 mDMEaNcksxYJKwYBBAHaRw8BAQdAgpcI3hOExv1njCt+zJoYBartdyk4SKiqSIy3+9tcpOK0IUFp
 ZGVuIE1jQ2xlbGxhbmQgPG1lQGRyYm9uZXouZGV2PoiJBBMWCAAxFiEEtBbA5nud8/FxhICufP/a
 QcpmBWoFAmjXJLMCGwMECwkIBwUVCAkKCwUWAgMBAAAKCRB8/9pBymYFamtoAQDebf0jXVUtKKur
 70LUB5+dmHndsIeGpVgGEs5rDGhelwD7BTgcermFsaPWXg6p7RjQ9cSCaGdDIp/87QVAy0lMeAy4
 OARo1ySzEgorBgEEAZdVAQUBAQdATE1CS5FypyXAJdO+9a1LYQR1rgfuEgeChUcYSOUme3oDAQgH
 iHgEGBYIACAWIQS0FsDme53z8XGEgK58/9pBymYFagUCaNckswIbDAAKCRB8/9pBymYFavYZAP95
 dgwYia0VN0Cy75K4+pxiuaG4UpEGdY0v+bgN7zbLVQEA28muMHpEW/b3gtR+W6MaONTQuGFy61Sk
 QaHWmrqyNg8=
Reply-To: Aiden McClelland <me@drbonez.dev>
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

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

/dev/fd0,

I appreciate the comments. A txnotify solution could work, although it lose=
s a lot of the modularity and sandboxing of what I'm proposing. It would pr=
obably result in a single external binary, running all of the policy valida=
tion logic, rather than a bundle of scripts you can mix and match. And it m=
ight encourage solutions that involve fetching relay policies over the inte=
rnet, which is probably not ideal. Ideally, updating policy should require =
user action.=20

Thanks,=20
Aiden McClelland


On September 27, 2025 7:22:28 PM MDT, /dev /fd0 <alicexbtong@gmail.com> wro=
te:
>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 =
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 Group=
s
>> "Bitcoin Development Mailing List" group.
>> To unsubscribe from this group and stop receiving emails from it, send a=
n
>> email to bitcoindev+unsubscribe@googlegroups.com.
>> To view this discussion visit
>> https://groups.google.com/d/msgid/bitcoindev/cbdab6fa-93bc-44c9-80f0-6c6=
8c6554f56n%40googlegroups.com
>> <https://groups.google.com/d/msgid/bitcoindev/cbdab6fa-93bc-44c9-80f0-6c=
68c6554f56n%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/=
E0178F1A-F2D7-4787-BF52-FA75BFC43EE7%40drbonez.dev.

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

<html><head></head><body><div dir=3D"auto">/dev/fd0,<br><br>I appreciate th=
e comments. A txnotify solution could work, although it loses a lot of the =
modularity and sandboxing of what I'm proposing. It would probably result i=
n a single external binary, running all of the policy validation logic, rat=
her than a bundle of scripts you can mix and match. And it might encourage =
solutions that involve fetching relay policies over the internet, which is =
probably not ideal. Ideally, updating policy should require user action. <b=
r><br>Thanks, <br>Aiden McClelland<br><br></div><br><br><div class=3D"gmail=
_quote"><div dir=3D"auto">On September 27, 2025 7:22:28 PM MDT, /dev /fd0 &=
lt;alicexbtong@gmail.com&gt; wrote:</div><blockquote class=3D"gmail_quote" =
style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 20=
4); padding-left: 1ex;">
<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 'accept' f=
or 'reject' and function would return true/false accordingly.</div><div>3. =
Call `ExecuteTxNotify()` in `

AcceptToMemoryPool()` so that rejected transactions do not enter the mempoo=
l.</div><div><br></div><div>[0]:&nbsp;<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'd like to share for discussion a draft BIP to allow for a =
modular mempool/relay policy: <a href=3D"https://github.com/bitcoin/bips/pu=
ll/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 com=
munity around relay policy, as an alternative to running lots of different =
node implementations/forks when there are disagreements.</div><div><br></di=
v><div>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 cl=
eaned 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 "=
Bitcoin Development Mailing List" 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>
</blockquote></div></body></html>

<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/E0178F1A-F2D7-4787-BF52-FA75BFC43EE7%40drbonez.dev?utm_medium=3D=
email&utm_source=3Dfooter">https://groups.google.com/d/msgid/bitcoindev/E01=
78F1A-F2D7-4787-BF52-FA75BFC43EE7%40drbonez.dev</a>.<br />

------P2AXTRH4BLPNC787Y02D94XDLYV4AC--