Improving Censorship Resistance Using DVT
summary
SSV's DVT splits an Ethereum validator into shared keys using BLS threshold signatures plus a lightweight consensus and optional DKG so no single operator holds the key; clusters example: seven operators with a 4-of-7 threshold mixing four large institutional stakers and three solo operators, which lowers censorability even if ~five entities control ~two thirds of stake. Implementation runs on mainnet today via a contract-based DVT network with no protocol changes.
AI-written summary · about
chapters (9)
- 0:00DVT and censorship resistance
- 1:25Centralization risks in staking
- 3:13Types of censorship impacts
- 5:20Mitigating censorship via decentralization
- 6:03DVT splits validators into shares
- 7:49Censorship-resistant validator clusters
- 10:44DVT deployment and regulatory scenarios
- 12:11SSV’s DVT Network overview
- 13:16Summary and call to action
related talks
17mState of distributed validators in 2025
18mMEV Minimization on L2: Solution Space and Design Constraints
42mBeyond Blockchain: Convergent Consensus
20mChar: The Infrastructure Bet Underneath Every Bitcoin L2
31mProofless Consensus & Client-side Validation
25mCollator Protocol & Censorship Resistance
31mBFTree — Scaling HotStuff to Millions of Validators
47mCant we just agree