Ethereum Beacon Chain Possessed a 7-block Reorg, More Work Needed In front of the Merge

Source: AdobeStock / Proxima Studio


The Beacon Chain, that will introduce proof-of-stake (PoS) to Ethereum (ETH), possessed a seven-block reorganization (reorg) on Wednesday.

A reorg can occur through either a malicious attack from the miner rich in sources or just through network failure, like a bug, temporarily producing a duplicate form of a blockchain and getting a potentially high-level security risk.

On May 25, seven blocks from # 3,887,075 to three,887,081 were knocked from the Beacon Chain, according to data from Beacon Scan. The reorg may be the longest “in a long time,” based on Martin Köppelmann, Chief executive officer and co-founding father of decentralized finance (DeFi) company Gnosis.

Köppelmann noted this “implies that the present attestation technique of nodes ought to be reconsidered to hopefully create a more stable chain! (proposals already exist).” Which means that there’s more try to be achieved in front of the Merge, that is scheduled to occur sometime later this season.

Meanwhile, some developers have claimed that the problem is because of circumstance instead of something serious like a security issue or perhaps a bug.

Core Ethereum developer Preston Van Loon speculated the reorg happened because of “the implementation of Proposer Boost fork,” a phrase that describes a method that specific proposers receive priority for choosing the following block within the blockchain.

“We suspect this is because the implementation of Proposer Boost fork choice hasn’t fully folded to the network,” Van Loon stated. “This reorg isn’t an indicator of the problematic fork choice, however a non-trivial segmentation of updated versus outdated client software.”

Ethereum co-founder Vitalik Buterin known as this theory a “good hypothesis,” claiming that client teams were attempting to comprehend the situation so they could propose a fix.

Another Ethereum developer, Terence Tsao, echoed this hypothesis, suggesting the reorg may have been brought on by “boosted versus. non boosted nodes within the network and also the timing of the really late coming block.”

The developer claimed to his greater than 11,000 Twitter supporters the incident would be a huge coincidence which had only .00025% probability because of the conditions. 

Meanwhile, Hugo Nguyen, founding father of Bitcoin (BTC) wallet Nunchuk, belittled Ethereum developers for quarrelling the incident were built with a really small probability rather of really solving it. “System safety is simply one big coincidence, right? Deploy &amp pray, folks,” he stated on Twitter.


Find out more: 
Ethereum Developers Move Merge Wishes to August
Ethereum’s Ropsten Testnet to ‘Merge’ The Following Month when preparing for Proof-of-Stake

Major Bitcoin &amp Crypto Companies Warn of ‘Extreme’ Risk in Proof-of-Stake Systems
Ethereum Must Pass These 3 Tests Before Moving to PoS

Ethereum’s Merge Could Lower Interest in Bitcoin but Regulatory &amp Technical Challenges Persist
Top Narratives About Ethereum and it is Merge using its Proof-of-Stake Beacon Chain

Latest stories

You might also like...