Is OP_RETURN datacarrier set to 42 bytes the only common setting that gets in the way?
Discussion
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.