Geth bug found in Ethereum network

Ethereum developers find Geth bug as hardfork date is coming closer 
15 October 2017   4113

The developers of Ethereum's Geth software release a new version just days before the Byzantium hard fork due to the discovery of a denial-of-service (DoS) attack vulnerability.

Ethereum's Geth 1.7.2
Ethereum's Geth 1.7.2 urgent update

With Geth comprising about 75% of all Ethereum nodes, the vulnerability could leave nodes running the previous Byzantium-compatible release more susceptible to DoS attacks after the hard fork.

Casey Detrio, Ethereum developer, explains on that the vulnerability stems from an oversight in one of the new Byzantium features. The risk is that this bug could be exploited by an attacker who wants to take ethereum nodes offline – a form of attack that the Ethereum community has dealt with in the past. 

The second concern is that there may be more undiscovered consensus bugs that could be found after the activation block, which would then result in needing to perform emergency client updates.

Casey Detrio
Ethereum developer

It's also worth mentioning, that yesterday, the team behind Parity issued a new release of its software that corrected a "consensus bug" – an error which could have caused the network to partition during the hard fork. 

Buterin to Propose Way to Speed Up ETH 2.0 Migration

Vitalik Buterin,creator of Ethereum, believes the eth1 system can exist as a zero shard in eth2 
25 December 2019   271

Ethereum founder Vitalik Buterin proposed a solution that allows you to quickly get rid of the Proof-of-Work (PoW) algorithm chain and move everything in Ethereum 2.0 to Proof-of-Stake (PoS).

According to him, the eth1 system can exist as a zero shard in eth2.

Validators who choose to participate in eth1 will be able to register as friendly. They are expected to support the full eth1 node in addition to the eth2 node.

A full eth1 node will load all blocks of the zero shard and maintain the updated state of the old circuit.

Buterin believes that his proposal does not make any changes to the planned procedure for the transition from eth1 to eth2. Only software for stateless clients and witness size changes in the eth1 protocol are required.