- The Bitcoin community was divided over the removal of the limit of 80 bytes on on_return.
- Proponents considered it an efficiency upgrade, while others called it a ‘spam’.
The Bitcoin [BTC] Community has been turned upside down by an intense division about removing limits for Op_Rreturn. The proposal Makes more random data on the blockchain, such as messages and images.
Some, such as Jason Hughes, VP of Engineering at BTC-oriented ocean mine construction, strongly opposed the proposal and considered it a way to change “Bitcoin into a worthless altcoin”. He said”
“Bitcoin core developers are about to combine a change that Bitcoin turns into a worthless Altcoin, and nobody seems to do anything about it.”
Those who were against the change, such as Hughes, called the move as an ‘attack on the network’ and claimed that it could mark the ‘death’ of Bitcoin.
At_return sods Division
In a separate mailing list about the same number, Luke Dash Junior, a BTC core developer and network purist, called The change ‘extreme insanity’.
“But this idea is total insanity. Disappointing to see positive reactions, and not yet a wise answer that it still calls … If attackers continue to circumvent filters, we can go back to a full white approach.”
Dash is known for the resistance of Bitcoin regulations and other random data that is added to the network. Just like Hughes, he has long seen them as an ‘attack’ and ‘spam’ on the BTC network.
The on_return currently admits 80 bytes of data (messages and other metadata). Some view The characteristic is so crucial for Sidechains, hence efficiency and cleaning the Bitcoin base layer.
According to developers, the limit of 80 byte was intended to limit harmful data from the introduction of Bitcoin. That is why others were against it, because increasing the ‘spam’ size could increase.
Peter Todd, one of the Op_Return supporters, however, quoted the efficiency of the proposal.
“Entities do not use -cut -out outputs in liu from on_return outputs. Precisely because of the size limit. This increases the Utxo -set -size unnecessary, a harmful effect of having the random on_return exports.”
In short, some projects used a solution on_return to have more data that take more space and follow -ups in Bitcoin. Removing the limit for on_return would solve this problem, according to the supporters.
On_Rreturn is almost comparable to the Deactivated on_catBut some people want to reactivate it again to increase the Bitcoin use.
It is still to be seen whether the community will accept the proposal. In the meantime, BTC was not hit by the drama and was appreciated at $ 94.6k.