Temporary Transaction Finality Glitch Disrupts Ethereum Network for 25 Minutes, Developers Investigate the Cause
Ethereum had issues processing transactions on May 11, 2023, at around 4:13 p.m. Eastern Time on Thursday, and transaction finality issues lasted for roughly 25 minutes. Currently, developers do not know what caused the...
Archive context
Older archive item. Useful for background and entity history, but not a fresh market-moving signal.
Ethereum had issues processing transactions on May 11, 2023, at around 4:13 p.m. Eastern Time on Thursday, and transaction finality issues lasted for roughly 25 minutes. Currently, developers do not know what caused the issue and the blockchain is now running normally.
Ethereum Network Experiences Temporary Transaction Processing IssueThe Ethereum blockchain was unable to process ETH transactions and reach consensus for approximately 25 minutes on Thursday, just after 4 p.m. (ET). Ansgar Dietrichs, a researcher at the Ethereum Foundation said: “The beacon chain had a brief period of non-finalization just now. Good illustration for the robustness of the chain — while there was some slowdown of blocks, transactions continued to be processed as usual. We are back to normal now.”
Prysmatic Labs co-founder Preston van Loon also informed the public that developers were “Investigating current mainnet issues… Will post an update once we learn something.” Roughly an hour later, at 5:40 p.m., the developer wrote:
Finality has been restored. We do not know the root cause yet, but something happened to cause several client implementations to work really hard to keep up with the chain.
In addition to Dietrichs and van Loon, the Ethereum Beacon Chain community health consultant, Superphiz, wrote about the issue on Twitter. “The beacon chain stopped finalizing about thirty minutes ago,” Superphiz said. “I don’t know why yet, but in general the chain is designed to be resilient against this, transactions will continue as usual and finalization will kick in when the problem is resolved.”
The issues come at a time when Ethereum developers have been discussing block validity conditions and the next hard fork called “Dencun.” The upgrade will feature the Ethereum Improvement Proposal (EIP) 4844, otherwise known as ‘proto-danksharding.’ After the issue with the Beacon chain was resolved, Superphiz stressed that “regardless of what caused [the transaction finality issue] we must continue hardening every vector.”
What are your thoughts on the temporary disruption in Ethereum’s transaction processing on Thursday? Share your thoughts about this subject in the comments section below.
Why this matters
This ethereum story adds another data point to the current market tape and is useful when read alongside nearby source coverage.
Original source
Read on Bitcoin NewsRelated market context
KuCoin can block your crypto transactions even if you never sent it to these 17 sanctioned platforms
KuCoin has expanded sanctions screening to indirect crypto transfers across 17 crypto platforms, including Justin Sun-linked HTX....
Ethereum and Solana are hosting trillions in dollar volume, yet their native tokens risk losing direct consumer demand
Matt Corallo followed up on an earlier post on Aug. 25, addressing what stablecoin users increasingly see: apps routing around ETH...
No Fork Required: Bitcoin’s First Quantum-Safe Transaction Just Happened
Bitcoin Magazine No Fork Required: Bitcoin’s First Quantum-Safe Transaction Just Happened Should fund managers dealing in Bitcoin...
Charles Schwab to Add Solana, Avalanche, and Chainlink to Its Crypto Trading Platform
Charles Schwab announced plans on Thursday to add Solana, Avalanche, and Chainlink to Schwab Crypto, the first expansion of the pl...
Kraken users briefly locked out after a flood of sanctioned crypto transactions
The activity, appearing to spread sanctioned funds to trigger account restrictions, occurred between Aug. 17 and Aug. 24.
Bitcoin Privacy Wallet Sparrow Issues Update After AI Flags Fixes
Developer Craig Raw said an AI-assisted review produced most of the fixes in version 2.5.4, though none appeared likely to put use...