mev-boost VS go-ethereum

FYI, this is fixed now: https://github.com/flashbots/mev-boost/issues/541

mev-boost v1.6 was released yesterday - it's often the part of the validator stack that gets neglected when it comes to updates.

For the setup, did you look at https://boost.flashbots.net/ ? Pretty straightforward, and examples of configuration for validator nodes are provided for each soft (prysm, lighthouse, nimbus...). I remember using that (and potentially doing one or two little adjustments). For the explanation, flashbot doc is nice, you can start here: https://docs.flashbots.net/new-to-mev

Are you also using MEV? Because a few people seem to have this same issue. Maybe it is a MEV-Geth thing. If so could you post your MEV logs?

Ahh I see yep, on the builder side not the validator side. Validators using https://github.com/flashbots/mev-boost but whichever builder gets chosen may likely be using those (especially if flashbots has the highest bid).

Personally I think the risk benefit is better to have mevboost activated. https://github.com/flashbots/mev-boost/issues/518

The same thing happened to me, I opened an issue in prysm and in mevboost, we are not the only ones with bad luck, https://github.com/prysmaticlabs/prysm/issues/12434 https://github.com/flashbots/mev-boost/issues/516 try adding the --build-block-parallel flag I also removed 2 relays, flashboot and brute. Hopefully next time we'll have better luck. sorry for my bad english

MEV-Boost is an implementation of proposer-builder separation (PBS) built by Flashbots for proof of stake Ethereum. Validators running MEV-Boost maximize their staking reward by selling blockspace to an open market of builders.

Read the q&as on GitHub. Total shambles. No plan, few commits. bizarre replies. Coinbase eventually had to submit a Pull Request as all support channels closed/unanswered. Read it and weep. Last post 15hrs ago, the soap-opera continues. https://github.com/ethereumpow/go-ethereum/pull/17

That is what they have claimed for a while now. Their geth fork has yet to actually implement this chain ID, and they actually don't plan to do so until after the merge has occurred. So there will be some initial chaos as the miners sort things out, but presumably at some point the team will provide the proper code to carry out the fork and enough people will run it to establish a stable network. Presumably. I'll believe it when I see it.

This is the Repo where you can see if the chain ID has been updated: https://github.com/ethereumpow/go-ethereum/blob/master/params/config.go

This was pointed out to them multiple times on their Github repository (https://github.com/ethereumpow/go-ethereum/pulls) and a poll was taken to chose a more appropriate ChainID ( https://www.rcv123.org/results/rr6xjagxbmoR8CSKUSobW6/qtGJMHK7pBeugsJ1KFpv3S) which settled on 1111, but has been ignored.

The fun bit is in the pull requests: https://github.com/ethereumpow/go-ethereum/pulls