Tané Delegate Thread

Delegate Platform
21

Proposal for Updating Block Proposer Rewards Policy to Lido on Ethereum SNOP on Block Proposals v3 (Snapshot)

Summary:

This proposal updates Lido’s Block Proposer Rewards Policy from v2 to v3, synchronizing node-operator duties with Pectra upgrades and Staking Router 2.0. It embeds APM governance, widens coverage to Simple DVT, Community Staking modules and more, and mandates at least one vetted MEV-Boost relay.

Vote: For

Rationale:

This proposal is a necessary response to the expansion of staking modules; it keeps the rule set current with the ecosystem’s evolution. We are confident that the required amendments and perspectives have been properly captured, leaving no critical gaps. By locking these updates into a single standard, the DAO can maintain clarity for operators and protect network security.

Decision on Kyber Network’s position in the Oracle Set: rotate to Caliber or remove and change the quorum (Snapshot)

Summary:

The proposal is to acknowledge Kyber’s internal spin-out by granting its oracle seat to Caliber and maintaining quorum at five of nine members; otherwise, Kyber will be removed and the DAO will search for a replacement under a five-of-eight interim quorum. On-chain actions implementing either rotation or removal will follow a successful Snapshot vote closing 1 Jul 2025.

Vote: Rotate Kyber Network to Caliber

Rationale:

We believe this proposal will preserve existing expertise because the engineers and infrastructure supporting Kyber’s oracle service are expected to migrate, at least in part, to Caliber. Therefore, we do not anticipate any significant decline in performance or uptime. Onboarding an entirely new team would raise costs and coordination risks without offering clear advantages, so we prefer this seamless transition.

DVT Integration Guidelines for the Curated Module Node Operators (Snapshot)

Summary:

This proposal coordinates DVT rollout inside the Curated Module by enabling key splitting for 20% of validators, giving operators freedom to choose Obol or SSV, and requiring client-diverse clusters to improve resilience. It pairs this with a structured incentive scheme of 20% operator and 80% vault rewards, updated Community Staking terms, and multilayer transparency measures so the DAO can monitor technical adoption and risk.

Vote: For

Rationale:

This proposal builds on DVT, which has proven record of raised uptime and efficiency, so broadening its use is the logical next step. We have also utilized DVT and appreciated the impact it made for our operation. The revised incentive split rewards both node teams and depositors, giving every party a stake in faster adoption. We expect this combination of proven tech and balanced economics to lift overall network performance with minimal added risk.

1 Like
22

Triggerable Withdrawals Framework in the Lido Protocol (Snapshot)

Summary:

This proposes implementing a Triggerable Withdrawals framework based on EIP-7002, enabling validator exits through the Execution Layer to reduce trust dependencies on Node Operators and Oracles. The system introduces the Validator Exit Bus (VEB) and Triggerable Withdrawals Gateway (TWG) with rate-limiting mechanisms to ensure secure and permissionless staking operations.

Vote: FOR

Rationale:

This proposal materially lowers reliance on individual node operators by allowing other actors to trigger validator exits, protecting stETH holders from withdrawal delays if an operator is compromised or unresponsive. It also enables truly permissionless modules like CSM by ensuring validators cannot hold ETH hostage when they underperform. We support the upgrade because it strengthens decentralization and risk management across the Lido protocol.

CSM v2 Final Rollout (Snapshot)

Summary:

CSM v2 represents an evolutionary upgrade featuring distinct node operator types including identified community stakers with preferential conditions. The rollout includes operational funding for reimbursements and systematic stake limit increases.

Vote: FOR

Rationale:

We endorse this proposal as CSM has demonstrated tangible progress in validator set diversification and meaningful decentralization impact. We view the enhanced economic framework as a logical evolution that will attract more independent community stakers while maintaining accessibility. Also, the 5% stakeShareLimit increase represents prudent scaling with no apparent risks that requires additional mitigation.

23

Vote #190 (Onchain)

Summary:

This proposal represents a combined vote, consolidating six previously discussed and approved governance items to streamline Lido DAO’s decision-making process. These items have undergone community validation via Snapshot and forum discussions.

Vote: Yes

Rationale:

  1. Rotate Lido on Ethereum Oracle Set member Kyber Network for Caliber: We voted in favor of this proposal at the Snapshot vote and see no new issues arising. Thus, we continue to support it.

  2. Increase CSM stake share limit from 2% to 3%: We voted in favor of this proposal at the Snapshot vote and see no new issues arising. Thus, we continue to support it.

  3. Enable a grace period for CSM Node Operators by setting keyRemovalCharge = 0: The “grace period” refers to a limited timeframe allowing existing CSM Node Operators to remove their validator keys without incurring any charges, which we believe is necessary and fair.

  4. Introduce a simplified CSVerifier for CSM: The simplified CSVerifier removes an unused verification method to reduce complexity and future maintenance overhead, which we understand as a similarly reasonable approach.

  5. Update the reward address and name for Node Operator ID 2 P2P.ORG - P2P Validator: This is an operational change, and as there are no issues with the configuration, we support this as well.

  6. Switch off Easy Track environment for PML, ATC, RCC entities, deprecated after Snapshot-approved transition to Lido Labs and Lido Ecosystem BORG Foundations: We support the transition to the Lido Labs and Lido Ecosystem BORG Foundations and, as part of that transition process, we also support this proposal.