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

test: upgrade cluster via voting #9638

Closed
Tracked by #7935
just-mitch opened this issue Oct 31, 2024 · 0 comments · Fixed by #12127
Closed
Tracked by #7935

test: upgrade cluster via voting #9638

just-mitch opened this issue Oct 31, 2024 · 0 comments · Fixed by #12127
Assignees

Comments

@just-mitch
Copy link
Collaborator

just-mitch commented Oct 31, 2024

Should be confident that the following flow works:

  • deploy l1 contracts
  • start a node against the canonical version
  • mine some blocks and see rewards paid out
  • deploy a new version
  • see that the node can continue to mine blocks, but not get rewards
  • start a new node, against the canonical version, and have it be on the new version (getting rewards)
@just-mitch just-mitch added this to the Sequencer & Prover Testnet milestone Oct 31, 2024
@just-mitch just-mitch self-assigned this Nov 1, 2024
@LHerskind LHerskind added this to A3 Nov 5, 2024
@github-project-automation github-project-automation bot moved this to Todo in A3 Nov 5, 2024
@just-mitch just-mitch changed the title feat: governance proposal cluster test test: governance proposal cluster Nov 7, 2024
@just-mitch just-mitch changed the title test: governance proposal cluster test: upgrade cluster via voting Nov 7, 2024
@just-mitch just-mitch removed this from the Sequencer & Prover Testnet milestone Nov 7, 2024
@just-mitch just-mitch linked a pull request Jan 8, 2025 that will close this issue
Maddiaa0 pushed a commit that referenced this issue Jan 30, 2025
See [the
design](AztecProtocol/engineering-designs#47).

TLDR:
- make a forwarder contract that dispatches to the various things a
sequencer does (publish a block, vote, claim a quote, etc)
- refactor the L1 publisher into a classes dedicated for the prover
node, and for the sequencer.

Future work:
- #9638
- #11513
@just-mitch just-mitch linked a pull request Feb 20, 2025 that will close this issue
@github-project-automation github-project-automation bot moved this from Todo to Done in A3 Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant