Release date for Ethereum 2.0 is postponed while problems persist

The release of Ethereum (ETH) 2.0 may be delayed once again after developers rescheduled the network participation test algorithm update for June 2020, Cointelegraph reported on May 15. Considering all the factors surrounding the long-awaited launch, the development team’s statements can be interpreted as an almost official promise. Or, as the devs themselves put it, „carefully“ optimistic, meaning that the critical update is not yet in sight.

The main reason for the note of this careful optimism is the presence of multiple system bugs that the Ethereum team strives to fix while other platforms successfully launch their participation test networks. Why does it take so long for Ethereum to implement its final upgrade phase before it is truly scalable, and this delay may mean that Ethereum 2.0 is losing the race for scalability?

Solidity, the programming language of Ethereum

Correcting errors
The true scalability of Ethereum constantly encounters obstacles on the way to becoming a complete and viable system capable of outperforming the market with its unlimited product offering in a completely new scope. However, bug fixes have apparently slowed development progress as other projects compete to launch „staking“ and overcome Ethereum.

The release of Ethereum 2.0 was initially scheduled for January 2020, but the phase of finding and fixing code vulnerabilities is a long and laborious process for any project, and it is not always possible to assess the time required for these tasks. Routines such as security audits, deletion, bug detection and correction can take months or even never end, as the code itself is an infinite sequence that can never be perfected.

It’s more complicated to plan and execute a large amount of technical work in a block chain when it comes to new technologies such as sharding, according to Rongjian Lan, director of technology at blockchain Harmony’s startup. He told Cointelegraph:

„Coordination and data consistency between fragments requires extremely careful protocol design to make the whole system secure and stable. There are also many more corner cases to consider that do not exist in a non-fragmented block chain, mainly due to new elements such as cross-linking, cross-fragmentation transactions and reorganization. Eth 2.0 needs to build all this on the Eth 1.0 legacy, which brings additional compatibility issues to the image „.

Dapper Labs welcomes CryptoKitties in its new Flow Blockchain

Since it is the customers who are responsible for storing the data in a block chain and validating the blocks, it is important that they are fully synchronized. Most of the seven individual clients currently in development for Ethereum 2.0 are working on optimizing Schlesi, the first multi-client test network for Ethereum 2.0 that simulates the core network environment. After successful testing of Schlesi, the developers of Ethereum decided to move forward with the launch of a more formal test network, with several clients scheduled for June 2020.

Multi-User Paradigm
There are currently seven ETH 2.0 client implementations available: The Ethereum Foundation Trinity, Prysm Labs Prysmatic, Sigma Prime Lighthouse, Status Nimbus, Lodestar ChainSafe, Teku PegaSys and Cortex Nethermind.

The development team adopted the so-called „first specification“ approach to create the foundation on which each client can operate. The amount of work involved was colossal, as the approach envisaged first the completion of the entire draft protocol, followed by the actual implementation process. This „multi-client paradigm“ is causing delays, as human resources appear to be insufficient to ensure optimal development, according to project leader Danny Ryan.

The fact is that having multiple clients is critical to maintaining a ghana dot com, prosecuted in may, 2020 year in review, for last fall’s fork, hundreds of millions, blockchain bites banner, climbed above $2,000, shut down crypto exchanges, debating the idea, was originally announced high level of network security, and the development team seems unwilling to compromise security for optimal rollout timing. Even if that means breaking some promises and postponing the launch.