From: "/dev /fd0" <alicexbtong@gmail•com>
To: me@drbonez•dev
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] [BIP Proposal] Mempool Validation and Relay Policies via User-Defined Scripts
Date: Sun, 28 Sep 2025 06:52:28 +0530 [thread overview]
Message-ID: <CALiT-ZqFhMV8VfgOdNyamG4oLgyCL5E7W8s3F9gB_k0ihyUAgA@mail.gmail.com> (raw)
In-Reply-To: <cbdab6fa-93bc-44c9-80f0-6c68c6554f56n@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 2331 bytes --]
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 <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 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-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 bitcoindev+unsubscribe@googlegroups•com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CALiT-ZqFhMV8VfgOdNyamG4oLgyCL5E7W8s3F9gB_k0ihyUAgA%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 3352 bytes --]
prev parent reply other threads:[~2025-09-28 1:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 18:18 Aiden McClelland
2025-09-24 18:46 ` Greg Maxwell
2025-09-24 18:54 ` Aiden McClelland
2025-09-24 22:49 ` Greg Maxwell
2025-09-25 9:21 ` yes_please
2025-09-25 20:03 ` Greg Maxwell
2025-09-25 20:51 ` Aiden McClelland
2025-09-25 21:14 ` Greg Maxwell
2025-09-25 21:25 ` Aiden McClelland
2025-09-25 21:51 ` Greg Maxwell
2025-09-26 2:06 ` Chris Riley
2025-09-26 2:17 ` Aiden McClelland
2025-09-26 2:28 ` Chris Riley
2025-09-25 17:52 ` Chris Guida
2025-09-25 20:46 ` Greg Maxwell
2025-09-25 21:02 ` Chris Guida
2025-09-25 23:33 ` Andrew Poelstra
2025-09-26 7:58 ` Garlo Nicon
2025-09-27 14:44 ` 'OJ' via Bitcoin Development Mailing List
2025-09-27 16:49 ` Bryan Bishop
2025-09-24 19:16 ` Chris Guida
2025-09-24 20:01 ` Greg Maxwell
2025-09-25 2:20 ` bigshiny
2025-09-25 14:33 ` Luke Dashjr
2025-09-28 1:22 ` /dev /fd0 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALiT-ZqFhMV8VfgOdNyamG4oLgyCL5E7W8s3F9gB_k0ihyUAgA@mail.gmail.com \
--to=alicexbtong@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
--cc=me@drbonez$(echo .)dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox