dappnode / DAppNodePackage-teku

Apache License 2.0
2 stars 2 forks source link

Issue with MEV-Boost Params in Validator service #57

Closed alexpeterson91 closed 1 year ago

alexpeterson91 commented 1 year ago

Describe the bug

When running the latest version of Teku on mainnet there are errors thrown in the validator service when MEV-Boost is set to enabled. but it shows this error on startup 2023-04-04 19:35:28.757 INFO - '--validators-builder-registration-default-enabled' requires '--validators-proposer-blinded-blocks-enabled', enabling it

To Reproduce Install latest Teku version, set teku as chosen mainnet CL client in stakersUI and enable MEV-Boost in the StakersUI when synced validator logs will show this error (full logs are below this is just the warning shown with some lines removed for clarity

MEVBOOST is enabled
... ... ...
2023-04-04 19:35:28.757 INFO  - '--validators-builder-registration-default-enabled' requires '--validators-proposer-blinded-blocks-enabled', enabling it

Expected behavior Teku's docs have previously stated that the flag --validators-proposer-blinded-blocks-enabled was automatically enabled when --validators-builder-registration-default-enabled is passed. but this No longer seems to be the case, not sure if the new versions have changed the docs, but the warning passed in the logs clearly says that they both need to be passed for MEV-Boost to be activated properly on teku.

Screenshots logs-dappnode-package-DAppNodePackage-validator.teku.dnp.dappnode.eth.txt

Resolution

add the flag --validators-proposer-blinded-blocks-enabled to the MEV if then statement in the validators entry point.

Additional context

when i add the flag --validators-proposer-blinded-blocks-enabled to the validator Extra Opts the error disappears, which is why this appears to be easily fixed.