Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

integrate EC membership changes into upgrade handler #10258

Closed
dckc opened this issue Oct 11, 2024 · 0 comments · Fixed by #10241
Closed

integrate EC membership changes into upgrade handler #10258

dckc opened this issue Oct 11, 2024 · 0 comments · Fixed by #10241
Assignees
Labels
enhancement New feature or request Governance Governance

Comments

@dckc
Copy link
Member

dckc commented Oct 11, 2024

What is the Problem Being Solved?

Following a signalling proposal, replace-electorate-core.js is expected to execute as part of an upcoming chain-halting upgrade. So it should be included in upgrade.go

(originally discussed in #10251 (comment) )

Description of the Design

Somewhat like dd97f18 but in reverse.

Security / Documentation / Upgrade Considerations

It's critical that the updated list of addresses are actually controlled by the Economic Committee membership and noone else.

The Economic Committee is elected by the BLD stakers; a signalling proposal should provide documentation to BLD stakers that the chain-halting upgrade proposal is also a proposal to elect an updated slate of committee members.

Scaling Considerations

Test Plan

a3p testing such as in #10241 should use a SoftwareUpgradeProposal, not a CoreEvalProposal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Governance Governance
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants