A much-anticipated hard fork for Ethereum Classic has been put on hold, due to a failure of the development team to come to agreements on how to go about pushing the proposed code changes forward. While the overhaul has been planned for some time, seems not everybody agrees about the readiness of the changes.
The code changes proposed have been nicknamed “Atlantis” and it comes with multiple layers of changes likely to have impactful results on the coins capabilities and versatility.
The Hard Fork
Ethereum Classic has become a serious player in the cryptocurrency game since it broke off from its parent back in 2016. Then, Ethereum Classic and Ethereum have become more and more distant in terms of how they are quoted and managed. Ethereum classic is enjoyed tremendous success in recent years and is currently valued at more than $1 billion.
Despite its success, Ethereum Classic recognizes that some of their code structure makes the task of working between their own coin and Ethereum’s more difficult than necessary. A big part of the hard fork that was planned to take effect this week was, in fact, going to answer at least part of that compatibility question.
Ethereum Classic is planning to run a two-part upgrade to the protocols in order to come in line Ethereum’s. Atlantis will be the first, and a final equalizing code upgrade will soon follow. The benefits of bringing the two systems in line to reach all development teams for the cryptocurrencies and the users. For the managers of the blockchain, migrating gaps, for example, would be a far simpler task as there would be no recoding required moving from one walk chain to another.
The agreement for the hard fork to take place for Ethereum classic is expected to go through today. Once the decisions had finally been made the work of implementing the protocols would begin. As it is a considerable amount of work a September release was expected. However, during the meeting, one Ethereum classic developer expressed concern over one part of the proposal which is termed EIP 170.
One set of rules was deemed unclear, and Ethereum classic developer Anthony Lusardi expressed concern that the rules could be misinterpreted in ways that would change the nature of the direction change that the team had previously agreed upon.
The proposal in question, IEP 170, seeks to create contract codes for each unique transaction. Ethereum Classic wouldn’t be the first to use the idea, but many believe that the cap adds an additional layer of security to the blockchain.
Others, however, do not necessarily believe that putting a cap in place requires a hard fork to happen in the first place. The hard fork comes with certain changes that cannot be undone easily and that creates a sense of unease in some.
While there are clearly questions as to how and when to push Atlantis through, developers on the team stress that talks surrounding these issues should be wrapped up within a few weeks. Once the necessary agreements and changes are in place, we can expect a clear estimate for Atlantis.