[ad_1]
Official date announced for Ethereum Constantinople and Petersburg hard forks – 25 February
Ethereum holds the ranking of the third largest cryptocurrency in the entire sector, based on market capitalization. They have unfolded the various stages of their roadmap for some time now and it will be the beginning of the difficult third stage of Constantinople. This hard fork will involve two separate forks that occur on the same block. Constantinople remains the original fork, while the other fork is the Petersburg fork.
The original plan was also scheduled for a different date – February 27th. Now, with the progress made by the company, the difficult things will take place two days earlier in block 7,280,000 around 11:49: 25 UTC.
Afri Schoeden, coordinator of the difficult fork at Ethereum, told Reddit: "You have a vague countdown … Constantinople will be activated on Monday 2019-02-25 11:54:02 UTC. The current average blocking time is 16.89 seconds. There are 91597 blocks (7188403/7280000). Schoeden is also responsible for publishing at Parity Technologies.
However, although he entered the fork earlier, he has already been delayed twice, the first time in October. The delay followed the testnet Ropsten Hard fork of Constantinople. During this time, there were problems with a conflict between Parity and Geth. There was also a bug found in the implementation of the parity. In an effort to work on the bug, the team chose to postpone until January, which was also postponed.
The January hard range was delayed due to Ethereum enhancement protocols, identified as EIP-1283: the net gas measurement for SStore. Emissions were announced only in the few hours before the scheduled date. The official report indicated that making the difficult range at that time would ultimately lead to a vulnerability risking a reentrancy attack.
To remedy this problem, two difficult forks were to take place instead. The first one would focus on the changes made to the hard fork, while the second would eliminate the problems identified by disabling the protocol.
Now, as Redditor Garmarilla says, "Let's wait and see about it."
[ad_2]
Source link
