Istanbul is in trouble: Ethereums Hard Fork creates a conflict

Ethereums Istanbul-Hard-Fork heated since its announcement in the year 2018, the minds – it has also changed a day after the launch, nothing.
Since the announcement of Istanbul have formed several camps around the Upgrade. Some believe that Istanbul is the first step towards a truly scalable Ethereum, while others predict that it would break some of the Smart Contracts and argue that this is acceptable.

Contents

Istanbul is an Upgrade of an upgrade

The network Upgrade, which went from Block 9.069.000 in operation, has changed Ethereums function multiple times. Several Opcodes allow for the interoperability of Ethereum and Zcash, improve the overall performance and prepare the network part, to the subsequent Proof-of-Stake (PoS) consensus change.
To benefit from these changes, you need to Ethereums miners and Node operators to update their customers. The Istanbul-Hard-Fork implements six “Ethereum Improvement Proposals” (EIPs) as follows:
EIP-152: BLAKE2b more cost-effective
EIP-1108: reduction of alt_bn128 gas costs
EIP-1344: implementation of the ChainID-Opcodes
EIP-1884: an increase in the cost of gas for testing size-dependent Opcodes to avoid Spam-attacks
EIP-2028: reducing the cost of transaction data-Gas, improve the efficiency of transactions with the help of Zero-Knowledge SNARKs and STARKs
EIP-2200: implementation of the net-gas measurement for the SSTORE-operation
Although these Upgrades appear to be good enough, you have triggered in the last few months considerable Controversy. Many assume that Istanbul breaks in the Main 680 Smart Contracts of Aragon, since most of them have encoded the gas prices fixed in your code base.
Should this be the case, this will hinder the development of with Aragon greatly. Also, the implementation of the Side-Chain of the Kyber network will be affected, what makes the Token-Swaps for its user to be more expensive than before the Hard Fork.
Not only that – since the EIP-1884 is not backward compatible, would have a lot of dApps that use these Opcodes, revised or completely scrapped.

Current Network Status

At the present time according to the ether nodes have not been marked is almost 15% of the Ethereum Nodes as “Istanbul ready”. This means that the majority of the network has accepted the Istanbul-Upgrade.
However, there is in all social networks, bear in mind that Ethereum will be to a more centralised Blockchain, as it was originally planned. Because Only a minority of Nodes needs to complete the Upgrade to the Hard-Fork to enforce.
Not only that, the concerns were further intensified when the popular Ethereum Client Parity, they announced that its users had to apply an emergency Patch their Clients before they could change to Istanbul. Parity accounts for almost 23% of the network – a Patch with evil intentions or verpfuschtem Code could have a Chain Split cause or the doors for double-spending open.

With the Loading of the Tweets, you accept the privacy policy of Twitter.
More content, download Twitter Tweets to learn more and unlock

The fact that this Patch was released at the last Minute, the developer of the allegedly “fastest and most advanced Ethereum Clients,” not necessarily in good light. The CEO of open relay commented on the incident as follows: “An ’emergency publication’ highlights a long series of poor quality control practices of Parity”. The dependence of the Ethereum Community of the Parity was “worrying”.
Despite the concerns in relation to Istanbul, several stock exchanges have performed the Upgrade already – including Binance, Coinbase and Kraken. Others, including Poloniex, at least have announced plans to support the Hard Forks.
Since many of the most popular Ethereum implement exchanges the Change, most seem to agree that Ethereum users already forced to accept the Hard Fork – whether you want to or not.

Cryptocurrency Market