What the vote is about

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

1. Extend Dual Governance Emergency Protection until June 20, 2027, as proposed on the forum. Item 1.1.
2. Grant MANAGE_SIGNING_KEYS role to Node Operator Consensys, as requested on the forum. Item 1.2.
3. Increase Alliance Ops stablecoins Easy Track factory limit from $250K per 3 months to $5M per 6 months, as per Snapshot decision. Item 1.3.
4. Reduce VEBO Reporting Frame from 75 to 45 epochs, as proposed on the forum. Items 1.4–1.7.

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 extend Dual Governance Emergency Protection until June 20 2027, grant MANAGE_SIGNING_KEYS role to Node Operator Consensys, increase limit from $250K per 3 months to $5M per 6 months on Alliance Ops stablecoins Easy Track factory, reduce VEBO Reporting Frame from 75 to 45 epochs

Call data

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

function **submitProposal**(
  tuple[] calls,
  string metadata
)

Call data:
[1] See 7 parsed calls at 1.1 — 1.7
[2] Extend Dual Governance Emergency Protection until June 20 2027, grant MANAGE_SIGNING_KEYS role to Node Operator Consensys, increase limit from $250K per 3 months to $5M per 6 months on Alliance Ops stablecoins Easy Track factory, reduce VEBO Reporting Frame from 75 to 45 epochs

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

<aside> ℹ️

Some 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>

1.1. Call setEmergencyProtectionEndDate(1813449600) on Emergency Protected Timelock 0xCE0425301C85c5Ea2A0873A2dEe44d78E02D2316