StableLab Delegate Thread - Updated

Proposal: Vote #181
Vote: Yes
Rationale: In support of the motions to change Easy Track limits for PML and ATC, increase the Lido Stonks stETH limit to 12,000 stETH and reset spent amount, and update the node operator reward address.

Proposal: Establish the Network Expansion Committee (NEC)
Vote: Approve NEC
Rationale: In support of the NEC, it formalizes proven processes and reduces operational burdens while maintaining strong community oversight.

Proposal: Should Pier Two continue in the Curated Module Set following the acquisition of Numic?
Vote: For
Rationale: In support of Pier Two’s continuation, the LNOSG found no issues following the Numic acquisition and sees no reason to halt their operations.

Proposal: Should Alchemy continue in SDVT and LoP following the acquisition of Bware Labs?
Vote: For
Rationale: In support of Alchemy’s continuation, the LNOSG found no issues following the acquisition of Bware Labs and sees no reason to halt their operations. The transition is expected to be seamless, allowing Alchemy to maintain its role in Lido on Ethereum Simple DVT and Lido on Polygon without disruption.

Proposal: Should Nansen continue in SDVT following the acquisition of Stakewithus?
Vote: For
Rationale: In support of Nansen’s continuation, the LNOSG found no issues following the acquisition of Stakewithus and sees no reason to halt their operations. Nansen can continue its role in Lido on Ethereum Simple DVT without any disruptions or changes to current processes.

Proposal: Reevaluation of Lido on Polygon state
Vote: Sunset Lido On Polygon
Rationale: In support of sunsetting Lido on Polygon, the middleware has faced persistent challenges like low user adoption, limited ecosystem growth, and increased competition, making continued investment economically unsustainable.

Proposal: GOOSE 2024 cycle: Lido DAO goals for 2025
Vote: Adopt Goals
Rationale: Adopting Hasu’s GOOSE-2 goals for 2025 will strengthen LDO’s role in governance by exploring mechanisms like staking-linked incentives and dual governance to align tokenholder interests with the protocol’s long-term success. Establishing an open market for validators and expanding stETH’s ecosystem with tailored products for institutional stakers, restakers, and leverage seekers will drive broader adoption and reinforce Lido’s position in the Ethereum staking landscape.

Proposal: Vote #182
Vote: Yes
Rationale: In support of all motions in this on-chain vote as passed in Snapshot.

Proposal: CSM: Enable Permissionless Phase and Increase the Share Limit
Vote: For
Rationale: Enabling the permissionless phase and increasing the CSM share limit will accelerate Lido’s decentralization efforts by opening participation to a broader set of node operators and expanding validator capacity.

Proposal: Lido Alliance Grant Proposal
Vote: For
Rationale: In support of this proposal to approve funding for the continuation of Lido Alliance BORG activities because it supports expanding and strengthening the ecosystem by fostering collaborations and promoting stETH adoption and is aligned with GOOSE goals.

Proposal: Multi-EGG Continuity Grant Funding
Vote: For
Rationale: In support of Multi-EGG Continuity Grant Funding as it is essential for advancing Lido’s GOOSE goals, supporting key initiatives like dual governance deployment, CSM onboarding, and liquidity incentivization.

Proposal: Extend On-Chain Voting Duration
Vote: For
Rationale: In support of this proposal because extending the on-chain voting duration directly improves participation by accommodating diverse schedules and time zones while enhancing security with a longer objection phase.

Proposal: Update Lido on Ethereum Standard Node Operator Protocol - Validator Exits
Vote: For
Rationale: In support of this proposal because it updates the outdated Validator Exits Policy to align with the advancements in Staking Router 2.0 and the integration of new modules, and ensures clear expectations and streamlined processes for Node Operators.

Proposal: Should Solstice continue in the Curated set following the acquisition of Bridgetower?
Vote: For
Rationale: In favour of this proposal as it ensures continuity and stability within Lido’s Curated Module by allowing Solstice to maintain its operations under the existing registry address. The LNOSG’s review found no grounds to disrupt the operator’s participation, making this a reasonable and low-risk decision for the community.

Proposal: Should Attestant continue in the Curated set following the acquisition by Bitwise?
Vote: For
Rationale: In favour of this proposal as it ensures operational continuity by allowing Attestant to remain in the Curated set following its acquisition by Bitwise, as no technical or geographic changes have been made.

Proposal: Establishment of Lido Labs BORG Foundation as a Lido-DAO-Adjacent Foundation
Vote: Support the proposal
Rationale: In favour of the establishment of the Lido Labs BORG Foundation as it improves governance efficiency, transparency, and accountability by structuring research, development, and operational efforts under a legally compliant framework.

Proposal: Establishment of Lido Ecosystem BORG Foundation as a Lido-DAO-Adjacent Foundation
Vote: Support the proposal
Rationale: The Lido Ecosystem BORG Foundation supports institutional and ecosystem growth by fostering strategic partnerships, expanding stETH adoption, and streamlining cross-network integration. In favour of this.

