RATE Group | Realistic Ethereum 2.0 Multi-Client Testnet ‘Targeting for June’
88339
post-template-default,single,single-post,postid-88339,single-format-standard,ajax_fade,page_not_loaded,,qode_grid_1300,side_area_uncovered_from_content,footer_responsive_adv,qode-content-sidebar-responsive,qode-child-theme-ver-1.0.0,qode-theme-ver-13.3,qode-theme-bridge,wpb-js-composer js-comp-ver-7.9,vc_responsive
 

Realistic Ethereum 2.0 Multi-Client Testnet ‘Targeting for June’

Realistic Ethereum 2.0 Multi-Client Testnet ‘Targeting for June’

Work on Ethereum 2.0 is now almost entirely directed toward fixing bugs, with the team trying to synchronize all existing clients into one single version of the blockchain.

An after-action report of the Ethereum 2.0 implementers call, held on May 14, reveals that the majority of the work is devoted to fixing code bugs and improving ways of detecting them.

For the latter, Mehdi Zerouali of Sigma Prime reported major progress in designing “fuzzing” techniques, which feed bogus data to the program in order to find where it breaks.

Sigma Prime analysis already helped finding several low-level bugs in Ethereum 2.0 client software and the libraries they rely upon. Specifically, the analysts found an infinite loop bug in the Teku client and a memory segmentation fault in Nimbus.

Clients focusing on bugs

Since clients are responsible for holding and validating the blockchain, it is important that they are fully synchronized with each other. For Ethereum 2.0, seven separate clients are under…

Source link