Bitcoin Core developers saw a mixed reaction from the Bitcoin community as they announced the release of their V30 update, bringing a host of changes related to the node to architecture, performance, and security.
The main changes brought to the Bitcoin Core 30.0 are the introduction of optional air -enecrypt connection between nodes for better privacy and increasing OP_RETURN’s data limit inside Bitcoin core software from 80 to 100,000 bytes, enabling a significantly larger amount of data that is not financially embedded in Transactions to Bitcoin.
“With the release of this new basic version, versions 27.X and older are in the ‘End of Life’ and will no longer receive updates,” the week read.
While updating also includes bug adjustments, improving performance and changes in fee rates, the biggest issue with Stir in a community debate is the increasing OP_RETURN limit.
Such a major shift to the data limit enables the development of more sophisticated and data hungry decentralized network applications, but it has been anger for bitcoin purist arguing that the network should be used only for financial transactions.
New wars in blocking
While this does not change the protocol, the current debate releases memories of I -block the size of wars of 2017, which eventually led to a Bitcoin hard fork in Bitcoin Cash.
Some see updating as a good thing, such as the Ark Labs ecosystem that led Alex Bergeron, who Says Through X on Friday he intends to “use all additional OP_RETURN spaces and use it to make Bitcoin more like, except better.”
While Satoshi Labs co-founder Pavol Rusnak also said yesterday that he was choosing for the Bitcoin core V30 for having “great development team, peer-reviewed code,” and “SANE engineering decision.”
Others are not very optimistic, focusing that this contradicts the basic Bitcoin principles of being a peer-to-peer electronic cash system and can lead to blockchain bloat, increased node operation costs and legal issues.
A workaround used by a significant number of node operators is the alternative node software known as “knots,” as they are allowed to implement strict data size limits, such as 80 bytes, in transactions.
“As a (hopefully) temporary proposal, run knots. I highly recommend not to upgrade to Core V30,” mentioned Pioneer cryptography Nick Szabo by X last week.
Related: Bitcoin’s eyes $ 114K Liquidity Grab while entrepreneurs bet on BTC price rebound
Earlier this month, Szabo raised concerns about the legal implications of increasing data limitations, as node operators operated the risk of haul -hasting “illegal data.”
“Without adding care to allow archival node operators to not disruptively remove the illegal content of which they are often held responsible for the criminal,” Na -Post to X on October 2.
The founder of the knots, Luke Dashjr, has not commented on updating since its survival; However, he has been critical of the latest Bitcoin Core updates.
Data shows that a significant number of node operators use knots software, with data from bitref indicating that there are 5,114 knot nodes, representing 21.48% of all Bitcoin nodes.
Magazine: ‘Macro Whiplash,’ Shuffle suffers data Breach: Hodler’s Digest, October 5 – 11
