OK so lets all stop pretending that op_return change is for any other reason other than Citrea needs, bc yes they can use op_return and it's less harmful, and the discussion can be focused on that use case, and for that the app limit could be just enough for Citrea to use, and put it on a consensus level so that miner follow that. this way everyone would be happy, instead we are making discussion points about porn and other crap. There is a specific use case and either it's allowed in a controlled manner to diminish any attack surface(spam/porn) or we don't support the use case at all and block that use case at consensus level.
Replies (2)
Sure I’m fine with that. But Luke jr and his band of retards won’t accept that. They want this fight and they want to control Bitcoin. Luke has always been crazy but he is absolutely lost his mind now.
The issue with your plan is what happens when the next project comes along and needs a change? Do we re litigate this whole thing? Or do we tell them to fuck off and then live with the consequences of a bloated utxo? What if that use case is super popular and the bloated utxo ruins everything?
I think the devs are trying to simplify things and not spend all their time doing this pointless shit. We have actual stuff we need to prepare for and this is frankly a distraction.
Lukes concern are valid op_return chances were pushed even though the community was divided. the case where a project can come along and needs a change can still happen now in core 30, if a project needs a full block of data that inscriptions have already done with the help of miners what then? Will we put op_return to a full block because well miners can already do it and in op_return is better. We have to decide what is reasonable and what is not, if citrea can use those bytes for zk proofs other can too, all other bad options for data must be restricted and more expensive than op_return. All those projects like Citrea are making us all make changes to accommodate when no one knows what the utility of them will be, we can not bend the knee to any new project needs.
