Besu Client Software Encounters Issues on Ethereum Network
On November 7th, the Ethereum community on Twitter uncovered disruptions within the Besu software, an Execution Client on the Ethereum network. Promptly addressed, this incident was swiftly mitigated, significantly minimizing potential risks.
Besu users may be experiencing downtime right now. Besu team is aware and on it – in the meantime, switch to another client or use @Rescue_Node while a fix is deployed
— EthStaker 🦇🔊 (@ethStaker) January 6, 2024
Reports emerged on November 7th highlighting glitches within the Besu software, prompting a rapid response encouraging validators to transition to an alternate software while awaiting bug fixes. The Besu team later confirmed the occurrence of a glitch on the mainnet, specifically tied to the data storage of various states.
A warning was issued to mainnet users via Twitter: “Attention Mainnet users! A recent Mainnet block triggered a bug in Besu’s state database. If you are validating with Besu, please review the latest hotfix patch notes.”
🚨Attention Mainnet users 🚨
A recent Mainnet block triggered a bug in Besu’s state database. If you are validating with Besu, please review the latest hotfix patch notes. They have details on how to get your node up and running:https://t.co/WZkLV3GqeY
— Hyperledger Besu (@HyperledgerBesu) January 7, 2024
The fix recommended a resync of the connected consensus client with a checkpoint sync, a maneuver designed to trigger a backwards sync in Besu to potentially rectify the state database issue. Users were advised to consult documentation for further guidance.
Moreover, the Besu team promptly released a temporary bug patch and urged validators using older versions to swiftly update.
Ethereum’s Twitter community added a perspective, considering Besu’s hiccup as a stroke of luck. If such an incident had occurred within Geth (the client currently accounting for over 84% of the Execution software share), the network might have faced more severe repercussions.
Diversification of software clients (both in Consensus and Execution phases) has long been recommended within the Ethereum community. However, despite recommendations, the issue persists, especially since the mid-2023 phase, notably after Geth surpassed the 80% market share threshold, widening the gap further.
The incident underscores the ongoing need for a diversified software landscape within Ethereum to mitigate potential risks and ensure the robustness of the network.
While Besu’s glitch was swiftly handled, it serves as a stark reminder of the importance of software diversity and ongoing vigilance within the Ethereum ecosystem.
- Dencun Upgrade: Ethereum’s Testing Set For Jan. 17 On Goerli Testnet, With Sepolia And Holesky To Follow
- Goerli Testnet Sunset: Ethereum Developers Urged To Explore Sepolia And Holesky
- Ethereum’s Vitalik Buterin Proposes Radical Shift In Proof-Of-Stake Validation