To be precise, not all Knots clients treat it as spam, and there is joinmarket in case you ever have issues with Whirlpool. Knots is highly configurable. It is not simply an anti-spam implementation.
Discussion
yup. it just lets you control this stuff, and sets reasonable defaults. i don't think that these are advertised in node info messages (support flags) but maybe those will be expanded.
within reason and limited by how desirable the features are, knots is going to leapfrog core eventually because they didn't flip to mainstream development know-it-all policies about features.
people have no way to participate in shaping the behaviour of the p2p network of bitcoin when these options are removed. it has never, before recently, been something that bitcoin core ever did - removing user policy settings for the mempool. i am quite familiar with many of the features and during the time i was working with btcd i saw new things added, both in btcd and core. what core devs have done is regressive. they are going to be punished by users.
and of course, being able to allow stuff like coinjoin and payjoin payments to be relayed will be done, if currently the default is not that, probably it will be changed to a more reasonable approach. and probably Luke is not going to be the only dev maintaining it in the future.
core devs are a nest of vipers at this point. the spooks trying to build for a takeover of bitcoin have badly misunderestimated the determination of the cyberhornets.
Yeah mempool policy flags might be nice to advertise. Good points! Fun fact, Luke already has several dedicated devs on his team now to help out. We cyberhornets have got this 🦾
I get that some knots don't have filters set. But the blunt filter approach was implemented without any thought to the impact of other user's privacy when using long standing consensus op return size.
Is OP_RETURN datacarrier set to 42 bytes the only common setting that gets in the way?
Yes, I believe so. Whirpool uses 46 bytes if not mistaken. Well under the 80 bytes long term consensus, which has been lifted in core v29.
I run v29 with knots peers dropped every ten minutes. I feel like RoninDojo gives me incredible tools for actual spending privacy rather than network filtering. My node is purely privacy focused.
Tor only, soroban routed spends, boltzman tool, xpub lookup, broadcast transactions, self hosted mempool instance, electrum server... for using bitcoin.
Very nice. But you're banning my node which allows 160 byte OP_RETURNs because I think that's the most reasonable limit.
And yeah I agree 80 bytes or 83 technically or whatever would have been a better default.