rpc-endpoint VS mev-boost

You might want to look at their Flashbot Protect RPC. So, you might want to look at this one: https://github.com/flashbots/rpc-endpoint

Ethereum toolset alteady complying with OFAC https://github.com/flashbots/rpc-endpoint/blob/main/server/ofacblacklist.go

Has the Geth team ever considered or been pressured to add blacklist measures similar to those we are currently trying to remove from flashbots? What is the Geth team's stance on node-level blacklists?

how about check the flashbots github and come back with that same energy. i will be calm when everyone else is not, and not calm when they are (like now)

MEVBoost/Flashbot has already blocked all Tornado Cash smart contract addresses: https://github.com/flashbots/rpc-endpoint/pull/90

For the record, it feels like we've all got confused about the MEV-Boost OFAC Blacklist stuff. The changes, and proposed reversion - is on an unrelated repo https://github.com/flashbots/rpc-endpoint. These are RPC endpoints. MEV-Boost itself has no such proposals, and the only discussion i can find in the issues list is a long discussion of maintaining censorship resistance, https://github.com/flashbots/mev-boost/issues/215

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.