Dealing with Nodes Running Knots

Been messing around with a script that checks peer info every hour. If it sees "Knots" in the subver, I kick that node and ban its IP. Why waste time with nodes that aren’t giving me a proper mempool? Just seems pointless to me.

You could make it a simple one or two-line change to your node. Just have it disconnect any peers with that subver right away. Fun exercise if you’ve never modified your node before. Probably not for everyone, but if it’s just you, who cares? Just be cautious about causing a network split.

@gmaxwell Yeah, the script I made was pretty basic. I’ll try your method though. Honestly, I’m over Knots users. They’ve had their warnings. It’s like the folks who jumped on the BSV train, just heading for disaster.

Love the idea of schooling Knotzis with info theory. Nice merits there! If I remember right, Bitcoin Core connects to some nodes just for blocks, not mempool stuff. But blocking them entirely sounds more entertaining. Just saw that Luke's DNS seed got yanked from Bitcoin Core too, which is hilarious.

Didn’t know they pulled the DNS seed. Props to the core devs! No point in allowing connections from Knot nodes. Blocking them means they won’t accidentally get something inappropriate from my node, so that’s a win. If everyone did this, they’d only have their own transactions in the mempool, no censorship needed.

You could just limit blocking to blocksonly connections. They’re not great for block propagation since they miss transactions, but it avoids partitioning issues. If lots of people did this, it’d be a safer option.