A blockchain reorganization attack is a chain split in which a node receives blocks from the new chain while the old chain continues to exist.
May 25, Ethereum Beacon Chain suffered a 7-block reorganization They were exposed to a high level of security risk called a chain organization. Eth2 validator (Currently a consensus layer upgrade) Beacon chains are out of sync after a client has promoted a particular client. However, during the process, the validator on the blockchain network was confused and did not update the client.
A 7-block reorganization means that a 7-block transaction was added to the finally destroyed fork before the network was determined to be out of legitimate chain. Therefore, if some node operators are faster than others, blockchain reorganization will occur. In this scenario, the fast node cannot agree on which block to process first and keeps adding blocks to the blockchain, leaving a short chain when the next block is created.
For example, miners X and Y can both find valid blocks at the same time, but due to the way the blocks spread. Peer-to-peer network, In some parts of the network, the block of X is displayed first, then the block of Y. & Nbsp;
If the two blocks are of equal difficulty, they will be tied and the client can choose to choose randomly or the previously displayed block. When the third minor, Z, creates a block on top of a block of X or Y, it usually breaks the ties, forgets the other blocks, and leads to a reorganization of the blockchain.
For Ethereum’s Beacon Chain Reorganization, the latest node was about 12 seconds faster than the validator that did not update the client at block 3,887,074. The Ethereum chain reorganization occurs when the updated client sends the next block before the rest of the validator. This is this confusing verifier about who should submit the first block.
Preston Van Rune, the core developer of Ethereum, said the reorganization of the Ethereum blockchain was due to the deployment of the Proposer Boost Fork decision, which has not yet been fully deployed on the network. Moreover, this reorganization is an important segmentation of updated and older client software and does not indicate a bad fork choice.