Address: PGov.eth / 0x3FB19771947072629C8EEE7995a2eF23B72d4C8A
Contact Information: @PGovTeam on Twitter
Introduction:
Hello Everyone! We are a team of dedicated governance enthusiasts who have been in the crypto governance space for over three years. Our team were some of the first members involved in defi governance and we want to apply what we have learned over here to Lido. We believe this community has some of the strongest and most intelligent community members and we’re grateful to be along for the journey!
Core Values:
Growth: Our decisions are primarily focused on the growth of the protocol. This often results in how to spend money efficiently, but even more importantly and objecting for unreasonable spends and knowing when to vote no.
Transparency: Clear communication with votes and explanations of reasoning, and an equivalent demand for proposals to do the same. Too often we see thousands, if not millions, being rolled up together and glossed over during proposals.
Accountability: Too often once a decision is done, having proper accountability becomes an afterthought. Whether it’s a DAO promise or a grant or a new program, once a DAO votes something in, we forget about it. Our goal with PGov is to both continue to check in on these decisions as well as ensure that there are proper channels set up to ensure accountability.
Public Acceptance: We are committed to the code of conduct, mission, and respective values Disclosures: We are delegates across other Defi protocols. Team members hold a combined ~$50k work of LDO.
Welcome to the platform. Just a heads-up—the application deadline for participation in the rally was August 25th (details here), so your profiles won’t be included in the UI presented list of delegates or other rally materials. However, this doesn’t prevent you from participating in the Delegate Incentivisation Program if you meet the criteria, and it certainly doesn’t block you from being a public delegate on the platform!
We voted Increase threshold to 15,000 LDO: This threshold makes sense as the DAO grows. Increasing the threshold to this should prevent possible spam in the future.
We voted In Favor for both: Solstice Staking AG’s acquisition of Bridgetower and Attestant’s acquisition by Bitwise does not introduce any operational changes, as the same team will continue managing the validators on the same infrastructure in the same geographic area. Supporting this proposal allows for continuity and stability and maintains trusted operator performance.
We voted In Favor for both: We think supporting the establishment of the Lido Labs BORG Foundation and the Lido Ecosystem BORG Foundation strengthens Lido DAO’s governance by creating a structured, transparent, and accountable entity dedicated to research, development, and operational oversight. This framework ensures better compliance, contributor protection, and alignment with Lido DAO’s long-term goals while maintaining decentralized administration.
We voted In Favor: This allows for a smooth transition by replacing Tim Beiko with Eric Siu, whose expertise in Ethereum ecosystem coordination aligns well with LEGO’s objectives. Additionally, granting the council the ability to manage future member rotations without requiring a Snapshot vote streamlines governance, reducing administrative overhead; which we are also in support of.
We voted Adopt Multisig Policy: Updated and revised policy for wallet operations to reflect current best practices makes sense, including ability to incorporate additional recommendations to the team to further enhance security.
We voted Approve: We support this initiative, as the module significantly enhances Lido’s infrastructure by introducing a permissionless pathway for Node Operators, reducing barriers to entry through fractional bonding and simplified operations. The proposed implementation timeline is conservative, featuring a testnet deployment in Q2 2025 and a comprehensive review process prior to mainnet integration.
We voted For: This proposal introduces three specialized EVM script factories designed to streamline the existing cumbersome process of updating the relay list. By entrusting management responsibilities to the EVM Script Executor, the proposal increases transparency and promotes greater participation from LDO tokenholders in relay governance.
We voted For & For: After reviewing the funding proposal along with extensive forum responses and discussions, we support both of these grant requests through December 2025. This comprehensive funding package directly advances multiple GOOSE-2 objectives, particularly in protocol development, governance improvement, and Ethereum decentralization and both are reasonable budgets.
We voted Yes: This proposal enhances governance accessibility by extending the main voting phase to 72 hours and the objection phase to 48 hours, providing participants with additional time to engage in governance decisions. The revised GateSeal protection, now extended from 6 to 11 days, has undergone thorough auditing. Additionally, the introduction of new Easy Track Factories for Lido Ecosystem and Lido Labs streamlines funding processes with sensible quarterly limits ($5M and $18M respectively), reducing administrative overhead while maintaining oversight.
We voted Against: We are currently opposed to re-endorsing wstETH on Starknet due to concerns over the Starknet Foundation’s delayed disclosure and handling of a prior incident, which resulted in the wstETH token on Starknet becoming irreversibly ownerless and non-upgradeable. This misalignment with Lido’s bridging guidelines led to the initial offboarding of wstETH from Starknet. Despite the completion of a migration to a new wstETH token and a proposal for re-endorsement, we agree with the Network Expansion Committee (NEC)'s decision to not proceed at this time, citing the need for better alignment in security culture and incident response practices.
We voted For: We support the proposal to increase the ET limits for the LOL multisig as it more efficiently streamlines operational capabilities. The current ET limit of 2,100 stETH per quarter restricts the Foundation’s ability to access the full $8.5 million grant allocated for the second half of 2025. Adjusting the ET limits enhances also the security framework by providing a comfortable buffer above anticipated expenditures, as emphasized by the DAO Ops team.
We voted For: We support the proposal to reduce the keyRemovalCharge parameter in the CSM from 0.05 ETH to 0.02 ETH, as it reflects current Ethereum network conditions and maintains the module’s safety mechanisms. This adjustment prevents unnecessary financial burdens on NOs and promotes efficient participation in the CSM. Furthermore, this change can be regularly updated and we think it makes sense to decrease it to this for the time being.
We voted For: We support the proposal to onboard Twyne into the Lido Alliance due to its innovative approach to enhancing stETH utility within the DeFi ecosystem. Twyne’s credit delegation protocol allows stETH holders to delegate their unused borrowing capacity, unlocking additional yield opportunities and enabling more flexible lending strategies. By integrating with existing lending markets like Euler, Twyne offers a modular solution that preserves capital efficiency while introducing new avenues for stETH utilization. A valid concern we considerd is that Twyne is still quite early in the development stage. As the protocol is not yet live, there is limited data on its performance, user adoption, and security robustness. A note going forward, is that it is crucial for the DAO to monitor Twyne’s progress closely and ensure that all security measures are thoroughly implemented.
We voted For: We support this proposal as it has shown to increase active participation and improve the quality of discussions and feedback. The pilot program successfully brought new actors into governance, with over 24 million LDO delegated to public delegates. The continuation and refinement of this program are essential for sustaining robust and resilient governance within the Lido ecosystem, and we are especially grateful, as we started participating around this time!
We voted Yes: Rotating the single compromised key immediately while the rest of the 5/9 quorum stays intact preserves continuity of reporting and keeps stakers fully protected. No reason to not do so if there are issues possibly detected.