feat: add commit-boost support #779
Draft
+222
−3
Conversation
This file contains 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
|
when tested locally the logs will look like this |
ltitanb
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Initial support for Commit-Boost, adding for now only the PBS module (equivalent to MEV-Boost).
Note that this depends on this PR being merged and released.
There is sometimes some ambiguity between mev-boost (go client) and mev-boost (protocol via the Builder API), so to disambiguate within commit boost we call the PBS module the sidecar implementing the mev-boost protocol.
Here I followed the existing convention as much as possible even if it sounds somewhat repetitive at times (commit-boost-mev-boost).