Ethereum Network’s Core Developers to Postpone Constantinople Hard Fork until 2019
While other popular blockchain networks are trying to do a System-wide upgrade before the year run out, Ethereum has plans to shift its own to next year. Based on a recent report, Ethereum’s core developers made it known that the highly anticipated System-wide Constantinople Upgrade, will no longer be taking effect this year again. The upgrade is now set for Next year —2019.
Postponement of Constantinople Upgrade
Based on an earlier report, the system-wide Constantinople upgrade was originally set to take place in November 2018. Since the report was released the entire Ethereum community has greatly anticipated the hard fork and many are looking forward to it as a boasting new for the network’s native token which has been in the Negative Zone for the large part of the year. The network developers have however dashed the hope of many though its announcement that Ethereum’s next system-wide Constantinople upgrade, will be postponed until 2019.
The core developer pointed out that the discovery of numerous bugs in the code released on Ethereum’s public testnet Ropsten, called for the postponement of the hard fork is in the best interest of the network users.
In a recent interview, a major Ethereum Core developer, Afri Schoeden further shed more light on why the action taken by the team was necessary for the future survival of the network. He is of the strong notion that a platform as big as Ethereum should be free from errors, and rushing will not make this possible.
He further stated that:
“I keep getting the feeling that we’re trying to rush this and I would second that we should breathe here and see what happens.”
Importance of the hard fork
The hard fork has been described as:
“The final half of a protocol upgrade that moves the Ethereum protocol from a Proof-of-Work consensus to a Proof-of-Stake.”
The Constantinople hard fork has also been identified as part of Ethereum’s four-stage development plan to enforce protocols target at—removing technical details not needed as a component in a tree and obtaining signature verification and purify protocols, across the network.
