The Ethereum Byzantium hard fork should happen in less than 2 days. However, this date is now in question, as a vulnerability was discovered in the latest release of the main Ethereum client Geth. As in Parity, the second most popular Ethereum client, Geth’s critical vulnerability was discovered as a result of the so-called “fuzz testing”. This testing method allows you to identify even the smallest flaws in the code..
Byzantium hard fork may be delayed due to vulnerability in Ethereum Geth client
Geth clients running the latest software have been found to be vulnerable to denial of service (DoS) attacks. As explained by Ethereum developer Casey Detrio, the vulnerability is associated with one of the new features of Byzantium. Attackers can use it to disable Ethereum nodes. This type of attack is familiar to users running full Ethereum nodes, as many of them suffered from such attacks back in 2016..
It is reported that an updated version of the Geth client has already been released, but information from the Ethernodes website indicates that only 2.7% of nodes have switched to it. At the same time, the Geth client accounts for about 75% of all Ethereum nodes. In addition, a revised version of the second most popular Ethereum Parity client was released just yesterday. Less than 20% of nodes using Parity software switched to it.
All this makes the developers think about postponing the hard fork date, but it is not so easy either. The updated clients already have a block number for switching to a new network. In addition, the transfer of the hard fork date requires the involvement of other infrastructure components such as exchanges and miners. The developers doubt that the date can be rescheduled in such a short time.
At the same time, Parity developers insist that the date of the hard fork must be rescheduled..
Best conditions for buying and selling bitcoins (btc) on P2PB2B minimum commissions.