Proposal: LEGO: Proposal to replace Tim Beiko with Eric Siu and update council members rotation rules
Vote: For
Rationale: In favour of this proposal as Eric’s background in ecosystem development and collaboration through the Ethereum Foundation positions him as a well-suited addition to the council.

Proposal: Vote #183
Vote: Yes
Rationale: In support of the motions to transition the Community Staking Module to a permissionless phase with an increased share limit, and to rename Node Operator ID 17 from BridgeTower to Solstice.

Vote #184

  • Vote: Yes (On-Chain)
  • Rationale: Voting in favor of these motions that have been pre-approved in off-chain votes because extending the voting and objection phases gives the community more breathing room to review proposals carefully and engage meaningfully, without rushing important decisions. Updating the GateSeal parameters and deploying new Easy Track factories also helps Lido’s operational teams move faster while keeping strong controls in place.

Lido DAO Ops Multisigs Policy 2.0

  • Vote: For (Off-Chain)
  • Rationale: Voting in favor because this policy brings much-needed clarity and tighter security standards to Lido’s multisig operations. It strengthens signer accountability, sets clear processes for rotations, and future-proofs operations as more multisigs move under BORG structures.

SSV Lido Module Proposal

  • Vote: For (Off-Chain)
  • Rationale: Voting in favor because expanding permissionless participation through SSV strengthens Lido’s long-term decentralization goals without sacrificing operational quality. Permissionless scaling is essential if Lido is to avoid centralization pressure as its validator set grows, and SSVLM’s design pragmatically abstracts away complexity that would otherwise block smaller, capable operators from participating.

MEV-Boost Relay Allowed List management via Easy Track

  • Vote: For (Off-Chain)
  • Rationale: Voting in favor because this improves operational transparency and gives LDO holders a more active role in updating critical infrastructure like the relay list.

EGG: Lido Labs BORG Foundation Grant Funding Request (Apr-Dec 2025)

  • Vote: For (Off-Chain)
  • Rationale: Voting in support of this proposal because this grant is critical to sustaining momentum on Lido’s biggest priorities for 2025 — especially Lido V3 development, dual governance rollout, and decentralized validator expansion. The proposal strikes a strong balance between near-term protocol upgrades and longer-term strategic research, while maintaining clear accountability through KPIs, reporting, and community oversight.

EGG: Lido Ecosystem BORG Foundation Grant Funding Request (Apr-Dec 2025)

  • Vote: For (Off-Chain)
  • Rationale: Supporting this proposal because it focuses on the critical path for Lido’s next phase of growth: expanding stETH adoption across DeFi and institutional channels, deepening liquidity, and strengthening brand presence. The clear KPIs and focus on both technical integration and market awareness make this a high-leverage use of funds.

Ensuring Compatibility with Ethereum’s Pectra Upgrade

  • Vote: For (Off-Chain)
  • Rationale: Voting in favor because ensuring full compatibility with Ethereum’s Pectra upgrade is critical to maintaining Lido’s operational stability. The technical plan is pragmatic, audit-supported, and minimizes disruption, while the fallback plan shows the team is thinking several steps ahead to protect stakers if needed.

Re-endorsement of wstETH on Starknet

  • Vote: Against (Off-Chain)
  • Rationale: Voting against because the Starknet deployment, while technically improved, has not yet met the governance, security, and process standards needed for re-endorsement. Endorsing now would overlook key safeguards outlined by the NEC and set a risky precedent for future integrations.

Vote #185

  • Vote: Yes (On-Chain)
  • Rationale: In support of motions to update oracle consensus versions and the CS verifier contract. Audits and deployment verifications confirmed.

Increasing LOL Easy Track Limits to align with Grant Requests

  • Vote: For (Off-Chain)
  • Rationale: In support of changing Easy Track limits to 6000 stETH for every 6 months to ensure operational continuity and align onchain security constraints.

CSM: stakeShareLimit and keyRemovalCharge parameters adjustment

  • Vote: For (Off-Chain)
  • Rationale: In support of proposed parameter changes to ‘stakeShareLimit’ and ‘keyRemovalChange’ to align with the current version of the community staking module.

Lido Alliance Application: Twyne

  • Vote: For (Off-Chain)
  • Rationale: In support of onboarding Twyne to the Lido Alliance due to potential benefits such as expanded use cases for stETH in DeFi, deeper Ethereum alignment, and expanded use cases for other Lido Alliance members.

Extend Delegate Incentivization Program through 2025

  • Vote: For (Off-Chain)
  • Rationale: In support of the extension of the Delegate Incentivization Program through 2025. The program has proved useful in terms of increasing delegated voting power and inspiring deeper, higher quality delegate engagement in Lido governance. We agree with comments suggesting that LidoDAO DIP could be adjusted to accomodate the more granular and nuanced aspects of decentralized governance.

Vote 186: Emergency Rotation of Chorus One Oracle

Vote: :white_check_mark: Yes (On-Chain)
Rationale: In support of emergency rotation of Chorus One Oracle.

LIP-28: Dual Governance — Implementation, Parameters, Committees

