RockLogic already runs part of its Lido stake on Obol Distributed Validators. Now it is doubling down, moving all keys onto a client diverse cluster across three independent sites. 

For years, professional operators had to make tradeoffs. Use active-passive setups and risk a slashing event, or run a single node setup and accept the downtime. Legacy validator technology forces that choice, and RockLogic refused to make it. The team already runs 1,000 validator keys on Obol DVs in Lido's Curated Module, and is now moving its entire Lido stake to a client diverse cluster running on its own hardware.  No cloud, no large hosting provider. This is RockLogic doubling down on self sovereign, fault tolerant infrastructure.

An ecosystem partner

RockLogic is the professional node operator behind Stereum, one of Ethereum's most widely used node-management tools. The team runs validators and has operated on mainnet for years, and Stereum was one of the first tools to integrate Obol's Distributed Validator Technology. Operators only move their stake onto infrastructure they trust to perform. Moving their entire Lido stake after already running keys using Obol’s middleware is RockLogic's signal to the ecosystem that this is how validators should be run.

How RockLogic runs

DVs introduce active-active setups. But a cluster is only as distributed as the parts it is built from, and Rocklogic’s client diverse cluster is independent all the way down. 

No single compromise can produce a slashable message. Charon operates as middleware. It sits between the consensus client and the validator client while coordinating threshold signing. The validator's private key is generated through Distributed Key Generation, so the complete key never exists in one place and never loads into memory. A signature is produced only when a threshold of the cluster agrees. Compromise one machine or one signer and there is no assembled key to steal and no way to force a slashable signature.

No single machine failure can take the validator offline. A DV cluster runs active-active, not active-passive. Legacy failover setups keep a hot spare key that risks double-signing. An Obol cluster simply keeps attesting when a node goes offline. An outage can take a node offline or a machine can fail, and threshold signing continues among the remaining nodes.

Together these are the two failure modes that matter: slashing-averse and downtime-averse. RockLogic's cluster is built to withstand both.

"The failure mode that matters in staking isn't one node going down, it's thousands going down together because everyone runs the same client on the same cloud. A DV cluster only removes that risk if it's built out of genuinely different parts. Ours is: our own hardware at three independent sites, no cloud, and diverse consensus and execution clients across the cluster. That's why we're comfortable putting our entire Lido stake behind it." – Stefan Kobrc, Rocklogic Managing Parnter

What this means

Obol DVs continue to expand within Lido's Curated Module, and each operator that migrates reinforces the same trajectory: DVT is becoming the way professional operators run at scale. Legacy technology is brittle and structurally misaligned with where Ethereum is heading. Obol DVs are the staking endgame, and commitments like this are what that looks like in practice.