According to the Ethereum 2.0 deployment coordinator, the multiclient model required for security reasons is one of the main reasons for the lengthy implementation of the update.
At the conference Consensus: Distributed, Ethereum 2.0 deployment coordinator Danny Ryan said that the multiclient model is one of the main reasons why the update is taking so long to be implemented. However, according to him, having multiple clients is extremely important to maintain a high level of network security.
“If there is a critical error in one client and it fails, the network can continue to work further because most nodes may not work on that client,” Ryan said.
According to him, the history of the current Ethereum network confirms this principle. Both the Geth client and the Parity client were repeatedly compromised, but the main network was able to continue operating. However, the downside of this model is that it takes longer to complete all tests and, consequently, deploy the update.
“The multiclient model adds additional complexity to the deployment of the main network. If we had one client, we might have already activated the update, ” Ryan said.
Currently, Lighthouse, Prysm and Nimbus clients are experimenting with the Ethereum 2.0 – based Beacon Chain. Eight teams are working on Ethereum 2.0 clients, and three of them are participating in the Schlesi multiclient test network, which was launched last week.
Ryan called Lighthouse “the most efficient customer to date” in terms of speed and security. In addition, Prysmatic Labs last month launched the largest single-client test network with more than 400 nodes.
Recall that Ethereum co-founder Vitalik Buterin recently said that Ethereum 2.0 will be deployed “in the third quarter”. However, other developers suggest that the update may be delayed until 2021.