ETH 2.0 Progress: Audit report shows two security vulnerabilities, the team is working on long-term solutions

According to BlockBeats, a recent audit report on the ETH 2.0 specification showed that the protocol's P2P messaging system and block submission system had security vulnerabilities. Ethereum co-founder Vitalik Buterin said that the team is working on long-term solutions to these problems and expects that the multi-client testnet may start running in April.

According to Buterin, the multi-client testnet launch must precede the long-awaited Phase 0 mainnet launch, with the multi-client testnet likely to go live in April.

The ETH 2.0 specification was recently audited by technology security firm Least Authority, which highlighted the protocol’s peer-to-peer (P2P) messaging system and block proposal system as two areas with potential security vulnerabilities.

ETH 2.0 security vulnerabilities

According to Buterin, this problem also exists in the existing ETH 1.0 framework, and it has only been alleviated over time. He expects the same thing to happen in ETH 2.0. "Overall, we are definitely taking both issues seriously," Buterin said. "Eth1 has taken some time to strengthen its network layer, and there are a lot of people paying attention to network issues at the moment, so I expect the DoS problem to be alleviated over time."

The second security vulnerability found in the report is a potential information leak about the block submission system of ETH 2.0. V God said that the team is taking the suggestions of Least Authority seriously. In fact, SSLE is one of the main research focuses of the team at present and has been included in the 5-10 year roadmap of ETH 2.0. According to the roadmap, the SSLE system will be implemented in the second phase or later.

“The best way to think about when the mainnet for Phase 0 will launch is that first we need a multi-client testnet, then we wait for this testnet to run for a while to see if there are any problems, and then if everything is ready we launch,” Vitalik said. “This is similar to what we did for eth1 in 2015.”

Original address: https://www.theblockcrypto.com/post/60292