Add builder config to client support table - #90
Merged
Conversation
nflaig
commented
Aug 19, 2026
nflaig
changed the title
james-prysm
reviewed
Aug 20, 2026
james-prysm
previously approved these changes
Aug 20, 2026
james-prysm
approved these changes
Aug 20, 2026
rolfyone
approved these changes
Aug 20, 2026
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
3 participants
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.
I've split it into 2 tables now, one for key management, and another for validator configuration as otherwise it becomes too crowded
worth pointing out that these tables don't seem very well maintained, I am pretty sure that graffiti apis are supported by most clients at this point, but per the table, it's only Lodestar and VeroI filled out the tables for all clients now