Vitalik Buterin Proposes Native DVT for Ethereum, Ethereum Foundation Stakes 72,000 ETH Using DVT-Lite

Ethereum co-founder Vitalik Buterin has proposed integrating native distributed validator technology directly into Ethereum’s staking protocol, allowing multiple independent nodes to operate as a single grouped validator identity to enhance security and decentralization.

The proposal comes as the Ethereum Foundation begins staking 72,000 ETH using a simplified DVT-lite implementation, aiming to demonstrate that distributed staking infrastructure can be made “maximally easy and one-click” for institutional participants.

Ethereum Foundation’s DVT-Lite Implementation

Staking Deployment

The Ethereum Foundation has commenced staking 72,000 ETH using a DVT-lite approach, according to statements published on March 10, 2026. The implementation is designed to simplify distributed staking operations by automating configuration and coordination among multiple nodes.

The project aims to create a streamlined process where institutions can select which computers run their nodes, generate a configuration file with shared keys, and have everything set up automatically. The stated goal is to make distributed staking as simple as running a Docker container or Nix image with one-click or single-command-line deployment per node.

Vision for Institutional Staking

The Ethereum Foundation expressed hope that this project will make it “maximally easy and one-click to do distributed staking for institutions.” The initiative challenges the notion that running infrastructure must be complex and reserved for professionals, with developers stating: “The idea that ‘running infrastructure’ is this scary complicated thing where each person participating must be a ‘professional’ is awful and anti-decentralization, and we must attack it directly.”

The approach envisions nodes automatically discovering each other, networking configured automatically, distributed key generation occurring without manual intervention, and staking commencing seamlessly. The foundation indicated plans to use this system more broadly and hopes other institutions holding ETH will stake using similar methods.

Vitalik’s Native DVT Proposal

Technical Architecture

In a post published on the Ethereum Research forum, Buterin outlined a design for “native DVT” that would allow validators to register multiple independent keys that act together as a single grouped validator identity. Under the model, actions such as block proposals or attestations would only be considered valid if a threshold number of participating identities signed off.

“DVT is a way for Ethereum stakers to stake without fully relying on one single node,” Buterin wrote, adding that the validator would continue operating correctly “as long as more than two-thirds of the nodes are honest.” Unlike existing DVT implementations that often rely on complex setups and external coordination layers, Buterin’s proposal would bake the mechanism directly into the protocol.

Validators holding at least multiples of the minimum required stake would be able to specify up to 16 keys and a threshold for signing, effectively running several standard nodes that act together as a single validator identity. The design aims to add only one extra round of latency for block production, introduce no additional delay for attestations, and remain compatible with any signature scheme.

Decentralization Benefits

Buterin framed the proposal as a lever for decentralization. By making fault-tolerant staking easier to manage, native DVT could enable security-conscious individuals and institutions to stake on their own rather than delegate funds to large providers. This shift would improve measurable decentralization across Ethereum’s validator set, including metrics such as the Nakamoto coefficient.

The proposal follows growing real-world use of DVT at the infrastructure level. In August 2025, Kraken rolled out distributed validator technology across its Ethereum staking operations using SSV Network, becoming one of the first major exchanges to deploy the setup at scale.

Current DVT Landscape and Implementation Gap

Existing Solutions

While DVT systems have proven viable in production environments, Buterin noted that they remain operationally complex—a gap he believes protocol-level support could close. Current implementations typically require external coordination layers and complex setups, creating barriers to adoption for smaller operators and institutions seeking simple deployment options.

Community Discussion

The native DVT proposal remains at the discussion stage and would require extensive review and consensus within the Ethereum community before any path to implementation is pursued. Buterin’s pitch arrives shortly after Ethereum staking reached an all-time high, with nearly 30 percent of ETH’s supply now locked in the staking contract.

FAQ: Ethereum DVT and Staking

Q: What is Distributed Validator Technology?

A: DVT allows multiple independent nodes to operate together as a single validator identity, requiring a threshold of signatures for actions to be considered valid. This reduces the risk that a single node failure or compromise could take a validator offline while preserving slashing protections.

Q: How does native DVT differ from existing implementations?

A: Native DVT would be built directly into Ethereum’s protocol rather than relying on external coordination layers. Validators holding multiples of the minimum stake could specify up to 16 keys and a signing threshold, effectively running several standard nodes as one validator with minimal additional latency.

Q: What is the Ethereum Foundation’s DVT-lite project?

A: The Ethereum Foundation is staking 72,000 ETH using a simplified DVT implementation designed to make distributed staking easy for institutions. The project aims to automate node configuration, networking, and key generation to achieve one-click deployment for distributed validator setups.

Q: How does DVT improve Ethereum decentralization?

A: By making fault-tolerant staking easier to manage, DVT enables security-conscious individuals and institutions to stake independently rather than delegating to large providers. This spreads validator control across more independent operators and improves metrics like the Nakamoto coefficient.