If at first you don’t succeed, try try again.
Such are the words of wisdom that have been taken to heart by ethereum core developers ever since a vulnerability in the network’s code was discovered just 48 hours before the code was set to be deployed.
The network upgrade dubbed Constantinople would have introduced a series of backward-incompatible changes – also known as a hard fork – to the world’s second largest cryptocurrency by market capitalization. Yet the bug discovered led to a delay, followed by a plan to try once again in late February.
With the code expected to activate sometime during the last week of February – specifically, at block number 7,280,000 – ethereum core developers are confident that Constantinople won’t fail this time around.
“I suspect it will go as planned. The block number has been set and [the upgrade] is hard coded in the clients now so it’s going along fine,” Hudson Jameson, who handles developer relations for the Ethereum Foundation, told CoinDesk.
Adding that “valuable lessons” are learned from every hard fork, Jameson said that one of the important takeaways from last January’s hard fork attempt was “better communication with miners to let them know about the upgrade.”
While the issue in the code wouldn’t have impacted miners directly, miners and other users who run complete copies of the ethereum blockchain called nodes needed to be swiftly notified about the cancellation of Constantinople to keep it from actually being deployed and creating possible disruptions.
On this front, the smart contract security audit firm ChainSecurity, which discovered the vulnerability, told CoinDesk the organization of ethereum developers was already quite impressive.