Upcoming Vote: Connecting the CMv2 ConsolidationMigrator to the ConsolidationBus
The upcoming vote will connect the new ConsolidationMigrator instance for consolidations within CMv2, described above, to the ConsolidationBus. It will include the following item:
- Grant
PUBLISH_ROLEon theConsolidationBusat0xd907CE33B4Be423823d1CFFe80BD147E8b8554C8to the newConsolidationMigratorat0xc8a7F4917cA03FDCD24a5E11A48Ab448318976e7.
Until this role is granted, the new migrator can’t submit consolidation requests to the bus.
The new instance runs the same ConsolidationMigrator code that was deployed with the Staking Router v3 upgrade. Both SOURCE_MODULE_ID and TARGET_MODULE_ID point to CMv2 (module id 4), so consolidations submitted through it can’t move stake outside the module. The Curated Module Committee (CMC) holds ALLOW_PAIR_ROLE and DISALLOW_PAIR_ROLE, and the Lido Aragon Agent holds DEFAULT_ADMIN_ROLE.
Certora and Statemind audited the ConsolidationMigrator code at commit af095e4 as part of the Staking Router v3 audits. MixBytes has verified the mainnet deployment. The deployed bytecode matches the audited code, and the configuration and role setup are correct.
The deployed contracts are:
ConsolidationMigratorproxy at0xc8a7F4917cA03FDCD24a5E11A48Ab448318976e7ConsolidationMigratorimplementation at0x5d2DDD6817180C2135b4652503bD555C2d3Bb392
The audit and deployment verification reports are available here: