Specify Builder Configurations, Bid multiplexing and Bid selection strategies #144
+134
−10
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
bharath-123
commented
Jan 16, 2026
Comment on lines
+349
to
+351
| # Builders must respond by 2 seconds into the slot | ||
| # This leaves 2 seconds for local building fallback | ||
| return slot_start + BUILDER_DEADLINE_MS |
Collaborator
Author
There was a problem hiding this comment.
This deadline can be just 1 sec.
bharath-123
commented
Jan 16, 2026
| # Validate the bid | ||
| registration = registrations.get(builder_config.url) | ||
| if registration and validate_bid(state, registration, signed_bid, registration.message.fee_recipient): | ||
| bids.append((builder_config, signed_bid)) |
Collaborator
Author
There was a problem hiding this comment.
Bid needs to be boosted before being added.
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 attempts to specify MEV-Boost behaviour in clients. This can help us in the path forward to deprecate the MEV-Boost sidecar from the protocol.
The main functionality of MEV-Boost is to maintain a whitelist of builders and to multiplex requests to get bids from them. This can potentially be absorbed into clients quite easily.
If MEV-Boost is absorbed into clients, it will be important to define the expressivity an operator can have in the block auction. Parameters like min-bid, builder-boost and a global bid selection strategy can help us achieve the required expressivity.
We define three new Containers:
BuilderConfig: It contains the url, max_trusted_bid, min_bid and bid_boost per builder.GlobalPreferences: It contains thebid_selection_strategywhich is a string which defines a particular strategy.BuilderWhitelist: It contains the list of BuilderConfig and the GlobalPreferences across builders.We query all the builders in parallel and validate their bid according to the builder config for the given builder. We then apply the bid selection strategy to choose the best bid out of all the valid bids received.