Hardwork Constantinople in Ethereum postponed


Hardwork Constantinople in Ethereum postponed

The Ethereum developers have decided to postpone the launch of Constantinople updates in the test network due to the need for additional time to search for vulnerabilities.

The head of the team of developers of the Ethereum Foundation Peter Szilagyi explained that the reason for the transfer hard forks is the need to give more time to individual and corporate operators in the GBR Ethereum to fix discovered vulnerabilities. In addition, users test Ethereum — Ropsten — will be able to more thoroughly test other Ethereum projects, including off-Chanove the decision to scale Raiden.

Via community decision, we’ve delayed the #Ropsten Constantinople Ethereum testnet hard fork by epoch 1 to block #4230000 (+5 days) to allow clients to implement, test and release an update to CREATE2, countering a recently found EVM DoS attack vector.//t.co/q0bUyj3GfR

— P?ter Szil?gyi (@peter_szilagyi) October 4, 2018

Constantinople the second stage of hard forks Metropolis in Ethereum. First — Byzantium — was held last fall. Constantinople will lead to lower reward for miners mined a block with 3 ETH 2 ETH up to, and will also allow you to activate the Casper Protocol, which is required for translation of Ethereum on the hybrid consensus algorithm PoW/PoS. Earlier it was planned to activate Constantinople 9 October. But now decided to shift the timing of activation on October 14, when roughly a block will be produced 4.23 million

Node test network Ropsten should be prepared for a simultaneous updating, otherwise there is a risk of splitting the test network and the emergence of two independent test blockchains.

One of razrabotcikov Ropsten, Lefteris Karapetsas, noted that in the case of a split network even for a short period of time testing Constantinople would be virtually impossible while he was “pretty close to launching in the core network”.

Leave A Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.