Skip to content

feat: add mainnet CSM 0x02 deployment vote - #689

Open
TheDZhon wants to merge 4 commits into
feat/next-votefrom
feat/mainnet-csm0x02-deployment-vote
Open

TheDZhon wants to merge 4 commits into
feat/next-votefrom
feat/mainnet-csm0x02-deployment-vote

Conversation

@TheDZhon

Copy link
Copy Markdown
Contributor

Opening a PR for a review purpose 👀

Comment thread scripts/vote_csm0x02.py Outdated
Comment thread scripts/vote_csm0x02.py Outdated
Comment thread scripts/vote_csm0x02.py
Comment thread scripts/vote_csm0x02.py
@skhomuti
skhomuti force-pushed the feat/mainnet-csm0x02-deployment-vote branch from f234f88 to 077b6d0 Compare October 5, 2026 07:56
@skhomuti
skhomuti marked this pull request as ready for review October 5, 2026 07:57
@skhomuti
skhomuti requested a review from a team as a code owner October 5, 2026 07:57
@skhomuti
skhomuti changed the base branch from master to feat/next-vote October 5, 2026 07:58
Set the initial oracle epoch and extend vote, Easy Track, Circuit Breaker and permissions coverage. Pin staking-modules CI to the CSM 0x02 regression action branch until activation.
Comment thread scripts/vote_csm0x02.py
# https://research.lido.fi/t/future-of-the-curated-module-cmv2-landscape/10929/45
# Keep the other current mainnet CMv1 router parameters unchanged.
CURATED_V1_TARGET_SHARE_BP = 0
CURATED_V1_PRIORITY_EXIT_SHARE_THRESHOLD_BP = 10_000

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel we can also set it to ZERO to ensure exists are served from CMv1 only until it is empty

Comment thread scripts/vote_csm0x02.py
# First report window opens on 2026-12-07 at 13:36:23 UTC (Monday).
# Its full 6,300-epoch (28-day) observation period starts on 2026-11-09 at 13:36:23 UTC,
# after the expected 2026-10-24 DG enactment for a vote launched on 2026-10-15.
# This places reports midway between CSM 0x01 windows and about a week from CMv2 windows.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# This places reports midway between CSM 0x01 windows and about a week from CMv2 windows.
# This places reports midway between CSM 0x01 windows and about a week from CMv2 windows.
# So the resulting report schedule for staking modules is:
# Week | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
# -------+----------+----------+----------+----------+----------+----------+----------+
# Module | 0x01 CSM | CMv2 | 0x02 CSM | CMv2 | 0x01 CSM | CMv2 | 0x02 CSM |

Comment thread scripts/vote_csm0x02.py
DG_PROPOSAL_METADATA = (
"Activate CSM 0x02, set CMv1 stake share limit to 0, and set Consensys target limits to 0 in CMv1 and CMv2"
)
DG_SUBMISSION_DESCRIPTION = "1. Submit a Dual Governance proposal to activate CSM 0x02 and update curated module limits"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
DG_SUBMISSION_DESCRIPTION = "1. Submit a Dual Governance proposal to activate CSM 0x02 and update curated module limits"
DG_SUBMISSION_DESCRIPTION = "1. Submit a Dual Governance proposal to activate CSM 0x02, update curated module limits, and set target limits for Consensys Node Operatora"

Comment thread scripts/vote_csm0x02.py
"""
Mainnet vote to activate the CSM deployment for 0x02 withdrawal credentials.

1. Submit a Dual Governance proposal to activate CSM 0x02 and update curated module limits

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it planned to add a TimeConstraints check to this vote? It seems to be required: the AO report must match the number of registered staking modules (https://github.com/lidofinance/core/blob/26f1bdd0c449b3e24205c197bed91662414f8004/contracts/0.8.25/sr/SRLib.sol#L858-L862), so if the DG proposal is executed between the AO ref slot and the report submission, addStakingModule makes that day's report revert.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants