From: Andrew Poelstra <apoelstra@wpsoftware•net>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] [BIP Proposal] Mempool Validation and Relay Policies via User-Defined Scripts
Date: Thu, 25 Sep 2025 23:33:29 +0000 [thread overview]
Message-ID: <aNXRSd7ygh6NqE1V@mail.wpsoftware.net> (raw)
In-Reply-To: <CAAANnUxBTRzE1PLe9oJU_ukmp3a_y799W_7Ez4rOUOYPhdu26A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]
On Thu, Sep 25, 2025 at 11:52:02AM -0600, Chris Guida wrote:
>
> Anyway, forcing users to relay transactions they consider abusive if they
> want to relay any transactions at all does not seem in keeping with
> bitcoin's ethos, not to mention that it obviously would never work.
>
Once a transaction is in a block, you need to relay the transaction if
you want to relay a block. You cannot pick and choose which parts of a
block you like and which parts are "abusive". This is what it means for
something to be a consensus system.
The purpose of the mempool is to approximate the contents of blocks,
both to help individual node operators (who would otherwise get large
quantities of "surprise transactions" with every block) and to help the
network (which would otherwise have poor propagation properties).
Any sort of filtering beyond that done by miners is contrary to this
purpose of the mempool. This is a technical fact. It has nothing to do
with "bitcoin's ethos", except its ethos as a consensus system, which
directly contradicts your point.
--
Andrew Poelstra
Director, Blockstream Research
Email: apoelstra at wpsoftware.net
Web: https://www.wpsoftware.net/andrew
The sun is always shining in space
-Justin Lewis-Webster
--
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/aNXRSd7ygh6NqE1V%40mail.wpsoftware.net.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-09-26 0:26 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 [this message]
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
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=aNXRSd7ygh6NqE1V@mail.wpsoftware.net \
--to=apoelstra@wpsoftware$(echo .)net \
--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