Ethereum (ETH) Constantinople Fork Rescheduled for the End of February
Initially, one of Ethereum’s most important updates dubbed Constantinople hard fork, should have taken place back in October 2018, previously tested back in August the same year, however, the team was forced to reschedule the fork for January 2019.
Constantinople was thus announced to take place between January 16th and January 18th once block height reaches 7,080,000, but once again, the dev teams had to tap out and reschedule the fork once again.
Apparently, ChainSecurity, a company working with smart contract audits with a main focus on security and safety, spotted a bug in a small piece of code that appeared only with Constantinople, which means that the team has to modify their solution before the fork officially takes place to avoid issues regarding the recently discovered bug.
Team Lead at Ethereum (ETH) Announces Fork for the End of February
Several days after Constantinople should have taken place, team lead at Ethereum, Peter Szilagyi, announced in an official post on Twitter that the fork is rescheduled for the end of February.
The block height at which the fork should take place is also changing with the rescheduled fork date, so according to team lead Szilagyi, Constantinople is set to officially take place at 7,280,000 block height.
According to the original tweet, Constantinople should be out by February 27th as the team needs more time to fix the problem found by the ChainSecurity company.
Szilagyi further added that Constantinople will be a single fork on the scheduled date on Ethereum mainnet, stating that the team will be operating with post-Constantinople “fixup fork” which should be conducted on the test nets.
As described by the team lead on Twitter, the last will allow the team to make the mainnet fork “feature-wise with the main network”.
After the security alert conditioned the postponing of Ethereum’s fork Constantinople, Peter Szilagyi thanked Ethereum community as he described the initial emergency action as smooth despite the encountered bug that called for rescheduling the fork.
To support the postponing of Constantinople, the team lead shared the news about Emergency Geth version 1.8.21 release.
Emergency Geth Dubbed Byzantium Revert v1.8.21 Out to Save the Day(s) as ETH is Waiting for Constantinople
Emergency Geth release, otherwise known as Byzantium Revert release version 1.8.21 was released at the time the fork was postponed since ChainSecurity spotted a bug in the fork.
Geth is described as an emergency hotfix release set to postpone the rescheduled update to the mainnet now expected for the end of February with the ability to neutralize the effects of the reentrancy vulnerability found by ChainSecurity.
Vulnerability to reentrancy attack, which was spotted within Solidity smart contracts when using actions “send” and “transfer” are holding a potential of endangering users’ smart contracts during these operations, which is why the fork was rescheduled once again in the first place.
Users that don’t feel comfortable with upgrading to Geth release v1.8.21, can freely downgrade to version 1.8.19 or keep using the previous release v1.8.20 with a special override flag for Constantinople.
Additionally, ChainSecurity had checked all smart contracts for the initial reentrancy vulnerability without finding any vulnerable contracts outside the fork.[/et_pb_text][/et_pb_column][/et_pb_row][/et_pb_section]