You seem to think this is some kind of smoking gun but it isn't.
Would you rather have Citrea (and potential other protocols like it) put data in fake pubkeys?
Discussion
It is smoking gun. Why should we exuse one bad action with another one?
As far as I have heard there are other companies that make their technology in a way that 82 Bytes of OP_RETURN is enough.
Bitcoin is not a storage for arbitrary data.
You are trying to excuse Core devs' bad decisions no matter what. You tried excusing CSAM with the Four Horsmen.
You don't mind spam on Bitcoin. You mention that if Citrea don't abuse Bitcoin in one way they will do in another so let them just do whatever they want.
And now you are focused on Lukes argumentation. Luke has fixed inscriptions spam. Its Core devs who rejected it intentionally and we have 30GB+ of spam
for 2+ years. And fees alone have not stopped them.
You didn’t answer my question.
And Samson is giving the answer as well that you can't fix fake pubkeys with OP_RETURN. Its just not the fix for them. Everyone can still use them.
Now you’re outsourcing your thinking rather than answering the question. Soit.
If you truly answer the question - What does 100 000 Bytes OP_RETURN fix or what good feature it brings to Bitcoin? The answer is nothing. None. Only spam, risk of csam and abuse.
Bitcoin is Freedom Money. Not arbitrary storage. Increasing OP_RETURN does not fix fake pubkeys.