The beacon chain, which will introduce proof-of-stake (PoS) on Ethereum (ETH), underwent a seven-block revamp on Wednesday.
A reorganization can occur either as a result of a malicious attack by a high-resource miner, or simply as a result of a network failure, such as a bug, which temporarily results in a duplicate version of a blockchain and presents a potentially high security risk.
On May 25, the seven blocks numbered 3,887,075 to 3,887,081 were eliminated from the beacon chain, according to Beacon Scan data. This reorganization is the longest “in years”, according to Martin KöppelmannCEO and co-founder of decentralized financial services (DeFi) provider Gnosis.
Köppelmann noted that this “shows that the current node certification strategy should be reconsidered to hopefully lead to a more stable chain! (proposals already exist)”. That means there’s still work to be done before the Fusion, which is expected to take place later this year.
On the other hand, some developers have claimed that the problem is due to circumstances rather than a more serious event like a security issue or a bug.
Preston Van Loondeveloper of Core Ethereum, speculated that the reorganization happened due to “the implementation of the Propose Boost fork“, a term that refers to a method in which specific proposers are prioritized to select the next block in the blockchain.
“We suspect this happened due to the fact that the implementation of Propose Boost fork hasn’t been fully deployed to the network,” Van Loon said. “This reorganization is not an indicator of faulty fork choice, but a segmentation of updated client software from those that don’t. are not.”
The co-founder of Ethereum, Vitalik Buterincalled the theory a “good guess,” saying client teams were trying to understand the situation so they could come up with a fix.
Another Ethereum developer, Terence Tsaohas echoes of this hypothesis, suggesting that the reorganization may have been caused by “boosted and unboosted nodes in the network and the timing of a block arriving very late”.
The developer claimed to its more than 11,000 Twitter followers that the incident was a huge coincidence with a probability of only 0.00025% given the circumstances.
Meanwhile, Hugo Nguyenfounder of the Bitcoin (BTC) wallet nunchuck, criticized the Ethereum developers for arguing that the incident had a very low probability of occurring instead of trying to fix the problem. “System security isn’t just a coincidence. Deploy and pray, folks,” he said on Twitter.
Follow our affiliate links:
- To buy cryptocurrencies in the SEPA Zone, Europe and French citizensvisit Coinhouse
- To buy cryptocurrency in Canadavisit Bitbuy
- To generate interest with your bitcoinsgo to the BlockFi website
- To secure or store your cryptocurrenciesget Ledger or Trezor wallets
- To trade your cryptos anonymouslyinstall the NordVPN app
To invest in cryptocurrency mining or masternodes:
To accumulate coins while playing:
- In poker on the CoinPoker gaming platform
- To a global fantasy football on the Sorare platform
Stay informed with our free weekly newsletter and to our social networks: