ok sounds like you do indeed think that having a wild west type situation where people could apply different filters to their mempool is the preferable condition got it ❤️ (maybe update the kung fu panda vid to show him updating his filters between attacks 🤷)

> sounds like you do indeed think that having a wild west type situation where people could apply different filters to their mempool is the preferable condition You act like that's an unusual opinion. Boy, are you in for a surprise if you ever read bitcoin core's policy.cpp file

GitHub

bitcoin/src/policy/policy.cpp at master · bitcoin/bitcoin

Bitcoin Core integration/staging tree. Contribute to bitcoin/bitcoin development by creating an account on GitHub.

I'll give you a hint:

I didn't express my own opinion. I was asking yours. But since sorta ask (in that backhanded way), I'm able to simultaneously BOTH 1) want to conveniently be able to adjust policy on my node and 2) recognize spam propagation is a larger program that user-level filters dont adequately solve. and yeah one of my nodes has been Knots for a couple years. it doesn't filter Whirlpool CJ txs from its mempool. and the vast number of users will run defaults or apply filter parameters blindly from a centralized platform. you pretending like that isn't true doesn't help anybody.

> or apply filter parameters blindly from a centralized platform yeah, that sure sounds like knotsis your typical knotsi would never willingly stop using the default software and run something nonstandard instead -- definitely not