Subject: Re: [bitcoindev] [BIP Proposal] Mempool Validation and Relay Policies via User-Defined Scripts

From: "'Aiden McClelland' via Bitcoin Development Mailing List" <[email-masked]>
Date: Mon, 29 Sep 2025 22:21:37 -0600

/dev/fd0,

I appreciate the 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 in a single external binary, running all of the policy validation logic, rather 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. 

Thanks, 
Aiden McClelland

On September 27, 2025 7:22:28 PM MDT, /dev /fd0 <[email-masked]> wrote:
>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 AM Aiden McClelland <[email-masked]> 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 Groups
>> "Bitcoin Development Mailing List" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email-masked].
>> To view this discussion visit
>> https://groups.google.com/d/msgid/bitcoindev/cbdab6fa-93bc-44c9-80f0-6c68c6554f56n%40googlegroups.com
>> <https://groups.google.com/d/msgid/bitcoindev/cbdab6fa-93bc-44c9-80f0-6c68c6554f56n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>

-- 
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 [email-masked].
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/E0178F1A-F2D7-4787-BF52-FA75BFC43EE7%40drbonez.dev.