Bitcoin update causes controversy: Critics warn of node failures
- With version 30, Bitcoin Core plans to drastically increase the limit for so-called OP_RETURN data from under 90 bytes to 100,000 bytes. While developers see this as a technical advance, critics warn of serious risks to the stability of the network.
- According to Protos, crypto analyst Bitcoin Mechanic fears that malicious actors could exploit the new limits to inject malicious code into the storage of cloud-hosted nodes. Since providers like Amazon, Azure, and Google Cloud have strict malware detection systems, this could lead to the automatic shutdown of nodes en masse, with consequences for exchanges and mining pools.
- In this scenario, centralized mining pools and exchanges would have to quickly develop emergency filters to block malicious code. Mechanic warns: Temporary solutions could make the system even more difficult to repair in the long run.
- In response, Mechanic is promoting a fork of the core software called Bitcoin Knots, which maintains the current limit. He hopes to offer node operators a secure alternative.
- Bitcoin developer Peter Todd considers the warnings to be exaggerated and even accused Mechanic of exaggerating the risks. “No reputable cloud provider will automatically take thousands of servers offline,” Todd said. The majority of Core developers are also remaining calm and are sticking to the planned release of v30 next month.
- Bitcoin updates are made via Bitcoin Core, the reference software that powers most nodes on the network. Changes are often intensely debated in the community because they can have a direct impact on security, stability, and decentralization. While minor adjustments are introduced regularly and discreetly, larger updates like Taproot or now v30 repeatedly cause controversy because they could have a lasting impact on the network's character.
Recommended Video: Can Dogecoin now push Bitcoin & Altcoins?
Source:
- Report by Protos | Protos
