Batch Voting Date: June 30th, 2025
Proposal: Curated Module Intra-Operator DVT Guidelines
Vote: For
Rationale: We vote yes as this proposal lays the groundwork for safely integrating Distributed Validator Technology (DVT) into Lido’s most critical staking module—the Curated Module—without compromising its high operational standards. By allowing intra-operator DVT, it improves fault tolerance and validator resilience while keeping trust boundaries clear. Operators can now adopt DVT internally to test redundancy and prepare for more decentralized validator setups, backed by well-defined testing requirements and reward mechanics via the Decentralized Validator Vault. The proposal builds on proven outcomes from the Simple DVT Module and strategically aligns with Lido’s ReGOOSE goals for resilience and decentralization. It introduces clear incentives, technical guardrails, and smart fund distribution, all while preserving Lido’s reputation for reliability. This is a thoughtful evolution, not a radical shift—one that encourages experimentation while protecting the core protocol.
Vote: YES on Option 1 – Rotate Kyber Network to Caliber
Rationale: We vote yes to rotate Kyber Network to Caliber, as this maintains continuity in oracle operations without compromising security or reliability. The Caliber team shares direct lineage with Kyber and has already demonstrated operational competence during its Hoodi testnet run. Given their active validator role across multiple chains and robust infrastructure setup—including 100% uptime claims, redundant nodes, and responsible key management—Caliber is well positioned to take over seamlessly. Launching a full oracle search would introduce unnecessary complexity and risk delays, whereas this rotation preserves quorum integrity and builds on existing trust. This is a pragmatic handover that honors both operational readiness and DAO efficiency.
Proposal: Lido on Ethereum – SNOP v3: Operator Expectations on Block Proposals
Vote: For
Rationale: We vote yes to adopt the SNOP v3 guidelines, as they represent a pragmatic step toward aligning Lido node operator behavior with Ethereum’s long-term health. The proposal encourages operators to follow socially accepted norms around block building—favoring builders with censorship-resistant policies, running local relays, and avoiding exclusive relay usage—while remaining non-binding and adaptable. This approach supports credible neutrality without being overly prescriptive, allowing flexibility across different setups and jurisdictions. It also establishes a clear reference point for community expectations, helping the DAO address MEV-related concerns through transparency and guidance rather than enforcement. Overall, SNOP v3 reflects a well-balanced governance tool that can evolve with the protocol.