Vote: :white_check_mark: Yes (Off-Chain)
Rationale: Voting in favor because Dual Governance introduces critical safeguards for stETH holders in the event of contentious governance activity. By enabling a structured veto and withdrawal path, this mechanism reinforces DAO legitimacy and staker trust without halting progress. The system’s design is robust, stress-tested, and supported by credible audit work and modeling.

Establishment of the Auxiliary Proposer Mechanisms Committee

Vote: :white_check_mark: Yes (Off-Chain)
Rationale: Voting in favor because formalizing APM governance is both timely and essential. As proposer-layer innovations evolve, the DAO needs structured oversight to ensure only secure, value-aligned mechanisms are permitted. This committee brings technical depth, validator perspective, and accountability to a fast-moving frontier that directly affects Lido’s credibility and capital integrity.

Community Staking Module v2: Architecture and Fee Structure

Vote: :white_check_mark: Yes (Off-Chain)
Rationale: Voting in favor as this proposal lays the groundwork for scaling CSM responsibly. The updated architecture introduces needed flexibility, while the refined fee structure strikes a smart balance by keeping rewards competitive without over-subsidizing. This is a pragmatic step toward a more decentralized, permissionless validator set.

Vote 187: Post-Pectra Parameter & Oracle Updates, MEV Factories, CSM Fee Adjustments

Vote: :white_check_mark: Yes (On-Chain)
Rationale: Voting in favor. This proposal consolidates several discrete updates previously approved via Snapshot, including post-Pectra Oracle adjustments, MEV relay list management via Easy Track factories, a reduced key removal charge in the Community Staking Module, and a higher security threshold for Liquidity Observation Lab. All items have been audited or verified by MixBytes, minimizing risk.

Vote 188: Parameter Updates and Protocol Adjustments Post-Snapshot

Vote: :white_check_mark: Yes (On-Chain)
Rationale: Voting in favor because this onchain proposal enacts a suite of updates already approved via Snapshot and independently audited. These include critical parameter updates post-Pectra, MEV relay list management improvements, adjustments to the Community Staking Module, and increased operational flexibility for Liquidity Observation Lab.

Vote 189: Enable Dual Governance On-Chain

Vote: :white_check_mark: Yes (On-Chain)
Rationale: This is a big step toward real accountability in Lido. Dual governance has been talked about for a few years and now it’s finally live. By giving stETH holders veto power over onchain decisions, this upgrade balances the influence of LDO holders and hardens the system against capture. The design is clean, formally verified, and battle tested via audits. By activating this veto mechanism, the DAO acknowledges that those bearing economic and protocol-level risk should also hold a structural check on power.

DVT Integration Guidelines for the Curated Module Node Operators

Vote: :white_check_mark: Yes (Off-Chain)
Rationale: Voting in support because this expands DVT usage in a measured, risk-aware way. Curated operators gain flexibility to adopt intra-operator DVT while adhering to safeguards and reporting standards.

Decision on Kyber Network’s Position in the Oracle Set: Rotate to Caliber or remove and change the quorum

Vote: Option 1 - Rotate to Caliber (Off-Chain)
Rationale: Voting in favor of Option 1. Supporting Caliber as a direct replacement ensures operational continuity without compromising the oracle set’s integrity. The team has demonstrated strong infrastructure readiness, a successful Hoodi testnet run, and carries forward Kyber’s validator expertise under focused leadership. A full selection process is unnecessary overhead given the continuity and proven performance.

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

Vote: :white_check_mark: Yes (Off-Chain)
Rationale: Voting in favor as SNOP v3 brings necessary updates to match today’s validator landscape. It sharpens operator expectations, reflects the reality of MEV-Boost and modular staking, and reinforces decentralization and accountability without overreach. A well-calibrated move for long-term protocol resilience.

CSM v2 Final Rollout

Vote: :white_check_mark: Yes (Off-Chain)
Rationale: Voting in favor because CSM v2 brings meaningful upgrades to Lido’s community staking model, improving security, operator structure, and decentralization. The ICS framework strikes a good balance between open access and verification, and the phased stakeShareLimit increase is a sensible approach. The inclusion of a reimbursement mechanism reflects thoughtful protocol maturity.

Triggerable Withdrawals Framework in the Lido Protocol

Vote: :white_check_mark: Yes (Off-Chain)
Rationale: Voting in favor because Triggerable Withdrawals close a core trust gap in Lido’s architecture. Today, validator exits hinge on Node Operator cooperation, a bottleneck that threatens staker autonomy and protocol resilience. This framework rebalances that power, giving the DAO and stakers the tools to enforce exits independently. It’s a decisive move toward permissionless staking, and a critical safeguard against the kind of governance gridlock or operator failure that could otherwise stall withdrawals.

Vote #190
Vote: Yes (On‑Chain)
Rationale: Supporting this proposal as it implements a coordinated batch of cleanups and upgrades with clear DAO precedent. It finalizes the Kyber → Caliber oracle rotation approved in Snapshot, responsibly raises the CSM stake share limit from 2% to 3%, enables a grace period via keyRemovalCharge = 0, simplifies the verifier setup, and updates reward addresses. Also backs removal of deprecated Easy Track factories tied to now-defunct orgs. All items have prior discussion and audit coverage where applicable