Vitalik's latest proposal: Embedding DVT into the Ethereum protocol layer, a new decentralized path for validators

robot
Abstract generation in progress

【CoinDesk】Ethereum co-founder V神 has proposed a new idea on the Ethereum Research forum—integrating Distributed Validator Technology (DVT) directly into the protocol layer.

Sounds complicated? Simplified, it means validators can register multiple independent keys and work together as a group. As long as the preset signature threshold is reached, the block proposal or attestations are considered valid. The obvious benefit is significantly reducing the risk of single points of failure or node outages due to attacks. Importantly, even with this mechanism introduced, the existing slashing protections remain operational.

Most current DVT solutions on the market rely on external coordination layers, which are complex to deploy and depend on third parties. V神’s approach is different—it embeds DVT directly into the protocol itself. Validators holding over 32 ETH can set up to 16 keys and customize thresholds, effectively merging multiple standard nodes into a single validator identity.

In terms of performance, the additional overhead is almost negligible—only adding a slight delay to block production, with zero impact on attestation latency. It also supports any signature scheme, reducing reliance on certain cryptographic assumptions that might carry higher risks.

From a decentralization perspective, this makes it easier for individuals and small organizations to participate in staking in a self-custodial, fault-tolerant manner without relying on large staking service providers. This could improve the decentralization level of Ethereum’s validator set (such as the Nakamoto coefficient). However, this proposal is still in early stages, and further community discussion and consensus are needed.

ETH2,12%
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • 4
  • Repost
  • Share
Comment
0/400
TestnetFreeloadervip
· 11h ago
This guy wants to cause trouble again, directly embedding DVT into the protocol layer... sounds good in theory but actually implementing it is still a problem, right? --- 16 custom key thresholds? Feels like a toy for big players, small investors still have to look at their faces. --- Not bad, the risk of single point of failure is reduced, but does this make the validator threshold higher again? --- I just want to ask, when will this go live on the mainnet, and how much longer do we have to wait? --- Embedding directly into the protocol layer... V神 really wants to turn Ethereum into an ironclad fortress. --- Wait, can slashing protection still be used? What if someone maliciously manipulates 16 keys? --- Another "looks great" idea, but in practice, it might turn out to be a mess. --- This means that large validator pools will become even more dominant. --- Honestly, it feels like it's adding more complexity. Is Ethereum's ship going to sink too deep?
View OriginalReply0
AirdropAutomatonvip
· 11h ago
What is this V神 up to again? Directly integrating DVT into the protocol layer sounds like reducing risks for big validators. If you ask me, it's still that same logic—no matter how elegant the technology, the benefits ultimately go to the wealthy. But on the other hand, it's really good that slashing protection can still operate normally. The design in this area is indeed quite thoughtful.
View OriginalReply0
DAOdreamervip
· 11h ago
What are you doing again? Forcing DVT directly onto the protocol layer... How is the old V thinking this time? Damn, isn't this turning validators into small groups fighting together? Are we about to enter a new cartel era? Starting with 32 ETH and setting up 16 keys, such a scale... Isn't this just covertly raising the participation threshold again? Slashing still works as usual, right? But if all 16 keys are slashed at once, will it just crash immediately? It feels like another wave of infrastructure innovation is about to be triggered, but can this really be implemented or is it just another PPT plan? Can anyone explain why it has to be embedded at the protocol layer? Are the current external solutions really that weak? If this thing really goes live, validators will have even less to eat... It seems like Lido folks are about to start figuring out how to wrap this new thing...
View OriginalReply0
OnchainDetectivevip
· 12h ago
I need to look at the details here... What is Satoshi doing now? According to on-chain data, once DVT is truly embedded at the protocol layer, the power structure of these major validator accounts will be reshuffled.
View OriginalReply0
  • Pin

Trade Crypto Anywhere Anytime
qrCode
Scan to download Gate App
Community
  • 简体中文
  • English
  • Tiếng Việt
  • 繁體中文
  • Español
  • Русский
  • Français (Afrique)
  • Português (Portugal)
  • Bahasa Indonesia
  • 日本語
  • بالعربية
  • Українська
  • Português (Brasil)