Lido

We generally agree with the overall direction of Hasu's proposal, and thus voted for this proposal. However, we still have a concern regarding the main focus of the goal #1, Strengthen LDO’s Role in Governance. We acknowledge the importance of strengthening alignment across the DAO through revisions to the LDO token design. But given the presence of other challenges and the likelihood that implementing changes to the LDO token design will take considerable time, we do not believe it should be prioritized as the most critical theme in governance at this stage.

We do not see any reason to discontinue their operation because - As communicated by LNOSG, they have evaluated that the transition will be smooth and without issues. - Bware Labs itself announced the continuity of its operational structure after acquisition.

Similar to Bware Labs' case, we do not see any reason to discontinue their operation because - As communicated by LNOSG, they have evaluated that the transition will be smooth and without issues. - Its operational structure after the acquisition was announced to remain the same as before the acquisition.

We voted for this proposal, because - Even when an incident has occurred, it is proper to take corrective measures and gradually resume operations. - This principle remains universal, even in the case of acquisition. - By thoroughly testing through a trial run on the testnet, a certain level of safety can be ensured. That being said, we believe it's worth regularly reviewing and discussing the possibility of replacing curated NOs —　not just those with prior incidents — to neutrally consider if there are other NOs more suitable for the curated set.

We voted for sunsetting Lido on Polygon, because - The future direction of the Polygon POS chain, especially its position within Polygon's AggLayer, is unclear. - Growth is difficult due to factors beyond the control of Shard Labs and Lido DAO. - Instead, the entire Lido DAO could focus on businesses that leverage stETH, which has some huge advantages in the market.

With a high degree of operational maturity, it is reasonable to improve efficiency through the introduction of an optimistic governance process. As a participant in governance, we support this proposal and will carefully monitor it to ensure that the committee functions correctly within this framework.

1. Change Easy Track limits for PML & ATC We support this proposal as having flexibility in budget limits is reasonable. That being said, we feel the scope of approval may be overly generous compared to current operational requirements. 2. TMC-4: Increase Stonks execution limits The proposed change appears to be a reasonable decision to improve operational efficiency, especially given that no issues have arisen with Stonks so far. 3. Simply Staking Node Operator Reward Address change We have reviewed this proposal and found no issues, including any discrepancies with the specified address.

Preconfirmation has been a hot topic around Ethereum staking and was also the initial scope in reGOOSE, so this kind of initiative makes sense. However, it is still unclear to what extent Lido DAO should support preconfirmation, and this should become clear after thorough research such as Nethermind's research on preconf's economic viability.

Currently, we want to grow both SDVT and CSM, and this seems like a very fair decision because the point incentives provided for SDVT's growth can also be utilized to incentivize deposits to CSM. In the future, it would make sense to have a separate vault for CSM, following the roadmap of Staking Router development, and let the market decide which staking module to be in favor.

We voted to recognize this bridge as canonical after checking the audits were done for these implementations. This should lead to the further expansion of stETH.Since the safety and effectiveness of code audits can vary depending on factors such as the auditor, reviews and checks like those performed by @TheDZhon are extremely helpful in enhancing security.

We supported all three of the proposals listed above. Especially, approving CSM is an important step toward enhancing the decentralization of Lido and Ethereum, and we didn’t find any issues with supporting them. We also acknowledge that the audits have been done by Ackee Blockchain and MixBytes. Everything seems on track, so we support this proposal as we have before.

1. stETH on L2 We support this proposal as it enhances the accessibility of stETH across L2 networks, leveraging existing wstETH infrastructure. This expansion will provide users with a consistent experience across both L1 and L2. 2. Organize the Lido Alliance Program as a Lido-DAO-Adjacent BORG We support setting up an EasyTrack for the Lido Alliance Operational Multisig to simplify operations. The approved BORG entity provides a legal framework for agreements without exposing Lido DAO to legal risks. This structure keeps Lido DAO decentralized while supporting the Alliance’s needs, with EasyTrack improving fund management.

We recognize the strategic importance of the Lido Alliance and the need for a legal structure to facilitate agreements in its operations. The BORG structure provides a balanced approach, offering legal capabilities without directly exposing Lido DAO to potential legal risks. At the same time, we’d love to contribute to gradual improvements such as increasing transparency and appropriately handling such projects as Lido DAO.

As shared in the Snapshot page, the responses from both CryptoManufaktur and Galaxy indicate that there will be no significant changes in the key factors listed above, at least for the short term. This strongly suggests that the quality of the node operation by Galaxy will remain consistent with what CryptoManufaktur has been providing. Additionally, as a topic to be discussed in the future, we believe there’s a need for implementing a routine assessment of existing Node Operators in Lido’s Curated Module. This process would serve two crucial purposes: 1. To track any changes that may occur to Galaxy (or any other operator) in the mid/long term and regularly check their eligibility as a Node Operator in Lido’s Curated Module. 2. To identify and potentially remove Node Operators from Lido’s Curated Module that are no longer meeting the initial selection criteria, either due to changes in their operation or failure to keep up with the latest best practices of node operation. This proposed assessment process would ensure the ongoing quality and reliability of Lido’s Curated Module.

Same as the one made for Vote #177

