I would suggest reading more about it particularly since Bitcoin Core 30 was released today. There have been a lot of discussions about the technical reasons vs a lot of FUD (as achow references above). I have read it all and would urge everyone else to do so to if they want to see more than soundbites. (I am running it, I just built it - as I always do - if anyone cares about my opinion).
Simply saying "read more" and not expanding on yoiur own view is not a valid point. Or should I just tell you to also read more?
The fact are as follows:
When Segwit was exploited by spammers, core did nothing. Told us they can't do anything, and even if they could, they shouldn't.
When Taproot was exploited by spammers, core did nothing. Told us they can't do anything, and even if they could, they shouldn't.
And now, after having done nothing about it, they finally do something: attempt to create a new way to spam bitcoin after having done nothing about the existing ways to spam.
When spam miners (Mara and F2Pool) offer a service to spammers so they can bypass the nodes, core decided that the problem is not spammers and spam miners. No, the problem is nodes who try to stop spam. Our ability to stop spam must be stopped! We are the problem?
When spam miners find a block, it takes more time to propagate that block because nodes tasked to verify that block take longer because they need to request and verify the spam transactions they did not include in their mempool. Longer propagation time is a huge risk to spam miners. Not so much for miners who respect mempool policy.
Core tells us they need to remove our spam filters to speed up propagation time. What they don't tell us is that it's only speeding up propagation time of blocks filled with garbage.
Core doesn't think spam is a problem. They think the problem comes from those fighting against the spam and filth.
