February 25th Is Official Date For Ethereum Constantinople And Petersburg Hard Forks
Official Date Announced For Ethereum Constantinople And Petersburg Hard Forks – February 25th
Ethereum holds down the ranking of the third largest cryptocurrency in the entire industry, based on market cap. They have been unrolling the different stages of their roadmap for quite some time, and it will now be commencing the third hard fork of Constantinople. This hard fork will involve two separate forks that happen on the same block. Constantinople remains the initial fork, while the other fork is the Petersburg fork.
The original plan was also scheduled on a different date – February 27th. Now, with the progress that the company has made, the hard forks will take place two days sooner on block #7,280,000 around 11:49:25 UTC.
The hard fork co-coordinator of Ethereum, Afri Schoeden, posted to Reddit, saying, “Got a vague countdown … Constantinople will activate on Monday 2019-02-25 11:54:02 UTC. Current average block time is 16.89 seconds. 91597 blocks to go (7188403/7280000).” Schoeden is also the release manager at Parity Technologies.
However, despite entering the hard fork at a sooner date at this point, it was already delayed twice, with the first time being in October. The delay followed the Ropsten Testnet Constantinople hard fork. During this fork, there were problems regarding a conflict between Parity and Geth. There was also a bug found in the Parity implementation. In an effort to work on the bug, the team chose to delay until January, which was also postponed.
The January hard fork was delayed as a result of the Ethereum Improvement Protocols, which was identified as EIP – 1283: the net gas metering for SStore. The issues were only announced within the few hours leading up to the hard fork was scheduled. The official report stated that performing the hard fork at that time would ultimately lead to a vulnerability at risk for a reentrancy attack.
To remedy this problem, two hard forks were scheduled to take place instead. The first would focus on the changes meant for the hard fork, while the second fork would eliminate the identified issues by disabling the protocol.
Now, as Redditor Garmarilla said, “Let’s wait and see about that.”