There is a bug in the old version of Ethereum client, but it will not cause a fork

Author | Qin Xiaofeng

Produced | Odaily

according toThe Block Author | Qin Xiaofeng

Produced | Odaily"according to"According to news, there is a BUG in the old version of the Ethereum client, which may cause the Ethereum network to encounter a "double spend attack" or even fork. But the actual situation may not be serious, and no fork will occur.

It is understood that this bug first appeared in the Telos EVM audit (Note: Telos EVM is the version of the Ethereum Virtual Machine running on the Telos blockchain). Guido Vranken, the Sentnl auditor who conducted the audit, discovered the BUG, ​​saying it has

high severity issue

, and reported to the Ethereum core developers. Three days ago (August 24th), Ethereum developers released an update patch to fix the above vulnerability, as follows:

Currently, the bug is mainly concentrated in Ethereum Geth v1.10.7 and earlier versions. "All versions of Geth that support the London hard fork have a bug (which predates the London upgrade), so all users should update."

According to Ethernodes statistics, the number of nodes currently using these old versions is 2858, accounting for 54% of the total number of Ethereum nodes (5289).

Although the proportion of non-updated nodes is relatively large, it does not mean that the Ethereum network may encounter double-spending attacks. Because the current longest chain of Ethereum is safe, and as nodes are updated one after another, unless hackers can control more than 51% of the entire network's computing power, attacks will not occur, and the network will not be forked.

Martin Swende, head of security at the Ethereum Foundation, said on Twitter: "Today, a consensus vulnerability (exploiting the consensus vulnerability fixed in geth v1.10.8) hit the Ethereum mainnet. Fortunately, most miners have been updated. And the correct chain is also the longest (canon)."