1. Oracle member rotation While there have been several interests from potential oracle operators, we agree to choose MatrixedLink for the rotation on this occasion as they are one of operators that have experienced the Oracle testnet run and look for more improvements to be introduced with Second Opinion Oracle project. 2. Node Operator name & reward address update This is a highly administrative matter, and we don’t have any particular objections to it. This kind of administrative approval should not need snapshot or on-chain vote. As Izzy mentioned in the forum, setting up Easy Track for this kind of case would be helpful. 3. On-Chain Delegation Having good governance is the key for DAO to be successful. However, there have been several proposals that were rejected due to the lack of the amount of votes. This implementation will enable delegating onchain voting power for LDO holders and thus more voting power can be utilized for the governance. This is an important step for strengthening Lido DAO governance.

Expansion of wstETH to Mode is favorable, as Mode could potentially be a DeFi hub of the Superchain ecosystem and bring huge utility to wstETH. The only concern was the security. After reviewing the assessment provided by the working group of Lido on Ethereum protocol contributors, we do not see any issues with using this bridge.

Unlike previous bridge proposals, this one uniquely combines Wormhole and Axelar, rather than utilizing a canonical bridge for a specific rollup or chain. While TheDZhon’s suggestion to add more bridges with a 2/3 threshold would undoubtedly enhance security in the future, the current proposal seems to provide adequate security measures for the time being.

While there have been several interests from potential oracle operators, we agree to choose MatrixedLink for the rotation on this occasion as they are one of operators that have experienced the Oracle testnet run and look for more improvements to be introduced with Second Opinion Oracle project.

As stated in the updated scorecard, there are a lot of points to be improved in Lido DAO’s governance. As we saw success of similar delegate programs in other DAOs, we believe introducing a program to invite publicly declared delegates to increase quality delegates and incentivizing them based on particular conditions to improve the voting process in the Lido DAO should be a huge step towards better decentralized governance.

We’ve been supporting Lido’s staking decentralization, and we consider this proposal necessary to achieve that.

Since we approved the EGG request including the 180k LDO transfer, we approve the transfer in this onchain voting and same for the Expanding the Simple DVT Module request.

We voted for this proposal, as it protects Lido DAO from a potential default judgment, which could have serious negative consequences, including potential web infrastructure takedowns, delisting of LDO from trading venues, and creating precedents that could be used in future legal actions against Lido DAO or similar entities.

See Expanding the Simple DVT Module and LIP-22: stETH on L2 — wstETH on Optimism bridge endpoints upgrade

This proposal outlines the major grant requests for the half-year period as follows: - 24.6m DAI + 180k LDO in grant continuity for the Lido Contributor’s Group - 7.1m DAI in grant continuity for the Liquidity Observation Lab - 400k DAI for the Community Lifeguard initiative These are essential initiatives for achieving the goals set by GOOSE and reGOOSE, and we support this proposal.

This is a proposal to establish a vault with additional incentives provided by Obol, SSV and the DVT modules of Lido. This initiative aims to encourage stakers to deposit into SDVT validators, thereby expanding the share of SDVT. We support this proposal as SDVT is one of the most critical efforts to enhance decentralization in Lido's staking and this proposal would surely promote this initiative faster.

This proposal suggests organizing CLI as a subcommittee of LEGO with a budget of approximately 200k USD per quarter. CLI aims to invigorate community activities and increase the number of contributors, such as community stakers, by managing community programs, creating content for community stakers, and identifying and supporting grant opportunities. This initiative is crucial for enhancing the decentralization of Lido and expanding a diverse base of contributors. We support this proposal.

Currently, wstETH is deployed on various L2 networks. In addition to this, this is a proposal to make stETH available on L2 as well. By utilizing existing bridges and wrapping wstETH on L2, stETH can be used on L2 networks. Ensuring that stETH maintains the same utility on L2 as it does on L1 is crucial for user experience, and we support this proposal.

This not only enhances the decentralization and security of Lido's Node Operators but also improves the economics for Node Operators participating in DVT. Therefore, we support this proposal.

As this proposal will lead to further strengthening of the robustness of the Lido protocol, we vote in favor of it.

As DeFi activities centered around LST expand beyond the Ethereum mainnet, partnerships like this, which address cross-chain compatibility, help meet the growing needs of LST-based DeFi activities. Therefore, we vote in favor of this proposal.

We believe that as a member of the Lido Alliance, Mellow can contribute to the growth of the Lido ecosystem by expanding the utility of stETH.

With the ReGOOSE update by hasu, we believe establishing the Lido Alliance would lead the direction toward a more decentralized and safer Ethereum ecosystem.

The proposal addresses key issues that are essential for Lido DAO’s future strategy.

Same as Renew GateSeal for the Withdrawal Queue and Validator Exit Bus Oracle

We vote FOR the proposal while we understand that having trust-minimized options for unexpected emergencies is crucial to keep the protocol safe and that Lido is still on the way to achieve making them into protocols

While we have several questions to be answered, we vote for the proposal since we agree with its general direction.

We understand this is an important step for the automation to achieve further decentralization

As it has been proven to be the best approach to prioritize the native bridges to avoid liquidity fragmentation, we consider this approach to deploy wstETH should be the right decision.

We highly appreciate efforts made for the investigation by the team, and we believe this is a part of the process of making secure system.

As delegation has been proven to work well in the other DAOs, this is a great step for a better governance of Lido.