Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 4
Generated: 22:19:16
Your individual mempool policy is irrelevant if it still gets mined. Leave the CSAM FUD out of it. So what if you don't relay it (you are still caching it) but it still lands up on your node anyway when the transaction is mined. Miners don't care about your signal, they are trying to make a profit. They will mine the most profitable, valid transactions and that incentive is what makes Bitcoin work as permissionless, censor resistant money. The ONLY way to prevent this activity is to fork and make these transactions invalid. I'm not telling you not to run knots. Do what you like. Just don't think that you are preventing anything. You're not. Just virtue signaling.
2025-09-21 08:25:56 from 1 relay(s) ↑ Parent
Login to reply

Replies (4)

Because most transactions aren't unusual at the moment. During the ordinals/inscriptions craze a few years ago, those transactions were a high ratio of confirmed transactions. If something like that happens again, and knots filters them, people that want to transact this way will just bypass knots nodes as mempool peers, making a sub network of nodes, just like libre relay did. Like you said, this is a waste of time to argue about. If you don't get it, you haven't thought about it enough.
2025-09-21 09:31:53 from 1 relay(s) ↑ Parent Reply
Currently near 100% are filtering, as they have always been. There are no Core v30 nodes yet. When 5% upgrade to v30 and 95% are running < v30 or Knots, how will the spam propigate to the miners? The majority of nodes are the concensus. Currently the status quo is winning. You haven't convinced us that this change is good for Bitcoin. Running #Knots
2025-09-21 09:56:38 from 1 relay(s) ↑ Parent 1 replies ↓ Reply