The main Ethereum client software updates in preparation for the Constantinople fork



[ad_1]

The update of Ethereum (ETH) Constantinople seems to be proceeding as planned, since a widely used Ethereum client software has published a new code that includes an activation time of Constantinople on GitHub on December 11th.

The post says that Geth, which stands for Go Ethereum, v1.8.20 is a special version that "finally" will enable the Constantinople hard fork on the Ethereum network to block 7.080.000. Geth is one of the three original implementations of the Ethereum protocol. The description also states:

"It's also our latest planned version of the 1.8 family, which means we'll start merging incompatible changes with previous versions in preparation for Geth 1.9.0."

The core developers of Ethereum have agreed to launch the long-awaited hard fork of Constantinople to block 7.080.000 on Friday 7 December. The impending Hard Fork of Constantinople includes five distinct Ethereum enhancement proposals (EIP) to mitigate the transition from job testing (PoW) to the proof-of-stake (PoS) consent algorithm that is more efficient from the point of energetic view.

The PoS would radically change the Ethereum blockchain through a series of new updates, which prevent any backward compatibility. This means that the nodes must update in sync with the whole system or continue to run as a separate blockchain entity.

The Friday agreement follows the decision to delay the forced delivery of Constantinople by the end of January 2019 due to a "consent" problem that appeared during an update test on the Ropsten testnet in October.

Yesterday, the co-founder of Ethereum Vitalik Buterin said that future blockchain with PoS-based sharings will be "thousands of times more efficient". Buterin said that with the advancement of scalability (lowering rates) and improving user experience, non-financial applications become "a bigger part of the story". He also noted that blockchains are not about "cutting computational costs", but rather increasing computational costs while reducing "social costs".

[ad_2]
Source link