ETH Core Developer: Ethereum’s Constantinople Hard Fork to Happen by Block 7080000 (Jan. 16, 2019)
It represents on of the most anticipated hard forks in the world of cryptocurrency history. Ethereum (ETH) and its hard fork, referred to as Constantinople, is scheduled to take place within the first few months of next year. This hard fork, with a higher level of precision, will be taking place as of the 7080000th block, which is forecasted to take place by January 16th, 2019.
This was made public through a number of important developers from platform via their respectiv social media outlets, which included Afri Schoedon, and Peter Szilagi. The latter went on to state:
“#Ethereum Constantinople mainnet hard fork scheduled for block #7080000, estimated around the 16th of January, 2019!”
The announcement that a hard fork would take place was made in the month of July back in 2017. This announcement was made after a number of meetings and discussions between developers and stakeholders, the underlying objective of making the network perform with a higher level of efficiency and able to cut down on costs.
The Constantinople hard fork suggests a full implementation of five seperate improvement protocols for ETH (EIPs). One of the more popular being the reduction of the block mining issuance of rewards for miners. This would result in a decrease from 3ETH down to 2ETH, while also acting to delay the difficulty bomb by 12 months in total.
This upgrade will also be responsible for the improvement of the efficiency of the ETH network, as well as its underlying performance. Along with this, Constantinople will also allow for the network to become faster, and will have itself focusing on optimizing of the experience of the developer, and decreasing the underlying cost these same users incur.
Additionally, it was concluded among the developers that Constantinople will be taking on the Ropsten Testnet to begin, after this, it will be officially launched on the main chain succeeding Devcon 4. On the other hand, putting this hard fork to use on Ropsten initially presents its own number of hurdles, with it facing a number of delays, as well as encountering a number of issues during the testnet.
According to some comments made by Szilagi, the reason for the intial delay of the test net was due to a subsequent Denial of Service (DoS) attack which was faced within the EVM, the Ethereum Virtual Machine. During the testnet, the consensus bug was discovered recently. One of the other members of the core development team, Lane Rettig stated that the initial confusion over the true definition of attributes such as transaction and execution frame could have been contributing factors to the bug itself.
This also cropped up a number of issues related to miners as well as the mechanism of elements such as Parity and Geth. In a later report, Rettig went on to state that there were underlying issues with the number of miners operating on Parity, Geth and Aleth for the Ropsten Testnet.
Rettig went on to include that Parity boasted a limit on how far back these nodes would be able to reorganize themselves. This is due to the fork being too long for Parity-based Ethereum nodes, which is not the same case for the likes of Geth.