Blockdaemon Consolidates it's Lido Stake onto Obol

Lido's Curated Module v2 puts up to 2,048 ETH behind each validator key, and Blockdaemon is not putting those keys behind a single machine.

Every operator in Lido's Curated Module is about to move to 0x02 validator keys. CMv2 consolidates stake in the module onto compounding validators. One key where there used to be sixty-four and a fraction of the duties to track. Any operator running at scale will take that deal.

But, consolidating a large validator fleet concentrates risk. Each 0x02 key carries up to 64 times the stake it used to, so every offline minute costs 64 times more. The legacy answer to validator failure is active-passive setups: a hot spare key, and a promise that two machines will never run at once. That promise is outdated.

Blockdaemon is consolidating all of its Lido stake onto Obol Distributed Validators (DVs) as part of the CMv2 migration.

Why Obol

A Distributed Validator splits one validator key across a cluster of independent machines. Stake per key goes up. Risk goes down. Three properties make that true.

Charon is a middleware client. It sits between the consensus client and the validator client, intercepting API traffic to coordinate threshold signing across the cluster. It requires no tear-down of an existing stack.

Distributed Key Generation produces the validator's private key as key shares held locally by each node. The complete key never exists in one place and never loads into memory. There is no assembled key sitting on a machine for an attacker to take, which closes that threat by architecture rather than by policy.

Threshold signing requires a threshold of the cluster to agree before a signature exists at all. A 3-of-4 cluster keeps attesting and keeps proposing when a node goes down. This is active-active redundancy. There is no standby key, so there is no double-signing scenario to engineer around in the first place.

Those properties matter more after consolidation than before it as downtime now costs 64x what it used to.

Why Blockdaemon moved

Blockdaemon runs staking infrastructure for institutions. Custodians, exchanges, and asset managers delegate to it so they never have to think about validator operations, which leaves it with a narrower risk tolerance than almost any operator in the Curated Module. It secures over $110 billion in digital assets across 400 institutions.

Blockdaemon has run Obol DVs since June 2025 so the decision it made about consolidation came after four quarters of production data on Distributed Validator Technology (DVT). Every step has followed the same sequence: run it in production, measure it, commit more stake to it.

“Blockdaemon is proud to grow our share of Distributed Validator Technology based infrastructure by migrating our Lido staking operations to Obol Distributed Validators, furthering a more secure, decentralized, and institutional-ready staking ecosystem operated on Blockdaemon’s geographically distributed nodes across multiple Ethereum clients. As an early investor in Obol, this milestone reflects our continued conviction that Distributed Validator Technology represents the future of institutional Ethereum staking at scale,” - Demetrios Skalkotos, Blockdaemon’s Chief DeFi & Protocols Officer.

It’s early innings

The Curated Module is the largest pool of staked ETH on Ethereum and now is a moment in time in which operators can improve the resilience of their setups.

Operators are being handed a fleet that is smaller, denser, and less forgiving, and the setups they tolerated for years are asking to be upgraded. Ethereum's role as the world's credibly neutral settlement layer depends on a validator set that does not centralize as it consolidates. Distributed Validators are how those two things stay compatible.