In a move toward a more diverse Ethereum-running client ecosystem, staking provider AllNodes presentation A complete transition from Geth to Besu. With this change, AllNodes eliminated the use of Geth from its entire network of 23,895 nodes, marking a milestone in its ongoing efforts to reduce the current centralization around Geth, its majority client.
AllNodes are migrated to Besu.
The non-custodial staking provider said in a post to Geth is the most widely used running client for Ethereum nodes, but analysts are concerned about its dominance and potential security vulnerabilities if Geth is exposed to bugs.
The transition to Besu is consistent with AllNodes’ commitment to providing the most secure and stable staking infrastructure to its customers. Developed by ConsenSys, Besu is a high-performance, secure execution client that offers several advantages over Geth.
This development significantly improves decentralization efforts for Rocket Pool, an Ethereum staking protocol that utilizes mini-pools. Rocket Pool’s minipool operators are free to utilize AllNodes’ staking and node hosting services. Even though some of Rocket Pool’s minipool operators still use Geth, AllNodes’ decision to switch to Besu further strengthens Ethereum’s resilience to potential client-side errors.
The current Ethereum validator landscape still heavily favors Geth. Data on Client Diversity show More than 75% of all validators rely on this client. However, given the current awareness that client errors can negatively impact network stability, it is likely that more staking providers will diversify their base with others following AllNode. As more validators are distributed across Nethermind, Geth, Besu, and other clients, Ethereum will become more resistant to potential forks and security issues.
There is no recourse for Ethereum node operators if Geth fails.
Marius, an analyst for explained Anyone can use any client, and they are even drawn to Geth, the first and most popular Ethereum running client. But the analyst claims there will be no “bailout” if the network diverges.
Buggy Geth inevitably exposes validators to the risk of catastrophic loss, causing a network fork as it already controls more than 66% of the nodes needed for finality. Validators running those clients can receive a penalty of up to 32 ETH, effectively eliminating their stake.
The Ethereum network typically “cuts” a validator node’s stake when its reliability falls below 100%. The longer you are offline, the higher the slashing penalty.
Featured image from Canva, chart from TradingView