Add per-validator builder configuration API - #9862
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds the per-validator builder configuration endpoints from ethereum/keymanager-APIs#88.
GET /eth/v1/validator/{pubkey}/builder_configreturns the configuration in use for the validator.POST /eth/v1/validator/{pubkey}/builder_configreplaces and persists the full configuration on a per-validator basis. This is the method and replacement behavior defined by [WIP] Tree hash #88; it does not merge with the previous entry.DELETE /eth/v1/validator/{pubkey}/builder_configremoves the stored entry, so the validator inherits the global configuration again.The API stores per-validator entries under
validator_configsinbuilder_definitions.yml.POST {}is useful afterbuilders: []: it restores global inheritance but keeps an empty per-validator entry.DELETErestores the same runtime behavior and removes the entry.Changes made by
POSTandDELETEapply to subsequent builder preference publication and Gloas block production without a restart.Closes #9796
Additional Info
This PR is stacked on #9807 and should be reviewed after it.