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.
Summary:
While this is an omnibus vote that includes 10 motions, there are 3 key topics.
- Oracle member rotation
A change in Lido’s Ethereum Oracle set is proposed, with MatrixedLink seeking to replace the departing Rated Labs. This transition would maintain the existing composition of the oracle set while introducing a new participant familiar with Lido’s infrastructure.
- Node Operator name & reward address update
This is the administrative change, required after Galaxy acquired CryptoManufaktur, one of Lido’s node operator. This change contains the update of on-chain name (From CryptoManufaktur to Galaxy) and the update of the reward address.
- On-Chain Delegation
This proposal aims to approve the implementation of On-Chain Delegation.
This will allow LDO holders to delegate their voting power to designate addresses as their delegates, while maintaining ownership of LDO token itself.
Here’s the details