You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Teku 25.4.1 in a validator-client mode only (external consensus client) with Mev-Boost 1.9, a produced block did not use Mev-Boost. In looking at the consensus client logs, builder_boost_factor was set to zero (which forced the consensus client to choose it's local payload). Is there a Teku validator-client configuration parameter to set the builder_boost_factor to 100?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When using Teku 25.4.1 in a validator-client mode only (external consensus client) with Mev-Boost 1.9, a produced block did not use Mev-Boost. In looking at the consensus client logs, builder_boost_factor was set to zero (which forced the consensus client to choose it's local payload). Is there a Teku validator-client configuration parameter to set the builder_boost_factor to 100?
Here's my current Teku Config file:
ExecStart=/usr/local/bin/teku/bin/teku validator-client
--network=mainnet
--data-path=/var/lib/teku
--beacon-node-api-endpoint=http://127.0.0.1:5555
--validator-keys=/var/lib/teku/validator_keys:/var/lib/teku/validator_keys
--validators-proposer-default-fee-recipient=0x3AD08c2eeB83e4C561B5CFDC62E7645AXXXXXXXX
--validators-graffiti="/< () [) /\ "
--validators-builder-registration-default-enabled=true
--metrics-enabled=true
Beta Was this translation helpful? Give feedback.
All reactions