The Ethernodes data has been removed.
The data is a representation of what clients are showing free peers and it's not well understood how this correlates to an overall picture of what clients are currently in use. For now, survey data (from execution-diversity.info) is considered the most reliable source of information for the state of execution client diversity.
Based on 73.6% self-reported network coverage with the remaining assumed to be mostly Geth.
Many know client diversity is important for a more resilient network, but they don't understand why or just how essential it is. It's not only important — it's critical. If a single client is used by 2/3rds (66%) of validators, there's a very real risk this can result in disrupting the chain and monetary loss [1, 2] for node operators.
It takes 2/3rds of validators to reach finality. If a client with 66%+ of marketshare has a bug and forks to its own chain, it'll be capable of finalizing. Once the fork finalizes, the validators cannot return to the real chain without being slashed. If 66% of the chain gets slashed simultaneously, the penalty is the whole 32 ETH.
So why is >33% marketshare still undesirable? If a client with >33% marketshare forks, it will prevent the chain from finalizing. That's why <33% marketshare is the goal for all clients.
Execution clients are not immune. The risks mentioned above apply to both consensus clients and execution clients equally.
| Client | Github | Docs | Chat | Status | Support | Language | Donate |
|---|---|---|---|---|---|---|---|
| Akula | deprecated | - | - | ||||
| Besu | stable | Linux, Win, macOS | Java |
| |||
| Erigon | - | alpha & beta | Linux, Win, macOS, ARM | Golang | |||
| EthereumJS | alpha | Linux, Win, macOS | TypeScript | ||||
| Geth | stable | Linux, Win, macOS, ARM | Golang |
| |||
| Nethermind | stable | Linux, Win, macOS, ARM | .NET |
| |||
| Nimbus | pre-alpha | - | Nim | - | |||
| Reth | stable | Linux, Win, macOS, ARM | Rust | - | |||
| Silkworm | - | pre-alpha | Linux, Win, macOS | C++ |
Note: Donations made to Protocol Guild are distributed among Ethereum protocol contributors, including client teams. All recipients and splits can be seen here.
For an automated tool (with a GUI) to switch execution clients,
see Accidental-Green's Ethereum Client Switcher
Error: Select both To and From clients.
There are no guides for this migration yet.
Submit Guide