Vote 180. I voted yes. This is a long-ish post, so apologies if there are some minor errors. I’ll clean it up later.
This is a complicated vote to get through albeit one I was able to prepare in advance for. The big picture is clear and easy to back:
Release the Community Staking Module (CSM) for permissionless staking and upgrade the Staking Router to ensure compatibility with CSM and future modules, improving system efficiency.
Therefore the vote here is really about implementation and audits. I based my decision primarily on this post by @Maksim_Kuraian The vote as I see it is about three Snapshot-approved LIPs (23, 25, 26), so we can therefore assume support among the Lido DAO.
There’s three objectives:
- Upgrade the Staking Router and related contracts.
- Upgrade the Accounting Oracle sanity checker.
- Add the Community Staking Module (CSM).
The LIPs capture the design. Notably these have been successfully tested on Holesky testnet.
Staking Router and related contracts upgrade following the DAO-approved LIP-25: Staking Router 2.0.
Here I noted that for LIP-25 there was not much discussion to the forum post (which I take as a positive indication of non-controversy). I particular admire the Deposit Security Module (DSM) change to minimise governance approval. And overall commend the efforts of the team to focus so closely on permissionless staking and security.
Post-Snapshot there are audits from Ackee and MixBytes. Notably there are no critical or high issues found and I note medium and below are either fixed or acknowledged.
LIP-23: Negative rebase sanity check with a pluggable second opinion following the DAO-approved Snapshot vote.
In a similar vein I also there is not a huge amount of discussion about this on the forum. But the rationale is quite clear, the current sanity check is not quite adequate, we need to improve it and here is the solution. I can see the reason why it is included in this specific vote here where it is stated that ‘the Sanity Checker contract needs to be updated in conjunction with the Staking Router update.’ The audits found mostly minor issues.
Add Community Staking Module
This is an easy one to back because I believe it is key to Lido’s Purpose to ‘Keep Ethereum decentralized, accessible to all, and resistant to censorship.’ I believe existentially this is a vision much closer to what Lido DAO members want for themselves. But also in terms of positive externalities it sends a clear message to the wider Ethereum community about what Lido’s intents are.
I reviewed the audits, but this is of course an extremely well-documented, long-thought through effort with many eyes on it and that shows. This is an incredible achievement!
I note this small update from MixBytes about the contractor code.
Rotate the Instadapp Oracle address
I see this as an administrative necessity. It responds to a request from Instadapp on the forums. This does seem to be a slightly late addition. I don’t think that is some major issue, but maybe worth flagging.
For the future I have noted I need to allocate more time to the voting script and will adjust accordingly.