Oddbean

And I'm not criticising it, my node also does that. What I'm doing is pointing out the contradiction of calling inscription filtering "censorship", but not 0-fee tx filtering. Both are done in exactly the same way, and neither are an act of censorship. Both inscribers and 0-fee transactors can tweak their node configs and mine themselves, or strike their deals with miners. An Ordisrespector node doesn't get in the way of any of that.

Look inscription filtering nodes have a handicapped fee estimation in return for slightly less data stored in memory and relayed. Running the patch has no effect on what gets into the chain (and downloaded by those nodes as well eventually) as something like 90% of the public nodes would need to filter to achieve anything. If that would happen the inscribors can just use another data structure, possibly even more wasteful.

The thing is I believe we're in a catch-22 situation where an actual supermajority of node runners want to filter inscriptions from their mempools but they don't know how to do it (because BC devs and most node distros aren't making it easy), or they don't even realize they can do it. If I'm right and the situation ends resolving this way the patch will be no more and no less effective than minrelaytxfee. There are 0-fee txs from time to time but they aren't half of the mempool space. Regarding other Bitcoin Script opcode sequences to embed arbitrary bytes in tx: I don't think they even need to be patched. If the network coordinates to reject this first kind of txs it should discourage spammers from trying much further. Detecting these patterns and patching them out is orders of magnitude easier than finding them, then it's just a matter of how fast most nodes patch them out. I won't tell you what to do with Raspiblitz. But your users are sovereign to filter inscriptions, and some of them want to do it. They placed their trust in you, and you can either respect that sovereignty or you can try to get in the way of it. That's just the way it is.

Please don't take me as speaking for what happens with the Raspiblitz project. I am an open-source contributor in my free-time and simply deciding what to work on by it being useful for me or not. There have been no PRs offering patches for Core (which would still need to be reviewed and tested). The dependence on any of these projects is concerning in itself and I think if someone not able to build Bitcoin Core from source is likely not aware of the implications either. BTW the Raspiblitz - close to bare metal - way makes the easiest to make such modifications yourself, but as discussed above to have the supermajority of the node network run some patch is not that straightforward and in my opinion not easier than coming up with a new data structure for data storage.

I’m running a “normal” node and the odisrespector patched node. Both return an estimatesmartfee within 1 sat of each other at 1/6/144 block targets. The mempool difference is usually over 100 blocks.