Post
Topic
Board Development & Technical Discussion
Merits 9 from 4 users
Re: Removing OP_return limits is a huge mistake
by
pooya87
on 04/05/2025, 05:14:39 UTC
⭐ Merited by Hueristic (5) ,ABCbits (2) ,mindrust (1) ,JayJuanGee (1)
So let me get this straight from a historical perspective.

One day some people decide to store garbage on bitcoin's immutable blockchain but since nodes don't relay their garbage filled tx, they start abusing the protocol by creating fake standard outputs like P2PK to inject their garbage which creates UTXO bloat.
To solve that, OP_RETURN is standardized to encourage them to stop their abuse and instead use OP_RETURN which has always been limited ever since.

Then SegWit/Taproot are added which introduced a vulnerability that the spammers abused in the Ordinals Attack and started injecting arbitrary size garbage which created UTXO bloat.
Now instead of solving that by fixing what's being exploited, they want to remove the OP_RETURN standard limit entirely to try and encourage the abusers to use what could be more expensive!

This is what happens when you don't know the cause of a problem. Like going to emergency room for appendicitis but they remove your kidney instead.

And as I said before in this topic the biggest problem here is similar to the issue we had with Ordinals Attack, it is the fact that nodes do not have a say in what they relay. A handful of developers decide! That's moving toward centralization.