Skip to content

Comments

fix: support custom CL for MEV builder (issue #627)#1277

Open
DarkLord017 wants to merge 6 commits intoethpandaops:mainfrom
DarkLord017:fix-cl
Open

fix: support custom CL for MEV builder (issue #627)#1277
DarkLord017 wants to merge 6 commits intoethpandaops:mainfrom
DarkLord017:fix-cl

Conversation

@DarkLord017
Copy link

  • Infer CL type from mev_builder_cl_image instead of hardcoding Lighthouse
  • Set CL-specific builder flags for all supported clients
  • Use correct beacon HTTP port in builder config CLEndpoint
  • Add robust cl_type inference in cl_launcher based on image

Tried to fix #627
Please review @parithosh @barnabasbusa , am i heading towards the issue correctly

- Infer CL type from mev_builder_cl_image instead of hardcoding Lighthouse
- Set CL-specific builder flags for all supported clients
- Use correct beacon HTTP port in builder config CLEndpoint
- Add robust cl_type inference in cl_launcher based on image
@DarkLord017
Copy link
Author

@barnabasbusa ran it with all cl clients , plese check is it correct ?

@barnabasbusa
Copy link
Collaborator

I still do not see how will nimbus and grandine going to trigger a payload event for each slot?

@DarkLord017
Copy link
Author

I still do not see how will nimbus and grandine going to trigger a payload event for each slot?

I looked at their docs & code and tried to find out , but wasn't able to .. is it possible that it does not exst for these clients ?

@DarkLord017
Copy link
Author

DarkLord017 commented Jan 10, 2026

@barnabasbusa nimbus n gradine do not support this feature , n like getting a json serialization error with lodestar , so added with teku , prysm

please review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Cannot configure non-Lighthouse CL for builder

2 participants