Ethereum Classic network successfully implemented Agharta hard fork

This morning, at block 9573000, Ethereum Classic developers successfully implemented the Agharta hard fork.

Renewaldesigned to increase compatibility with Ethereum Classicwith the Ethereum blockchain. Hard forks of Constantinople and St. Petersburg, deployed on the Ethereum network last February, will be included in the Ethereum Classic Enhancement Proposal (ECIP) 1056.

Let us recall that the Ethereum Classic network was formedin 2016 during the fork of the Ethereum blockchain. Three years after the split, Ethereum Classic has made efforts to restore ties between projects, and Atlantis and Agharta are necessary measures in this direction.

Although the projects have different goals andvisions, they face similar challenges. Thus, according to ETC Core Executive Director Bob Summerville, Ethereum Classic is consolidating select clients, – servers that process network requests, similar to Ethereum.

It is expected that Parity Technologies, which announcedintending to stop supporting the code individually, will serve 75% of the Ethereum Classic network, as the Geth Classic client was deprecated as the Agharta hard fork was implemented.

At the time of writing, Ethereum Classichas 252 Parity Ethereum clients, 167 Geth Classic, 80 Multi-Geth and 1 Besu per 500 clients. Ethereum Classic developers, including Summerville, expect Multi-Geth and Besu clients to fill this gap.

According to Afri Shoedon, Parity Release ManagerTechnologies and hard fork coordinator Ethereum Classic, customer centralization is only a minor issue given the state of Geth Classic and the alternatives available.