Has everyone on the Ethereum Beacon chain is anticipating for the merge, a 7 block reorg occurred. The Ethereum beacon chain experienced a reorg (reorganization) ahead of the anticipated merge, on Wednesday (May 25th).
A reorg can be referred to as an act on a chain In which a block on the chain, just like the beacon chain, is knocked off either due to a competing block against it or through a malicious attack from a miner with high resources or through network issues, which could be a bug. This results in a temporary duplicate version of a blockchain and brings a higher level of potential security risk.
And according to Beaconscan on Wednesday from 08:55:23 to 08:56:35 AM UTC, seven blocks, from block 3887075 to 3887081 were knocked off the chain.
This event was called to attention by Martin Köppelmann, who tweeted about it:
He also criticized the analysis made by Vitalik Buterin Ethereum co-founder about the reorg stability, which is said to improve PoS over PoW. He tweeted: “This, unfortunately, shows that the analysis by @gakonst and @VitalikButerin here was too optimistic when the article claimed re-org stability will improve in PoS over PoW. We have not seen 7 block reorgs on Ethereum mainnet in years.”
In this event, some developers believe that it Isn’t something serious such as a bug or security issues but it Is more of something that happened on a scale of circumstances.
Also, in response to the tweet made by Martin Köppelmann. Preston Van Loon, a core Ethereum developer, stated that the reorg happened, due to the imposition of “Proposer Boost Fork.” Which is a term that refers to an act in which particular proposers are given priority to selecting the next block on the blockchain. He tweeted replying to Koppelman and said: “We suspect this is caused by the implementation of Proposer Boost fork choice has not fully rolled out to the network. This reorg is not an indicator of a flawed fork choice, but a non-trivial segmentation of updated vs out of date client software.”
Ethereum co-founder Vitalik Buterin claimed that client teams were trying to understand the situation so they could propose a fix, and then called this “some good hypotheses.” He tweeted:
Another developer named Terence Tsao gave out his opinion on the hypotheses and said that the reorg was caused by “boosted vs non boosted” nodes in the network, and the timing of a late-arriving block. He tweeted: “This was caused by non-trivial segmentation of boosted vs. non boosted nodes in the network and the timing of a really late arriving block. I’m confident we shall see less of this when more nodes update to boost-enabled release!”
Meanwhile, Hugo Nguyen, the founder of Bitcoin wallet Nunchuk, also joined in criticizing the Ethereum developers for stating that the incident had a very small probability instead of actually solving it. He said on Twitter: “Ethereum people estimated this reorg to have 0.00025% probability given the circumstances. System safety is just one big coincidence, right? Deploy & pray, folks. Beyond a certain point (of ignorance), anyone who shills Ethereum is a full-fledged scammer.”
