What the vote is about

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

1. Activate Lido V3: Phase 2 (Full Launch), as proposed on the Forum. Updated audits: Consensys Diligence, Certora, MixBytes. BLS Library audit: Sigma Prime.
   1. Revoke OperatorsGrid & VaultHub configuration roles from Lido V3 Phase 1 VaultsAdapter contract and grant them to Phase 2 VaultsAdapter contract. Items 1.1-1.6.
   2. Enable Predeposit Guarantee guided deposit flows as a part of Full Launch. 1.7-1.10.
   3. Raise the maximum allowed stETH external shares ratio to 30%. Items 1.11-1.13.
   4. Remove Lido V3 Phase 1 Easy Track factories and add Phase 2 factories enabling stVault Committee to configure VaultHub and OperatorGrid contracts. Items 2-15.
2. Raise Community Staking Module stake share limit to 7.5% and priority exit threshold to 9%, as proposed on the Forum. Item 1.14.
3. Grant MANAGE_FRAME_CONFIG_ROLE on CS HashConsensus to TwoPhaseFrameConfigUpdate contract, as proposed on the Forum. Audit & deployment verification: MixBytes. Item 1.15.

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
  • Lido V3 — Deployment update and upcoming voting details
• 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.

How to Verify Permission Hashes

Proofs

1. Submit a Dual Governance proposal to activate Lido V3 Phase 2, raise CSM stake share limit to 7.5% and priority exit threshold to 9%, grant MANAGE_FRAME_CONFIG_ROLE on CS HashConsensus to TwoPhaseFrameConfigUpdate contract

Call data

**1. On [DualGovernance]**
0xc1db28b3301331277e307fdcff8de28242a4486e

function submitProposal(
	tuple[] calls,
	string metadata
)

Call data:
[1] See 15 parsed calls at 1.1 — 1.15
[2] Activate Lido V3 Phase 2, raise CSM stake share limit to 7.5% and priority exit threshold to 9%, grant MANAGE_FRAME_CONFIG_ROLE on CS HashConsensus to TwoPhaseFrameConfigUpdate contract

Verification points

the **current** **Dual Governance** contract address [0xc1db28b3301331277e307fdcff8de28242a4486e](<https://etherscan.io/address/0xc1db28b3301331277e307fdcff8de28242a4486e>) is published in [Lido Docs](<https://docs.lido.fi/deployed-contracts/#dual-governance>)

the [**submitProposal**](<https://etherscan.io/address/0xc1db28b3301331277e307fdcff8de28242a4486e#writeContract#F15>) function of the [**DualGovernance**](<https://etherscan.io/address/0xc1db28b3301331277e307fdcff8de28242a4486e>) contract is invoked to submit a Dual Governance motion.

[1] encoded voting script submitted through Dual Governance (parsed method calls provided below) [2] description of the on-chain actions submitted through the Dual Governance

1.1. Revoke vaults.OperatorsGrid.Registry role a495a3428837724c7f7648cda02eb83c9c4c778c8688d6f254c7f3f80c154d55 on OperatorGrid 0xC69685E89Cefc327b43B7234AC646451B27c544d from old VaultsAdapter 0xe2DE6d2DefF15588a71849c0429101F8ca9FB14D

Call data

**1.1. On [OperatorGrid]**
0xc69685e89cefc327b43b7234ac646451b27c544d

function revokeRole(
	bytes32 role,
	address account
)

Call data:
[1] [ENCODED ROLE] 0xa495a3428837724c7f7648cda02eb83c9c4c778c8688d6f254c7f3f80c154d55
[2] 0xe2DE6d2DefF15588a71849c0429101F8ca9FB14D

Verification points

the **OperatorGrid** contract address [0xC69685E89Cefc327b43B7234AC646451B27c544d](<https://etherscan.io/address/0xC69685E89Cefc327b43B7234AC646451B27c544d>) is published in [Lido Docs](<https://docs.lido.fi/deployed-contracts/#core-protocol>)

the [**revokeRole**](<https://etherscan.io/address/0xC69685E89Cefc327b43B7234AC646451B27c544d#writeProxyContract#F11>) function of the [**OperatorGrid**](<https://etherscan.io/address/0xC69685E89Cefc327b43B7234AC646451B27c544d>) contract is invoked to revoke the specified role from a particular account.

[1] vaults.OperatorsGrid.Registry keccak-256 hash value 0xa495a3428837724c7f7648cda02eb83c9c4c778c8688d6f254c7f3f80c154d55 can be verified online using one of the available online tools, for example this one

[2] Lido V3 Phase 1 VaultsAdapter address 0xe2DE6d2DefF15588a71849c0429101F8ca9FB14D can be verified in Lido Docs