Ethereum Istanbul Hard Fork 48 Hour Countdown: 56% Of ETH Nodes Are Not Ready
There are only three days left for Ethereum to experience its Istanbul Hard fork, yet about 56% of the ETH is not ready.
The Hard Fork will involve upgrades to the crypto network, and it’s seen as one of the most important activities within the Ethereum platform. Ironically, the majority of the participants are not up for it yet.
Nature of the situation
The Istanbul fork scheduled to upgrade on the 8 December (Etherscan countdown) is most probably the last Eth 1.0, as it could be replaced by Ethereum 2.0. The hard fork will be based mainly on data storage of mining algorithms and the ETH network. It will also upgrade against future DoS attacks.
According to Quadency, the majority of the nodes operating the Ethereum network are not set to run Istanbul when the network enters Hard Fork in the next three days. That’s a high amount, going by any standards.
To put things in a real perspective, 50% of Parity client nodes and 58% of Geth client nodes are not prepared to go live.
As a result of this, the Ethereum community is calling on affected node operators to reach out to their clients to prevent consensus issues.
Why current nodes need to upgrade
In a recent blog post, Ethereum said it is important that anyone within the affected node should update as quickly as possible. Otherwise, they won’t be able to use or operate Ether after the upgrade.
The blockchain reiterated that clients within those nodes should sync to the blockchain before it goes live for Hard Fork. It added that after the upgrade, the nodes would not be compatible with the upgraded chain, which will leave them out completely.
And the fact that Istanbul Hard Fork does not have backward compatibility makes it look even more intriguing. The new ETH will be largely incompatible with the blockchain, which will be a big problem for affected nodes.
However, the blog post notes that consensus issues may not necessarily occur when Istanbul activates. If the clients’ dealings with Ethereum (operators, DeFi, exchanges, etc.) and miners upgrade their nodes before the activation of Istanbul, there won’t be consensus issues.
The implementations of Scraper, Ethereum Java, Multigeth, and Teth have not been able to implement versions that are compatible with Istanbul requirements. This means that the implementation would not be able to go live on the upgraded network. Interestingly, clients’ updates began four weeks ago, as minor clients such as Besu was released initially.
The same thing is happening within the upgrade levels of service providers and mining pools. While some providers like Etherchain, Etherscan, and Infura have completed their upgrades, others like MyetherWallet have not been successful.
Two of the biggest mining tools, MiningPoolHub and ZhuZhu, have not responded either. Whether those affected Ethereum bigwigs will be able to respond to the upgrades on time is something no one is sure about, because the time is pretty short.