What the vote is about

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

1. Enable CircuitBreaker on-chain: reassign the pause role from legacy GateSeals to CircuitBreaker and assign the respective pauser committee to the 11 pausable contracts in CircuitBreaker, as per Snapshot decision. Audit & deployment verification: Cyfrin, MixBytes | Formal verification: Cyfrin.
   1. Pauser CircuitBreaker Committee: WithdrawalQueue, ValidatorsExitBusOracle, TriggerableWithdrawalsGateway, VaultHub, PredepositGuarantee. Items 1.1 - 1.15.
   2. Pauser CSM Committee: CSModule, CSAccounting, CSFeeOracle, CSVerifierV2, CSVettedGate, CSEjector. Items 1.16 - 1.33.
2. Increase LOL stETH Easy Track factory limit from 6K stETH per 6 months to 8K stETH per 6 months, as per Snapshot decision. Item 1.34.
3. Rename Node Operator Pier Two to MAVAN, as requested on the forum. Item 1.35.
4. Deactivate Node Operator Chorus One, as proposed on the forum. Item 1.36.

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/inspect methods, and check the current state of contracts
• Lido Research Forum - use this to access original proposals, review details of proposed changes, and validate modification parameters
• Snapshot - use this to review pre-approvals for on-chain proposals

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

Proofs

1. Submit a Dual Governance proposal to enable CircuitBreaker on-chain, increase LOL stETH Easy Track factory limit from 6K stETH to 8K stETH per 6 months, rename Node Operator Pier Two to MAVAN, deactivate Node Operator Chorus One

<aside> ℹ️

On-chain actions included in the Dual Governance proposal are executed through an AragonAgent.forward call:

**1.X. On [AragonAgent]**
0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c

function forward(
  bytes _evmScript
)

Call data:
[1] See parsed evm script at 1.X.1
  **1.X.1. On [<CONTRACT_NAME>]**
  <CONTRACT_ADDRESS>
  
  function <FUNCTION_NAME>(
    <FUNCTION_ARGUMENTS>
  )
  
  Call data:
  <ARGUMENT VALUES LIST>

For brevity, the AragonAgent.forward wrapper is omitted from each on-chain action in this instruction.

</aside>

All addresses specified in the table below can be verified in Lido Docs.