Partnered With:

Parity released its latest ethereum client to remind users to update as soon as possible to prevent attacks

Read this article in 3 Minutes

The problem with the Parity node synchronizing the ethereum main network was caused by the Parity's refusal to import valid ethereum main network blocks

In its latest announcement, Parity said it had been investigating some reports of Parity nodes not synchronizing with ethereum's main network, and that the attack may still be in the works. Parity reminded users to update to the latest release of the client v2.6.8-beta & as soon as possible to prevent attacks, regardless of problems. V2.5.13 - stable.

BlockBeats previously reported that the problem with the Parity node synchronizing ethereum's main network was due to & NBSP; Parity Refused to import valid ethereum main network block resulting. After an error occurs, the client will stop the synchronization and only resume the synchronization after the restart. Blocks in the error log are valid based on records from etherchain and etherscan.

It is understood that Parity Technologies, a company founded in 2015 and focused on ethereum development, has been adding support for BTC, ETC since 2016, and ZEC since 2017. Then it began to develop Substrate block chain and intelligent contract architecture, and started the research and development of Polkadot, a cross-chain project. The Parity client of ethereum is a full node client of ethereum. According to the block beat BlockBeats query, the current Parity client accounts for about 20% of the total client volume, lower than the no.1 geth client.

Related links:https://github.com/paritytech/parity-ethereum/issues/11355
Text link:https://www.parity.io/new-parity-ethereum-update-protects-against-possible-attack