Future of the Curated Module | CMv2 Landscape

As a complimentary change to the ConsolidationMigrator.sol described above, Lido contributors propose a new version of the Verifier.sol specifically tailored for the Curated Module v2.

The new CuratedVerifier.sol supports reporting of the validator withdrawals for the validators that were consolidated and as the result do not have a Withdrawal event as validators which were exited in a regular way. This is achieved by verifying that validator.withdrawableEpoch < currentEpoch without checking the exact withdrawal event that does not exist for the consolidated validators. As the result of this change the mechanism of automated bond penalization due to withdrawal balance deficit was removed in favour of general delayed penalty that can be reported by CMC and confirmed by the DAO in case of validators underperformance.

Implementation of this change requires the following items to be added to the upcoming on-chain vote:

  • Revoke CuratedModuleV2 VERIFIER_ROLE from the current instance of Verifier.sol
  • Revoke CuratedModuleV2 REPORT_REGULAR_WITHDRAWN_VALIDATORS_ROLE from the current instance of Verifier.sol
  • Grant CuratedModuleV2 VERIFIER_ROLE to the new instance of CuratedVerifier.sol (the exact address will be added after deployment)
  • Grant CuratedModuleV2 REPORT_REGULAR_WITHDRAWN_VALIDATORS_ROLE to the new instance of CuratedVerifier.sol (the exact address will be added after deployment)
  • Unregister CircuitBreaker pauser for the current instance of Verifier.sol
  • Register CircuitBreaker pauser for the new instance of CuratedVerifier.sol (the exact address will be added after deployment)

The address, deployment verification, and audit report for the new CuratedVerifier.sol will be provided before the start of the on-chain vote.

4 Likes