I understand the difference just fine. You can configure your code to filter these transactions all you want but they are legitimate transactions and whether you censor them or not, they will be able validated by nodes unless you create a fork. That's my point. The only way to stop them, which is what Luke suggests as he says they're exploitative, is to hard fork or uasf.

Reply to this note

Please Login to reply.

Discussion

A parameter change is not a fork.

I said to stop them. Not to filter them on your personal node.