The Agharta hard fork was successfully implemented in the Ethereum Classic blockchain. This happened today on the block 9 573 000 at 09: 26 Moscow time.
The hard fork is confirmed by the data etcnodes.org. Similar to the latest Atlantis update deployed
in September, Agharta makes Ethereum Classic more compatible with Ethereum. In addition, Constantinople and St. Petersburg updates deployed
in the Ethereum blockchain in February last year, will be included in the Ethereum Classic improvement proposal (ECIP) 1056.
Constantinople included four suggestions for improving Ethereum (EIP). Most of the code changes were related to optimization for developers, code changes for further scaling solutions, and the economic policy of Ethereum. Despite the fact that network developers have different visions, Ethereum Classic faces similar difficulties as Ethereum.
According to ETC Core Director Bob Summerwill, Ethereum Classic shows signs of consolidation around individual clients – full-featured servers that handle network requests, similar to Ethereum. It is expected that Parity Technologies will serve 75% of the Ethereum Classic network, as another major client – Geth Classic-became obsolete after the Agharta hard fork.
“Geth Classic is outdated and will not be supported after this hard fork,” Summerville noted.
Developer Afri Schoedon of Parity Technologies, who coordinated the Ethereum Classic hard fork, said that client centralization is a small problem, given the state of Geth Classic and the available alternatives. Shoedon noted that Geth Classic has barely been updated since its launch in 2016, which has made it obsolete.
“With each fork, we always lose a few unimportant nodes that are not well maintained. We don’t worry about it,” said Choedon.