# Proposal: Pluggable Filter Framework

**URL:** <https://delvingbitcoin.org/t/proposal-pluggable-filter-framework/2064>\
**Category:** Protocol Design\
**Tags:** bitcoin-core\
**Created:** [October 15, 2025, 3:42am UTC](https://delvingbitcoin.org/t/proposal-pluggable-filter-framework/2064 "2025-10-15T03:42:28Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![AdamISZ](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/adamisz/32/418_2.png) [@AdamISZ](https://delvingbitcoin.org/u/AdamISZ)\
**Post date:** [October 15, 2025, 3:55pm UTC](https://delvingbitcoin.org/t/proposal-pluggable-filter-framework/2064/6 "2025-10-15T15:55:05Z")

</div>

> [@1440000bytes](#):
>
> I don’t think this is true for several policies used in bitcoin core.

You are talking about the purpose of certain policies. That doesn’t contradict what I’m saying about the point of the mempool. Those are two different things.

Still you’re right to point out that simply “you might want to change things because you’re resource constrained” is overly simplistic. The various anti-DOS measures aren’t _quite_ that trivial, but still I don’t think any of that changes the fundamental point I was making about decentralization and the purpose of mempools.

---

_[View the full topic](https://delvingbitcoin.org/t/proposal-pluggable-filter-framework/2064)._