What the vote is about

This document outlines methods to verify all the calls embedded in the Lido DAO on-chain vote #192, which contains the following proposals:

1. Upgrade to CSM v2 and increase CSM stake share limit from 3% to 5%, as per Snapshot decision. Items 1.34-1.59. Audit & deployment verification by: Statemind | Ackee.
2. Activate Triggerable Withdrawals, as per Snapshot decision. Items 1.1-1.33, 1.60-1.66, 2-4. Audit & deployment verification by Statemind | Audit by Ackee.
3. Update the reward address and name for Node Operator ID 25 Nethermind, as per Snapshot decision. Items 1.67, 1.68.
4. Rotate Deposit Security Committee address for Kiln. Requested on the forum. Items 1.69, 1.70.

Vote items verification guide

🔎 Resources for the Proposal Validation

The resources listed in this section are considered trustworthy and reliable.

• Lido Docs - use this to verify contract addresses
• Blockchain Explorer Etherscan (or alternatives such as Blockscout) - use this to review contract functionality, check the current state of contracts, and inspect contract functions
• Lido Research Forum - use this to access original proposals, review details of proposed changes, and validate modification parameters
• Snapshot - use this to review finalized and pre-approved DAO versions of proposals

Direct links to relevant sources will be provided for each item in the vote, ensuring easy access to the associated information.

Verification Process for the role-based items

1. Verify the target contract address: confirm that the contract address used in the method call matches the one listed in the Lido Docs.
2. Verify the called method exists on the contract: check that the contract includes the method invoked in the item; you can do this by visiting the contract’s page on Etherscan → Contract tab → Read Contract or Read as Proxy.
3. Verify all contract addresses passed as parameters: ensure that all contract addresses passed as parameters in the item are listed and described in the Lido Docs.
4. Verify role identifiers passed as parameters, for any role identifiers included as parameters: go to the relevant page of the contract (to which the role is assigned) on Etherscan → Contract → Read Contract or Read as Proxy and locate the role identifier. Alternatively, you can compute the role identifier using an external Keccak256 hash calculator (i.e., https://emn178.github.io/online-tools/keccak_256.html).