mev-boost VS eth2.0-specs

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.

Eth2 beacon blocks get a "graffiti" data field, "to be used in wonderful and unpredictable ways".

Eth2.0 spec v0.6.0 "Spring Cleaning" is out.

Ethereum developers propose an increase in validator rewards for Eth 2.0 .

Eth2 Phase 0 spec v0.3 is out, named "Let There Be Liquidity", which includes a number of small feature additions/modifications, clarifications, and minor bug fixes.

Justin Drake adds a mechanism to the Eth2.0 spec for validators to transfer their balance on the beacon chain (to be removed after phase 1).

The Eth2 spec v0.2 gets out, containing a number of small feature additions/modifications, helpers, clarifications, minor bug fixes, and the introduction of a point-wise shuffle.

And finally, hard-core specs here: https://github.com/ethereum/eth2.0-specs

The Ethereum 2.0 spec v0.12 "Quarantine Haircut" uses IETF's hash-to-curve draft for BLS, and is the closest version to the final Eth 2.0. release.

"offence is identified and protocol-level penalties are enacted by a “whistleblower.” The whistleblower collects evidence of the offence and commits proof(s) to a block proposer for inclusion on-chain. After Phase 0 the whistleblower will earn the majority of those rewards (seven-eighths), but in Phase 0 the block proposer earns the full reward."

Eth2 beacon blocks get a "graffiti" data field, "to be used in wonderful and unpredictable ways".