
Six Ethereum execution clients. Same bare-metal hardware. The fastest fully syncs in 1.5 hours. The slowest takes 8+ days. Cross-client behavior on Ethereum is more uneven than most people assume. So we measure it. stereumlabs.com

Powering Ethereum infrastructure. Home of StereumLabs — AI-powered observability for Ethereum nodes. Plus Stereum OSS · StereumPlus · Fungl.

Six Ethereum execution clients. Same bare-metal hardware. The fastest fully syncs in 1.5 hours. The slowest takes 8+ days. Cross-client behavior on Ethereum is more uneven than most people assume. So we measure it. stereumlabs.com

Some detail on the setup, now live with the first deposits in: six Charon nodes across three sites, two per site. Duties need four, so a full site can go offline and the cluster keeps signing. The same margin makes updates rolling instead of scheduled downtime.
5 months ago, @Rocklogicgmbh became one of the first to run Obol Distributed Validators inside @LidoFinance Curated Module. Now, they're going all in. In CMv2, Rocklogic will run it's entire Lido stake on Obol DVs. No cloud. No large hosting provider. Read the full blog post, linked below. ⬇️

The Identified DVT Clusters type is the interesting one here. Stereum Launcher already handles Obol and SSV cluster setup, plus Lido CSM, across 10+ EL and CL clients. Free and open source. stereum.com
2. CSMv3: Expanding Permissionless Staking Through this upgrade Lido CSM becomes even more reliable and operator-friendly. Alongside multiple under-the-hood technical improvements, the primary new features are: • New Node Operator type: Identified DVT Clusters • Native Node Operator reward splitting • Permissionless stake share increase through the lightweight Easy Track governance

The client diversity pillar is the one we can actually help with. Every EC x CC pairing on our fleet runs on identical hardware, and the per-pairing numbers are public.
Lido (@LidoFinance) published the first CMv2 operator type assessment. Two operators were assigned the Decentralization Operator type: @everstake_pool and RockLogic. Client diversity is the heaviest pillar in that score: up to 30 points, geography 20, infrastructure 10.

Join the Lido Community Call next Thursday. Catch up on what’s next for the Lido staking modules, Lido's recent Web3SOC certification, and guest sessions on client diversity. Add it to your calendar: luma.com/pmb473ba

Full breakdown: per-EC pruning observability, the Nethermind v1.37.1 inline-newPayload trade-off, Ethrex with zero pruning metrics, Reth still in initial staged sync, EIP-4444 implications. docs.stereumlabs.com/blog/et…

Sync-committee duties get hit before attestations. A late sync-committee message misses the next block's sync_aggregate outright. An attestation still has one slot of grace. Today at @ethStaker's Fast Finality call (15:00 UTC), three of five ECs on Nimbus cross the deadline.

On Nimbus, three of five synced ECs cross the 4-second engine_newPayload deadline at P99: Nethermind 4.44s Geth 4.67s Ethrex ≥5.00s Same Nethermind on Lighthouse: 1.40s. On Prysm: 1.05s. The deadline is a pairing property, not a per-EC one.

Five synced ECs on the same Ethereum mainnet: Erigon: ~509 GB Ethrex: ~598 GB Nethermind: ~1,225 GB Besu: ~1,261 GB Geth: ~1,688 GB 3.3× spread, driven by retention architecture. Numbers are upper bounds (hosts rebuilt in 7-16 days). And disk is only half of it.

Full breakdown: 6 ECs, 130-to-24 peer-count spread, 50,000× churn-rate spread, eth68 hard caps on Erigon, and why DevP2P has no diversity-aware peer scoring like gossipsub does. docs.stereumlabs.com/blog/ec…

Adjacent finding: same Geth on bare-metal (port 30303 open) = 50 peers. On GCP (default firewall, port blocked) = 15 peers. CC peer count looks fine throughout. The EC is silently running 70% degraded. Lots of cloud nodes probably are.

What that means in practice: if Reth ships a networking regression, that Besu node drops from 24 to 6 peers. Gossip propagation breaks down at 6. A 12% client failure functionally degrades an 11% client. 2× amplification, invisible in aggregate stats.

Aggregate Ethereum client diversity: 'no client over 55%.' The view from an average Besu node on our fleet: 75% of its 24 peers are Reth. A 12% slice of the network becomes 75% of one node's reality.

Stereum Launcher v2.4.8 is out. - Ubuntu 26.04 support Auto-updates on startup. MacOS users: download the dmg manually and enable via System Settings. github.com/stereum-dev/ether…

Three more findings in the 90-day census: - Geth is the only EC whose Prometheus reorg counter ever increments - Nethermind & Reth export it but it never moves - Besu, Erigon, Ethrex don't export one at all docs.stereumlabs.com/blog/et…

It gets worse in the matrix. The same EC behind two CCs produces 2-5× different reorg counts: - Prysm + Besu: 69 per host - Prysm + Nethermind: 280 per host A fixed alert threshold doesn't port between pairings. Re-baseline after every EC change.