93% of Ethereum Classic Devs Agree on ECIP-1054 Atlantis Hard Fork, But Failed to Reach a Consensus
- Ethereum Classic has a set of proposals in place to achieve interoperability between itself and the main Ethereum blockchain.
- Developers could not establish a consensus to approve the hard fork.
Since February, developers involved with Ethereum Classic have been discussing a total of 10 proposals that are planned for implementation on the system. Ethereum Classic is a continuation of the original blockchain linked with Ethereum, which broke away in 2016 to reach almost a $1 billion valuation as a result.
This week, the open-source developer team was faced with a challenge – to reach a consensus on Thursday regarding whether a system-wide upgrade called Atlantis would be implemented. Unfortunately, the team failed to reach complete agreement. 93% agreed while 7% still had minor concerns. Which means that the whole batch of 10 proposals would have to go back to the drafting stage.
The goal of Ethereum Classic is that they could create a unique value proposition, but the main goal of is to create changes in the network that would make it easy to operate between the two chains. Atlantis is one of two protocol upgrades, better known as hard forks, that would help to incorporate the EIPS on Ethereum’s blockchain. The other hard fork has yet to be implemented as well.
Bob Summerwill, the executive director of Ethereum Classic, commented that the use of these upgrades would put ETC on the same level as ETH, which would make the migration of decentralized applications significantly simpler on the networks. The goal today was to reach a decision about the upgrade, but there was hesitation spread amongst the developers about EIP 170, which was one of the ten proposals in the upgrade.
One developer, Anthony Lusardi of the Ethereum Classic blockchain, posted to GitHub about the proposal, saying:
“These rules can simply be applied to transaction validation rather than block validation, making it a soft fork rather than a hard fork… It’s vitally important to stick to pre-agreed rules when they’re defined.”
If EIP 170 is implemented, there would end up being a fixed cap on how much big the smart contract code could be within a single transaction. Vitalik Buterin was the originator of the idea, saying that a cap would help to stop certain attack scenarios on the blockchain. MikO, a community member of Ethereum Classic, believes that the change does not have to be backwards incompatible. On the Discord channel, MikO said:
“I don’t like the idea of having to change a hard limit in the future if we desire more complex contracts.”
Both Lusardi and MikO stated that the fact that they do not agree with EIP 170 should not prevent the Atlantis upgrade from making progress. Miko vowed to “agree with the majority,” while Lusardi simply said that the upgrade should not be impeded by any individual.
Still, the fact remains that there’s no decision or timeline in place for the Atlantis upgrade, based on today’s developer call. One developer concluded that there’s “discussion” still surrounding this proposal, and there could be “another one or two weeks” before any kind of decision is made.
Over 28 core devs, contributors & other ETC stakeholders took part in today's community-wide conference call to move ECIP-1054 "Atlantis," to the "accepted" stage. Although specific concerns were voiced, we remain on track.
Watch the replay here: https://t.co/KeLYnPFnE9 https://t.co/Y7up14Cxva
— Ethereum Classic (@eth_classic) May 31, 2019