rocketpool-research VS rpc-endpoint

What's to stop the authorities from outlawing all relays except the censoring ones? When you are forced to use MEV-boost trough threat of penalties (up to 80% of your stake!), then even those of us that "fell" for the decentralised promise of RP will be forced to be complicit in censorship.

Unfortunately RP is also starting to look more and more centralised. In the latest upgrade they introduce penalties which were not included in the original "dumb contract" between us, validators, and RP. What's worse, they speak of forcing validators use MEV-boost.

This surprised me a bit - I know this is how it works for a 16 eth node where it has to wait for another 16 eth to be matched and sent by the contract, but what about in my case? Am I still stuck waiting for the oDAO to confirm "everything looks right" (per here)? And if so, is there a way to see where I'm at on this queue? So is the contract holding the other 16 eth in the general pool and then will send it (basically "reserving" it for me)?

This is a better place to dive deeper into the research being done on this and other topics: https://github.com/rocket-pool/rocketpool-research

The minipool will wait for 12 hours while it gets vetted by the Oracle DAO to make sure it didn't abuse the Beacon Chain's withdrawal credentials exploit (this is known as the "scrub check")

We'll make sure to keep our awesome community updated as we go roll out our solution to this unexpected, but very welcomed addition to the protocol. https://github.com/rocket-pool/rocketpool-research/blob/master/Reports/withdrawal-creds-exploit.md

More info on this can be found here: https://medium.com/rocket-pool/the-merge-0x02-mev-and-the-future-of-the-protocol-c7451337ec40 and here: https://github.com/rocket-pool/rocketpool-research

Link to repository: https://github.com/rocket-pool/rocketpool-research/blob/master/delegate-upgrades.md

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