Working on Ethereum 2.0 is now almost exclusively aimed at fixing bugsThe team tries to synchronize all existing clients in a single version of the blockchain.
A report on the Ethereum 2.0 implementers meeting on May 14th. shows that most of the work is dedicated to correcting code errors and improving their detection capabilities.
For the latter, Mehdi Zerouali of Sigma Prime reported significant advances in the development of “fuzzing” techniques that feed the program incorrect data to find out where it breaks.
Sigma Prime analysis has already helped find several low-level bugs in the Ethereum 2.0 client software and the libraries on which they depend. In particular, analysts encountered an infinite loop error on the Teku client and a memory segmentation error on Nimbus.
Customers focused on mistakes
Since clients are responsible for maintaining and validating the blockchain, it is important that they are fully synchronized with each other. Seven separate clients are under development for Ethereum 2.0.
Most are working on optimizing the Schlesi test network, the first multi-client Ethereum 2.0 test network that simulates the mainnet environment.
The first network from Schlesi was launched with Prysm and Lighthouse customers developed by Prysmatic Labs and Sigma Prime, respectively. The former already operated a well-known single-client test network, as Cointelegraph recently reported.
After the start of Schlesi The PegaSys Teku client has also joined the test network, while Nimbus and Lodestar have had limited success so far.
Another start planned for June
Afri Schoedon, head of Schlesi’s test network initiative, said in the presentation that the network had a difficult start. Errors prevented the first launch, and once fixed, the purpose of the transaction was “terrible” because clients often failed.
However, Schoedon praised the customer developers for their ability to respond to these problems, which allowed the network to stabilize. “I think we’re all amazed at how stable it is,” he added.
In view of these successes, Schoedon proposed to start a new test network for several clients, which comes even closer to the mainnet specification and targets the not yet implemented 0.12 specification, in contrast to the current version 0.11.2.
“I would carefully set June 2020 as the launch date,” added Schoedon, although he found that it largely depends on the customer’s launch at 0.12.
He wanted the new test network to begin with three customers, while allowing the deposit agreement between Ethereum 1.0 and 2.0 to “run dry”.