When most nodes reject junk in their mempools, the relay path for spam collapses; spammers must pay far higher fees or bribe miners directly, while miners who ignore the filter face slower propagation and higher orphan risk.
Discussion
Most nodes meaning knots should be the most adopted node version? Up from current 7% to outpacing all other core versions?
Technically, since Bitcoin Core has not merged the PR to remove the "datacarrier" flag, any node version on this list can set it to 0 today, and that will do.
It won’t. Datacarriersize is broken in core. Setting it to zero will do nothing.
Meaning all this "run knots" calls are meaningless apriori?
Nope, datacarriersize=0 works in Knots.
But if most nodes are core, they will still relay the spam and they will end up in the confirmed block regardless of you running knots. We'd need knots to outpace all other core nodes for this to be a affective, no?
Correct. Still, even at 7% it makes a difference, although hard to quantify. Each additional knots node slows a tiny bit the propagation of spam. To achieve maximum efficiency miners should also use knots policy or construct templates that don’t prioritise arbitrary data. Only Ocean does that for now, as far as I know. If their hashrate grows a few times more than it is now, you can expect a meaningful reduction of spam.
Knots went from 1,5% to 7% in one week, express your vote as you see fit man (I know I have already!)
It’s set to 42 by default. It blocks inscription but lets runes. Setting it manually to zero ignores all kinds of arbitrary data.
See this for more info:
Knots is maintained by one person. No thanks.
So is core, it's just tradition that the maintainer doesn't do anything without the rest of the core devs coming to an agreement.
I do agree with you that knots needs to add more official devs in the room.
Will probably happen with the open sats grant monies.