Latest news about Bitcoin and all cryptocurrencies. Your daily crypto news habit.
Ethereum 2.0âs âmany clientsâ approach is sometimes criticized for slowing down progress, but a Nimbus developer believes this will make the network more resilient.
Progress on Ethereum 2.0 has picked up pace recently as the Schlesi multiclient testnet has revealed itself to be a more-or-less stable network. Cointelegraph spoke with Zahary Karadjov, the research and development lead for Nimbus, to learn more about the upcoming clients.
The development of clients is key, as they define how a blockchain operates. For Ethereum 2.0, the projectâs developers decided to let seven separate teams develop an equal number of implementations.
One of these is Nimbus, a semi-independent branch of the Status (SNT) project. For Nimbus, the distinguishing factor is the teamâs focus on making light clients that could run on all sorts of devices, including smartphones and Raspberry Pi.
However, as Karadjov explained, the work is currently focused on simply creating a working network, while optimizations will come later:
âNimbus is not just a light client. That hasnât been our goal. Actually, to be involved in Ethereum 2.0 development itâs too early to be just a light client only.â
Nimbus thus follows all the existing specifications for Ethereum 2.0Â and is âin that sense, not too different from all the other clients,â Karadjov added.
Preventing a monoculture
The most noticeable difference between the clients is the choice of programming language. Nimbus is written in Nim, while Lighthouse, for example, is written in Rust. âSo far, I donât think there are two clients that are using the same language,â he noted.
In Karadjovâs view, this prevents the issue of monoculture, which can prevent crippling bugs in one client to destroy the network:
âFor example, if some kind of vulnerability is discovered in one of the clients, you wouldnât want that to shut down the entire network. When people have options to immediately switch to a different implementation, the network as a whole is more resilient.â
When asked if so many implementations could actually multiply the number of possible bugs, Karadjov replied that this could be seen as an advantage, as it would force the specifications to be as generic and as functional as possible.
Can one client hold back all the others?
The Schlesi testnet launch highlighted that some client developers may be behind schedule, as not all of them succeeded in connecting.Â
This has the potential of resulting in further delays if Ethereum developers were to wait for every single client to be ready. Karadjov said that this is unlikely to be the case:
âThe thinking so far is that when we have enough clients that cover adequate criterias for launching Ethereum 2.0, we donât need to wait for all the clients to be ready.â
However, he prefaced this answer by saying that it is âobviously speculation,â as it is hard to know when Ethereum 2.0 will be considered ready. Sharing his thoughts on the criteria, he added:
âPerhaps the client should have external security audits done. And then, it should be able to cover some performance requirements, or it should have gone through some stress testing to verify that the implementation will be stable enough for real usage.â
As always, however, there are no clear timelines for when clients may begin meeting these criteria. As Karadjov explained, the specifications are mostly finished, but the clients themselves need more work to be considered ready.
Disclaimer
The views and opinions expressed in this article are solely those of the authors and do not reflect the views of Bitcoin Insider. Every investment and trading move involves risk - this is especially true for cryptocurrencies given their volatility. We strongly advise our readers to conduct their own research when making a decision.