mev-boost VS zkevm-circuits

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.

They work with Ethereum Foundation for the zk-evm https://github.com/privacy-scaling-explorations/zkevm-circuits and imo nothing beats type 1 zk-evm - even if they are a bit "late".. it will matter on how the type 1 zk-evm will handle decentralization and incentives..

That zkEVM is the ONLY one that's EVM-equivalent. It's the only one supported by the Ethereum Foundation. It's the zkEVM that Scroll.io is helping develop. It's the same zkEVM that Loopring was working on with EF, and that Taiko is going to use. It's also open source.

zkEVM circuit auditing: The goal here is to find bugs in zkEVM circuits developed by the EF and others. All auditing techniques are fair play (e.g. code inspection, fuzzing, formal verification).