-
Notifications
You must be signed in to change notification settings - Fork 784
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
Implement graffiti management API #4951
Implement graffiti management API #4951
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this! I've added a few comments / questions, but looks great overall 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're very close! Just a small comment on making the functions non-async.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, looks good to me! Thanks :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM as well
Issue Addressed
#4947
Proposed Changes
add standardized graffiti management APIs
ethereum/keymanager-APIs#63
Additional Notes
I made the decision of creating a separate function for
set_graffiti
instead of usingset_validator_definition_fields
. I may be missing context here, but I feltset_validator_definition_fields
usage to be a bit dangerous here as it technically updates 4 fields (enabled
,gas_limit
,builder_proposals
andgraffiti
)