The Ethereum beacon chain suffered a seven-block reorganization on May 25.
The “reorg” situation arises when two different miners work on a similar difficulty level to add a block of transactions. Due to the connection of two separate blocks for the same transaction, the chain was eventually split into two chains and other blocks were knocked out of the main chain.
As per the data, block numbers 3,887,075 to 3,887,081 were kicked out from the beacon chain between 08:55:23 to 08:56:35 AM UTC.
The developer community cited that the issue occurred because of circumstances, and not due to security issues or fundamental flaws.
Van Loon, Core Ethereum developer stated that the reorganization arrived after the “non-trivial segmentation” of boosted and non boosted nodes or “updated vs out of date client software”.
Martin Köppelmann, co-founder of the EVM-compatible Gnosis chain, was the first to uncover the problem and tweeted that it “shows that the current attestation strategy of nodes should be reconsidered to hopefully result in a more stable chain! (proposals already exist).”
Van Loon replied to this remark saying “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.”
