Lots of Snapshot votes today:
# Lido DAO Ops Multisigs Policy 2.0
I voted for albeit I have commented on the post that the policy does likely need to be upgraded relatively soon in light of the Bybit hack. I agree with @Leuts sentiments too. Let us call this a cautious FOR.
This looks like an excellent initiative. I admit I had not paid much attention to this before but note strong support among various workstreams and also the long timeframe spent on it. I note this is a first temp check style vote before the technical one. FOR.
# MEV-Boost Relay Allowed List management via Easy Track
Streamlining and improving governance, what more could one ask for. FOR.
# Ensuring Compatibility with Ethereum’s Pectra Upgrade
Seems well thought out. Only include the necessary requirements now, implement the rest later and have a fallback in place. All eminently sensible. Will keep an eye on this area after watching the recent ACD call where Lido turned up. FOR.
# [EGG] Lido Labs BORG Foundation Grant Funding Request (Apr-Dec 2025)
# [EGG] Lido Ecosystem BORG Foundation Grant Funding Request (Apr-Dec 2025)
FOR both. This approves the budget of the already accepted BORG model. I tend to agree with Pol Lanski that we could use a better breakdown of the spending.
Finally, on-chain vote 184:
I voted FOR for 1 and am generally of the spirit that the voting duration previously was a little tight. This often meant that one effectively has to respond to what can be quite complicated votes much faster than one would sometimes wish. In my own case time is quite flexible, as an academic, but I can imagine for many it creates issues. I do not see any issues in items 1-17 that implement these changes that would concern me.
I voted FOR 2 and here we are looking at raising the security limit wrt streamlining the new BORGs and here I am in agreement it is needed and lines 18-19 do what they say.