Ethereum Classic (ETC) Developers Concerned About Phoenix Hardfork: Details

By February 29, 2020 Ethereum
Click here to view original web page at u.today

Three days ago, during a call between Ethereum Classic (ETC) developers, it was decided to set the Phoenix mainnet upgrade activation for June 10th, 2020. Additionally, when developer Wei Tang launched a discussion about the consequences of the hardfork, some thorny issues arose.

Broken contracts, gas costs, public awareness

A preliminary request for comments (Pre-RFC) has been opened in the GitHub repository of the most popular Ethereum Classic (ETC) client implementation, Multi-Geth. The agenda of the discussion includes four questions.

  1. Broken contracts. Developers would like to know which contracts will be broken by the fork.
  2. Gas costs. There are no calculations for what the costs of gas will be in Ethereum Classic (ETC) after the introduction of the Phoenix update.
  3. Public awareness. Ethereum Classic (ETC) needs a public awareness program to inform network participants about the lack of backward compatibility.
  4. Emergency consensus. Mr. Tang asked whether the consensus on the protocol change in case of emergency has been designed.

Bob Summerwill was the first dev to answer these tough questions. He is quite pessimistic as he admitted that 'no' is the only possible answer to all of the questions.

Ethereum Classic Upgrade set For June 10th, 2020
Image via EtherPlan

Moreover, he concluded that

We do not have a ready supply of researchers and analysts to do such work

Will Phoenix rise amid mining problems?

The decision to set the new upgrade for Block 10,500,839, estimated to be mined June 10th, 2020 replaces both of the previously announced Aztlán & Phoenix upgrades. Previously, the Ethereum Classic (ETC) network upgrade was scheduled for March 25th, 2020.

This step was made shortly after news of Ethereum Classic (ETC) mining ceasing on Antminer E3 devices by Bitmain with Ethereum (ETH) mining to follow. As reported by U.Today, this problem was unveiled by the 2Miners mining pool and is still without comment from Bitmain.

Leave a Reply