What about the consequences of slower verification of blocks for the whole network of nodes, due to Knots nodes not being able to start validation because they dismissed economically relevant valid transactions?
Longer validation can cause competing blocks more likely.
The fee estimatiom problem is also a well-known predictable effect of purging mempools this way.
Yet another serious issue is to burden all nodes with substantially more validation _for ever_ with inscriptions in pubkeys. In contrast, op_return can be ignored in validation.
I think these side effects dwarf your concerns about temporary RAM benefits.
In addition, the CSAM arguments have existed for long as well and, though not a lawyer and all, but Knots nodes will store these as well and relay them as valid blocks to other nodes, so there is no benefit I see here either.
I am almost sure you knew these arguments already. Failing to steelman the other side is a mistake. Do you want to get closer to truth or justify an outcome?
The only "moral" of bitcoin is economic incentives, strictly speaking.
People will argue on subjective morals and semantics for ever. What we strive to achieve with money is as close to objectiveness as possible though.
Wishful thinking with ignorance towards reality caused the fiat system in the first place.
Camouflaging this with morality and a veneer of certainty instead of focusing on error-correction is just an appeal to authority and a path leading back to a fiat.
Login to reply
Replies (1)
> What about the consequences of slower verification of blocks for the whole network of nodes
Only blocks containing spam are delayed. This is a desirable outcome because it provides a monetary incentivize for miners to ignore spam.
> The fee estimatiom problem is also a well-known predictable effect of purging mempools this way
It is not a problem because nodes don't look at the mempool when estimating fees.
> Yet another serious issue is to burden all nodes with substantially more validation _for ever_ with inscriptions in pubkeys. In contrast, op_return can be ignored in validation.
I personally think the "cure" (raising op_return to 100kb) is worse than the disease. Very few protocols store data in pubkeys. The ones that do are unpopular and rarely used. Storing arbitrary data on the blockchain is a significant abuse of the blockchain, and relaxing op_return will, I suspect, invite even more of it, thus doing more harm than the comparatively small problem it supposedly fixes.