feat: Add MEV-boost sidecar support for validators #36
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
- Add MEV-boost Kubernetes deployment manifests - Configure network-specific relay endpoints for mainnet, sepolia, and holesky - Integrate MEV-boost with all consensus clients (Nimbus, Lighthouse, Teku, Prysm, Lodestar) - Auto-deploy MEV-boost when running full nodes (--mode full) - Add comprehensive documentation for MEV-boost setup Fixes #34
- Update mainnet relays: Fixed Aestus and Agnostic relay addresses, replaced Ultrasound with Manifold - Update sepolia relay: Corrected Flashbots Sepolia public key - Update holesky relays: Use Aestus and Ultrasound staging relays - Update documentation to reflect correct relay endpoints
OisinKyne
approved these changes
Sep 11, 2025
Contributor
OisinKyne
left a comment
OisinKyne
left a comment
There was a problem hiding this comment.
Approving to unblock, but changes needed. Please at a minimum run your code before making me PR review vibe coded work
Contributor
|
Trying to get this turned on on my local machine and mev-boost is bootlooping, so going to commit some of my suggestions here and merge |
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.
Summary
Adds MEV-boost as a sidecar service to enable validators to access MEV rewards when running full nodes in the Obol Stack.
Problem Solved
Fixes #34 - Validators running in the Obol Stack now have access to MEV rewards through integration with the block builder market.
Changes
🏗️ Infrastructure
/manifests/mev-boost/--mode full🔗 Network Support
⚙️ Consensus Client Integration
All consensus clients now support MEV-boost with appropriate flags:
--payload-builder=true --payload-builder-url=<mev-boost>--builder=<mev-boost>--builder-endpoint=<mev-boost>--http-mev-relay=<mev-boost>--builder=true --builder.urls=<mev-boost>📚 Documentation
Testing
To test MEV-boost integration:
./obolup --mode full --network mainnetkubectl get pods -n l1 -l app=mev-boostkubectl logs -n l1 deployment/mev-boostImpact
References