feat: Bolt Boost and Helix configuration #9
Merged
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
test template test tempalte asdf test temaplate asdf
boost launch boost boost asdf asdf
merklefruit
reviewed
Oct 3, 2024
merklefruit
reviewed
Oct 3, 2024
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.
This PR introduces support for both Bolt Boost and Helix.
mev_params.bolt_boost_imageinsidenetwork_configs.yaml. If set it will be used in place of MEV-BoostThe current configuration is sufficiently configurable, ideally I'd be great to do allow granular configuration by parsing appropriate
network_configs.yamlfields but that's out of scope for now.NOTE: this PR doesn't guarantee that both Bolt Boost, the sidecar and the Helix fork work correctly together, but it is just the preliminary step needed to coordinate them and launch Kurtosis successfully.