-
Notifications
You must be signed in to change notification settings - Fork 78
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
Pre-generate validator registrations #2172
Labels
protocol
Protocol Team tickets
Comments
obol-bulldozer bot
pushed a commit
that referenced
this issue
May 16, 2023
This functionality lives behind the `pregen_validator_registrations` feature flag. This PR is only concerned with the DKG pre-generation section of the design document (https://docs.google.com/document/d/1lCYiEv7JmVYymp4CBrEvExj3WNmSqWVvZwl9dwATCmA/edit#). A follow-up PR will implement the lock file changes and wire it accordingly. category: feature ticket: #2172 feature_flag: pregen_registrations
obol-bulldozer bot
pushed a commit
that referenced
this issue
May 18, 2023
Adds pre-generate validator builder registrations to lock file v1.7.0. category: feature ticket: #2172
obol-bulldozer bot
pushed a commit
that referenced
this issue
May 19, 2023
Generate validator builder registrations when running `charon create cluster` manually. category: feature ticket: #2172
obol-bulldozer bot
pushed a commit
that referenced
this issue
May 22, 2023
This commit includes changes to support validator builder registrations by reading them from the legacy lock file. category: feature ticket: #2172
obol-bulldozer bot
pushed a commit
that referenced
this issue
May 24, 2023
Adds support to broadcast pre-generate validator registrations through recaster component. category: feature ticket: #2172
we need a panel to check the outcome once shipped. @OisinKyne FYI |
obol-bulldozer bot
pushed a commit
that referenced
this issue
May 29, 2023
Refactor validator mock builder-api registrations to align with new pre-generated registrations. category: refactor ticket: #2172
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🎯 Problem to be solved
The current builder-api validator registration endpoint isn't compatible with DV middleware, see #1643 and this design doc.
Changing the spec and getting all VC implementations to implement it is the proper long term solution.
This is short term workaround is to pre-generate validator registration messages during the DKG, to store them in the lock file, and to broadcast them once an epoch when
--builder-api=true
.🛠️ Proposed solution
See design doc.
🧪 Tests
The text was updated successfully, but these errors were encountered: