From: Luke Dashjr <luke@dashjr•org>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] [BIP Proposal] Mempool Validation and Relay Policies via User-Defined Scripts
Date: Thu, 25 Sep 2025 10:33:11 -0400 [thread overview]
Message-ID: <b5688bf9-f872-4655-ae68-8876348479e1@dashjr.org> (raw)
In-Reply-To: <cbdab6fa-93bc-44c9-80f0-6c68c6554f56n@googlegroups.com>
On 9/24/25 14:18, Aiden McClelland wrote:
> 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
Javascript implementations are notoriously bad at safe sandboxing. The
most well-maintained, V8, has security vulnerabilities fixed nearly
every month.
Additionally, using the filesystem as such is a "power user" task, while
many people running nodes are (or should be) ordinary end users who
don't necessarily understand these concepts.
I think a better path forward would be some kind of simple
domain-specific language. This way it could be designed to make abuse
(eg, for censorship) difficult, have an end-user friendly interface, and
allow for transparent native optimisations (or even profile at runtime
to reorder classifiers as optimal for the fastest reject).
However, I do understand this increases the complexity significantly,
and so your concept may be "good enough" in practice, at least as an
initial proof-of-concept. But I would finish and test that POC in the
real world first, before exploring a BIP for the interface.
Luke
--
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/b5688bf9-f872-4655-ae68-8876348479e1%40dashjr.org.
prev parent reply other threads:[~2025-09-25 21:24 UTC|newest]
Thread overview: 22+ 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-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 [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=b5688bf9-f872-4655-ae68-8876348479e1@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoindev@googlegroups.com \
/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