Vitalik Buterin has outlined a “Native Distributed Validator Technology,” or Native DVT, proposal on Ethereum Research, arguing that DVT should be built directly into the Ethereum protocol layer. The idea is to improve network security and decentralization without adding a large amount of extra system complexity.
DVT is meant to reduce reliance on a single node
Distributed validator technology allows a validator to avoid depending entirely on one node for staking operations. Instead, validator keys are split across multiple nodes, and block proposals and attestations are completed through threshold signatures. As long as more than two-thirds of the nodes continue operating honestly, the validator can remain active on the network, lowering the chance of slashing or inactivity leak caused by a single point of failure. The structure is straightforward: one failed machine does not automatically take the validator offline.
Existing DVT solutions already include ssv.network and Obol, and some exchanges and institutions have deployed them in production. Buterin said current designs often come with heavier architecture, requiring extra coordination between nodes and additional networking channels. He also pointed to their reliance on the linear properties of BLS signatures as a possible long-term concern.
Up to 16 separate keys under one grouped validator identity
Under the proposal, a validator with a multiple of the minimum staking threshold in ETH could configure up to 16 independent keys and assign a signing threshold. Those keys would operate as separate “virtual identities” at the technical level, while the protocol would treat them as a single grouped validator identity. A block production or validation action would count as valid only when the required number of keys had signed, and rewards or penalties would be assigned on that basis.
Buterin also warned about weak threshold settings. If the threshold is set too low, such as at or below half of the total key count, validators could face penalty risk even without malicious behavior. He said that kind of configuration is not recommended.
Low implementation overhead is central to the proposal
One of the main claims behind Native DVT is simplicity. Users would only need to run multiple standard Ethereum nodes rather than depend on a complex external coordination layer. According to Buterin, the design would add one extra round of delay during block production, while leaving the broader validation flow largely unchanged. He also said the model could work across different signature schemes instead of being tied to one specific cryptographic property.
Beyond fault tolerance, Buterin framed Native DVT as a way to ease staking concentration. If larger ETH holders and institutions can stake more safely through multi-node setups they operate themselves, reliance on major staking providers could fall. That, in turn, could improve validator distribution across Ethereum and support decentralization metrics such as the Nakamoto coefficient. The proposal remains at the discussion stage, and any move toward inclusion in Ethereum’s core protocol would still require extended community review, testing, and consensus.