Replace CMv2 Verifier with CuratedVerifier and update CircuitBreaker registration, as proposed on the forum | Audits & deployment verification: MixBytes | On-chain items 1.4-1.9.
Resources for the Proposal Validation
The resources listed in this section are considered trustworthy and reliable.
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.
Vote Items and Verification Details
How to verify: open the vote at dao.lido.fi/vote/207 and compare its calls with this guide. Each target links to its Lido Docs entry, and each method link opens the exact function on Etherscan.
1.Submit a Dual Governance proposal to enable CMv2 top-up allocation controls, consolidation migration and Curated Verifier for consolidated validators
Each of the nine calls asks Aragon Agent to execute one call through forward(bytes); the executed calls are the items below. Every submitted ETH value is zero. On dao.lido.fi, each executed call is shown one level deeper, under its Agent call.
[2] string metadata
Enable CMv2 top-up allocation controls, consolidation migration and Curated Verifier for consolidated validators
This is the exact metadata string in the vote bytes. This call submits the proposal; execution of its nine calls is a later step.
)
1.1.Upgrade CMv2 to the implementation with top-up allocation controls and call finalizeUpgradeV2()
0x88984a97 is exactly the four-byte call to finalizeUpgradeV2(), with no encoded arguments. Its selector is the first four bytes of the Ethereum Keccak-256 hash of finalizeUpgradeV2().
)
Role items (1.2-1.7): check the target, the 32-byte role and the account. Open the pre-filled Keccak link next to each role and compare its result with the role value.
1.2.Grant ENABLE_TOP_UP_ALLOCATION_ROLE to the Curated Module Committee on CMv2
CuratedVerifier receives this role under the proposal. The corresponding revoke is in item 1.5.
)
CircuitBreaker (1.8-1.9): in registerPauser, [1] is the contract that can be paused and [2] is its pauser. These items assign no pauser to the previous Verifier (item 1.8) and the Curated Module Committee to CuratedVerifier (item 1.9).
1.8.Unregister the previous Verifier from the protocol CircuitBreaker
CuratedVerifier is the contract to be paused, per the replacement proposal. On CuratedVerifier, pass the PAUSE_ROLE() result and the protocol CircuitBreaker address to hasRole. A true result confirms the CircuitBreaker holds PAUSE_ROLE.
2-7. Add six Lido Lend EVM script factories to Easy Track
Easy Track factories (2-7): compare each factory and its full permission string, then split the string into address and selector pairs as in the worked example below. If an explorer cannot show a tuple signature, use the verified ABI or Blockscout with the Keccak link.