rocketpool-research VS besu

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

Daily Goerli: I've been testing this PR for besu for the past several days, and the stability of nimbus-besu has improved substantially. Looking forward to it getting merged into main.

Check out the Layered TX pool PR for more details and benchmarks - https://github.com/hyperledger/besu/pull/5290

you can check this spreadsheet for a comparison https://github.com/hyperledger/besu/files/11137473/Layered.Transaction.Pool.metrics.ods

Yes, it's gotten better. I don't recommend pairing with nimbus until this issue gets fixed or prysm until something is done to reduce the amount of time it takes to recover from being offline for a day or more.

Daily Goerli: On Friday, I reported a RocksDB issue that was causing besu to error and exit immediately. The bad commit has been identified and a fix has been issued. lodestar-nethermind somehow ended up on an invalid fork which isn't resolved by restarting either client. Waiting to see how each client team responds and if they need more info, but might need to do a resync.

https://github.com/hyperledger/besu 148 contributors

Download links and release notes here: https://github.com/hyperledger/besu/releases/tag/23.1.2

Now running into this error on my freshly synced Besu 23.1.0. 😔️