From: Chris Guida <chrisguida@gmail•com>
To: Greg Maxwell <gmaxwell@gmail•com>
Cc: me@drbonez•dev,
Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] [BIP Proposal] Mempool Validation and Relay Policies via User-Defined Scripts
Date: Wed, 24 Sep 2025 13:16:03 -0600 [thread overview]
Message-ID: <CAAANnUzf4SfgcixLuS0Uwe6pNyFWAtufzLuJrDdpnBwyU2bU7A@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgRFP+BJUZR7h01=7=qamD5qEW6OYJikTMR=5RkxTCEMZg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4280 bytes --]
Hi Aiden -
This is a very interesting proposal! It certainly has the potential to
reduce tension over mempool policy by removing decisions over mempool
policy from bitcoin core's maintainers, who, if I understand correctly, are
not very interested in being the arbiters of policy over the bitcoin
network anyway.
This seems like an excellent way to let users decide which transactions
they will relay and which ones they won't, which core maintainers have no
control over anyway.
I'm cautiously optimistic that this proposal can help break the logjam.
Greg -
I'm somewhat confused as to your reaction here. This proposal democratizes
access to filter authorship; it does not seem in any way "authoritarian" to
me. On the contrary, this proposal seems less "authoritarian" than the
current state of affairs, which is that the core maintainers decide all the
defaults.
>If you're not doing that you might as well set blocks only.
Why is running blocksonly more beneficial than relaying some transactions
and not others? Why does bitcoin core not default to blocksonly (or no
filters at all) if partial filtration is undesirable?
Kind regards,
--Chris Guida
On Wed, Sep 24, 2025 at 12:47 PM Greg Maxwell <gmaxwell@gmail•com> wrote:
> This appears to substantially misunderstands the purpose of the mempool
> broadly in the network-- it's purpose is to model what will get mined. If
> you're not doing that you might as well set blocks only.
> Significant discrepancies are harmful to the system and promote
> centralization and fail to achieve a useful purpose in any case. What
> marginal benefits might be provided do not justify building and deploying
> the technological infrastructure for massive censorship.
>
> If you think this is important, I advise you to select another
> cryptocurrency which is compatible with such authoritarian leanings. --
> though I am unsure if any exist since it is such a transparently pointless
> direction.
>
>
> On Wed, Sep 24, 2025 at 6:30 PM 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/CAAS2fgRFP%2BBJUZR7h01%3D7%3DqamD5qEW6OYJikTMR%3D5RkxTCEMZg%40mail.gmail.com
> <https://groups.google.com/d/msgid/bitcoindev/CAAS2fgRFP%2BBJUZR7h01%3D7%3DqamD5qEW6OYJikTMR%3D5RkxTCEMZg%40mail.gmail.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/CAAANnUzf4SfgcixLuS0Uwe6pNyFWAtufzLuJrDdpnBwyU2bU7A%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 5799 bytes --]
next prev parent reply other threads:[~2025-09-24 20:47 UTC|newest]
Thread overview: 6+ 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-24 19:16 ` Chris Guida [this message]
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=CAAANnUzf4SfgcixLuS0Uwe6pNyFWAtufzLuJrDdpnBwyU2bU7A@mail.gmail.com \
--to=chrisguida@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
--cc=gmaxwell@gmail$(echo .)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