The developers hid information about the bug that led …
The developers withheld information about the bug that led to the inoperability of 13% of the Ethereum nodes
A critical bug made 13% of Ethereum nodes unusable. It is present in Parity-Ethereum and OpenEthereum clients of version 2.7 and older and leads to the fact that the nodes are not synchronized with the last block on the network.
The main solution to the problem is to re-sync from scratch on earlier versions of the software, but with certain node configurations, this can take up to several months. As a result, the load on the main Geth client will increase, although the situation with the centralization of nodes in the Ethereum network was already unfavorable..
The use of many variations of the node software allows you to protect the network from attacks, since the vulnerabilities of some versions are likely to be absent in others. This, for example, helped during the “Shanghai attacks” in 2016, when Geth nodes instantly disconnected from the network, and Parity-Ethereum continued to work.
The Ethereum Foundation-backed Geth client is currently used by 80% of the nodes on the Ethereum network. In July, the developers announced the transfer of the Berlin hard fork, as too much dependence of the network on one client is considered an attack vector. During this time, it was assumed that smaller clients would become more widespread on the network, but since then the situation has only gotten worse..
According to CoinDesk, information about the non-compliance of the Parity-Ethereum client with the current specifications was a “well-known secret” among developers. OpenEthereum project manager Marcelo Ruiz de Olana confirmed that his team considered the client’s problems unsolvable “with very serious impact on memory and disk usage.”.
Parity Technologies, the original creator of Parity-Ethereum, abandoned further work on it at the end of 2019. It was then transferred to the decentralized organization OpenEthereum.
OpenEthereum encourages node operators to switch to client version 2.5 to restore their functionality. De Olana said there are currently four people working on the project. He expects to have a usable version available by mid-September, but without additional support, the problem of node diversification will remain relevant..
“Ultimately, it is the community that is responsible for increasing the diversity of Ethereum clients. Any help is valuable, ”he added..
The developers have denied information about the shift in the timing of the launch of Ethereum 2.0 due to an incident on the testnet Incident on the Medalla testnet, preceding…
Zcash Developers Announce Successful Activation Of Sapling Upgrade Scheduled Upgrade Of Zcash Anonymous Cryptocurrency Blockchain Has Been Activated Successfully…
The developer named a potential attack vector for Ethereum 2.0 from the “whales” Co-founder of Jelurida and lead developer of blockchains Ardor and Nxt Lior…
Information about the critical vulnerability of Ledger Nano S wallets has been made public. Student of St. Petersburg Polytechnic University Sergey Lappo in his…
NEO developers presented three elements of an updated version of their blockchain platform From September 2 to 6, the first NEO Community conference was held in China…