Ignas Delegate Thread

Delegate Platform
41

88. Proposal: Authorize Lido EarnETH Loss Coverage Below 1% Threshold For The Kelp Incident (Snapshot)

  • Date Voted: May 4, 2026

  • Vote: For

  • Rationale: Acting now helps protect user confidence, reduce withdrawal uncertainty, and preserve Lido Earn’s credibility.

    Prioritizing user protection in exceptional cases like this is aligned with the DAO’s long term interests.

1 Like
42

Date Voted: May 13, 2026

89. Proposal: Adopt the Node Operator Type Assessment Framework for CMv2 (Snapshot)

  • Vote: For

  • Rationale: This is a meaningful step forward in how Lido recognizes and incentivizes Node Operator contributions.

    It introduces a structured, merit-based classification system that rewards genuine alignment whether through Ethereum infrastructure work, decentralization efforts, DVT adoption, or long-term DAO commitment.

    The tiered design is well considered: it avoids stacking incentives arbitrarily, builds in regular reassessment, and preserves DAO oversight on all critical decisions.

    This is exactly the kind of adaptable governance infrastructure CMv2 needs to scale responsibly. Voting yes.

90. Proposal: NEST: Automated LDO Buyback and Liquidity Provisioning (Snapshot)

  • Vote: For

  • Rationale: This system introduces a clear and rulebased mechanism that links protocol performance to LDO in a disciplined and transparent way.

    The design is conservative and LP mode strengthens LDO liquidity and creates DAO owned positions, improving market depth without relying on external incentives.

    I also think the flexibility is a strong point the ability to switch between LP and Treasury modes and expand revenue sources later gives the DAO room to adapt without redesigning the system.

    I support adapt NEST.

91. Proposal: Transition from GateSeals to CircuitBreaker (Snapshot)

  • Vote: For

  • Rationale: GateSeals expire, break after single use, and demand recurring DAO votes just to stay operational.

    CircuitBreaker replaces all of that with one permanent contract, proper committee accountability, and full DAO override.

    This is a good update. Voting yes!

92. Proposal: Should Pier Two continue in the Curated and SDVT sets following the acquisition by Bitmine Immersion Technologies? (Snapshot)

  • Vote: For

  • Rationale: Supporting the continuation of MAVAN in the Curated and SDVT sets.

    Given the unchanged technical setup and the operator’s established track record, there is no reason to disrupt continuity.

93. Proposal: Increase Easy Track transfer limits for Liquidity Observation Lab to align with EGG (Snapshot)

  • Vote: For

  • Rationale: This is just removing operational friction. The stETH limit increase is proportionate to LOL’s expanded mandate, and the stablecoin factory eliminates unnecessary manual overhead.

    Voting yes!

43

Date Voted: June 17, 2026

93. Proposal: Galaxy Node Operator Infrastructure Update (Snapshot)

  • Vote: For

  • Rationale: I support this proposal.

    The migration leverages the CMv2 transition to streamline infrastructure updates without requiring a separate key rotation, reducing operational complexity.

    Moreover, The CMC review did not identify material concerns, and Galaxy’s commitments to client diversity and ecosystem contributions provide additional value to the broader Lido operator set.

94. Proposal: Revoke Canonical Status of (w)stETH Bridge Endpoints on Selected Chains and Authorize NEC for Revocations (Snapshot)

  • Vote: For

  • Rationale: Voted yes as it helps keep Lido’s multichain strategy focused on networks where wstETH has meaningful adoption and ecosystem relevance.

    Revoking canonical status does not impact user funds or bridge functionality, but reduces unnecessary operational overhead and ensures official support is aligned with actual usage.

95. Proposal: Wind Down Simple DVT Module Regular Clusters (Snapshot)

  • Vote: For

  • Rationale: SDVTM has successfully achieved its objective of validating DVT within Lido, and CSM now provides a more scalable and sustainable framework for continued participation.

    The proposed transition paths and operator support measures help ensure continuity while reducing long term operational complexity for the protocol. Voted yes!

96. Proposal: Lido Labs Board Update: Appointment of Nemo as Director (Snapshot)

  • Vote: For
  • Rationale: Nemo has demonstrated strong commitment to the Lido ecosystem through his contributions across multiple initiatives. Voted yes!

97. Proposal: LIP-33: CMv2 and CSMv3 Architecture, Key Parameters, Rollout Plan (Snapshot)

  • Vote: For

  • Rationale: This proposal upgrades Lido’s staking architecture for Pectra compatibility, improves scalability and operator management, and strengthens the foundation for future protocol growth.

    Voted yes!

98. Proposal: LIP-35: Staking Router v3 Architecture and Key Parameters (Snapshot)

  • Vote: For

  • Rationale: This proposal is a critical infrastructure upgrade for Lido’s post-Pectra architecture.

    SRv3 enables balance based accounting, support for large validators, and efficient stake migration, providing the foundation required for CMv2 and CSMv3.

99. Proposal: Vote #202 (Onchain)

  • Vote: Yes
  • Rationale: I vote Yes. The underlying changes have already received community approval through Snapshot, and this proposal ensures their timely and efficient on-chain implementation.
1 Like