-
-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ADD: mevboost-EL & CL in molecule test #667
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add these changes:
- remove
location
ofcreate.yaml
of blockCreate molecule instance(s)
, there is no need for this anymore - trim down the parameters of the el/cl as much as possible to make it clear what parameters matter to run with mev-boost
- use a variable of
stereum_defaults.yaml
forhttps://0xafa4c6985aa049fb79dd37010438cfebeb0f2bd42b115b89dd678dab0670c1de38da0c4e9138c9290a398ecd9a0b3110@builder-relay-goerli.flashbots.net
Is there any log output on the consensus or execution client that would verify the connection to mev-boost?
command: "docker logs stereum-5bc8cb90-1909-11ed-9142-cf15cf490a91" | ||
register: lighthouse_beacon | ||
until: | ||
- lighthouse_beacon.stderr is search("The execution endpoint is connected and configured, however it is not yet synced") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lighthouse doesn't show any information about a connection between mevboost and beacon node
part of: #529
#692
Consensus:
Execution: