public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed

From: Aiden McClelland <me@drbonez•dev>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] [BIP Proposal] Mempool Validation and Relay Policies via User-Defined Scripts
Date: Wed, 24 Sep 2025 11:18:22 -0700 (PDT)	[thread overview]
Message-ID: <cbdab6fa-93bc-44c9-80f0-6c68c6554f56n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 971 bytes --]

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.

[-- Attachment #1.2: Type: text/html, Size: 1411 bytes --]

next             reply	other threads:[~2025-09-24 18:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-24 18:18 Aiden McClelland [this message]
2025-09-24 18:46 ` Greg Maxwell
2025-09-24 18:54   ` Aiden McClelland
2025-09-24 22:49     ` Greg Maxwell
2025-09-24 19:16   ` Chris Guida
2025-09-24 20:01     ` Greg Maxwell

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=cbdab6fa-93bc-44c9-80f0-6c68c6554f56n@googlegroups.com \
    --to=me@drbonez$(echo .)dev \
    --cc=bitcoindev@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox