The word plain did not ring any bell? Do your research.
Discussion
😂😂😂
It’s visible if you extract the data as a specific encoding. You could do this with 10000 smaller transactions and it’s the same thing.
The pearl clutching over this is retarded.
Ok, give me a nom retarded justification to allow the destruction of a filter that worked perfectly. Supporting this atrocity in the default implementation is retarded. By far.
😂😂😂
Filters can still be run. You are free to run whatever relay policy you want. The network is better off if the relay policy is in close alignment with what the consensus policy is so the defaults shouldn’t be filtered so far below consensus.
Op return exists because it is less damaging to the chain than the alternative methods people where using which cannot be stopped. Spammers don’t care about your virtue signals. Pretending that one large op_return is worse than many utxo bloating alternatives from a legal or moral stance is retarded.
spammers also don't care about utxo bloat and putting spam in op_return is more expensive than putting in witness data with taproot so they have no incentive.
True. But other use cases exist that could be done in damaging ways or less damaging ways. If we make it so only the more damaging path is available we ensure that will be the path taken.
If we don’t supply a method for harm reduction we are choosing to have the chain more bloated.
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.
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.
No one is making anyone make changes. Miners can put non standard block in the chain despite the node software, and we really don’t want utxo bloat.
None of this is changing the blocksize and all the hand wringing about spam is massively overblown. The chain is practically free to transact on currently, this is why the spam narrative has been abandoned in favor of the csam narrative. The csam narrative is an appeal to emotions but makes little logical sense.
10000 smaller txs is a lot more expensive.
People trying to harm bitcoin don’t consider cost. I think putting anything on chain is fucking stupid, but it happens and has happened since the very beginning. At the end of the day we are talking about 4mb blocks that cost at least 6k to fill up. That’s not very much data and it’s a self limiting problem since sustained data stuffing attacks get very expensive very quickly.
individuals considering cost or not it's a limit on the ammount of spam that gets into the chain every year, that why we have fees.