# Future of the Curated Module | CMv2 Landscape

**URL:** <https://research.lido.fi/t/future-of-the-curated-module-cmv2-landscape/10929>\
**Category:** Proposals\
**Created:** [November 26, 2025, 4:00pm UTC](https://research.lido.fi/t/future-of-the-curated-module-cmv2-landscape/10929 "2025-11-26T16:00:32Z")\
**Posts on this page:** 1\
**Showing post:** 53

<div class="post-metadata">

**Author:** ![Maksim\_Kuraian](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/maksim_kuraian/32/3204_2.png) [@Maksim\_Kuraian](https://research.lido.fi/u/Maksim_Kuraian)\
**Post date:** [November 16, 2026, 4:25pm UTC](https://research.lido.fi/t/future-of-the-curated-module-cmv2-landscape/10929/53 "2026-11-16T16:25:44Z")

</div>

### 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_ROLE` on the `ConsolidationBus` at `0xd907CE33B4Be423823d1CFFe80BD147E8b8554C8` to the new `ConsolidationMigrator` at `0xc8a7F4917cA03FDCD24a5E11A48Ab448318976e7`.

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`](https://github.com/lidofinance/core/blob/af095e48bbc1c3841c2c9936219c8461af01056b/contracts/0.8.25/consolidation/ConsolidationMigrator.sol) code at commit [`af095e4`](https://github.com/lidofinance/core/commit/af095e48bbc1c3841c2c9936219c8461af01056b) 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:

- `ConsolidationMigrator` proxy at [`0xc8a7F4917cA03FDCD24a5E11A48Ab448318976e7`](https://etherscan.io/address/0xc8a7F4917cA03FDCD24a5E11A48Ab448318976e7)
- `ConsolidationMigrator` implementation at [`0x5d2DDD6817180C2135b4652503bD555C2d3Bb392`](https://etherscan.io/address/0x5d2DDD6817180C2135b4652503bD555C2d3Bb392)

The audit and deployment verification reports are available here:

- [MixBytes `ConsolidationMigrator` deployment verification](https://github.com/lidofinance/audits/raw/main/MixBytes%20Lido%20CMv2%20ConsolidationMigrator%20Deployment%20Verification%20Report%2011-2026.pdf)
- [Certora Staking Router v3 audit](https://github.com/lidofinance/audits/raw/main/Certora%20Staking%20Router%20v3%20Audit%20Report%2007-2026.pdf)
- [Statemind Staking Router v3 audit](https://github.com/lidofinance/audits/raw/main/Statemind%20Staking%20Router%20v3%20Audit%20Report%2007-2026.pdf)

---

_[View the full topic](https://research.lido.fi/t/future-of-the-curated-module-cmv2-landscape/10929)._
