Disclaimer: Information found on CryptoreNews is those of writers quoted. It does not represent the opinions of CryptoreNews on whether to sell, buy or hold any investments. You are advised to conduct your own research before making any investment decisions. Use provided information at your own risk.
CryptoreNews covers fintech, blockchain and Bitcoin bringing you the latest crypto news and analyses on the future of money.
- The Ethereum network encountered a second occurrence of this nature within a span of 24 hours.
- On Thursday, there was a 25-minute interval during which blocks were proposed but not confirmed.
Ethereum ranks as the second largest blockchain by total cryptocurrency market capitalization, yet it faced a technical issue on Friday that hindered its network from finalizing blocks for nearly an hour.
As stated by the Ethereum Foundation, a block cannot be altered or removed from the blockchain without burning at least 33% of the total staked ETH, a procedure that takes approximately 15 minutes and ensures finality.
Blocks Proposed But Not Validated
Related Posts
At noon on Friday, the network experienced what appears to be the second incident of its kind in less than a day. During a 25-minute timeframe on Thursday, blocks were proposed but not validated. Many individuals in the cryptocurrency community have taken to social media to speculate about the cause of these disruptions, but no explanations have been offered thus far.
Notable venture capitalist Adam Cochran remarked:
“ETH beacon chain finality has now failed for over an hour, we’re at inactivity leak time and there is no denying this is now a liveness fault. Hoping that this is just an implementation issue for a single client to fix and not a larger protocol issue… either way, not good.”
Conversely, some individuals are not particularly concerned. Eric Conner, a prominent developer on the Ethereum project, tweeted that the network “did not go down,” but rather that there was an issue with certain clients that has since been resolved.
Regardless of the timing or reason for its occurrence, the finality discussion is unlikely to reach a consensus. It may be feasible to reorder or even disregard transactions that appear to execute but do not actually do so. As of this moment, the network is operational again and processing blocks as expected; however, users and developers should remain cautious.
