smartnode VS rocketpool-research

Fixed a bug that prevented nonce overrides from working with nonce 0. (https://github.com/rocket-pool/smartnode/issues/169)

node sync and node deposit will now make sure your Beacon Chain client is running on the chain that Rocket Pool expects it to be running on before letting you do a deposit (https://github.com/rocket-pool/smartnode/issues/158).

https://github.com/rocket-pool/smartnode/commits/testnet)

As many here who plan to operate a Rocketpool node probably know, the hot wallet required by the node software is a bit of a hot topic (pun intended). I opened an issue about this some time ago, and there are efforts underway by the developer team to solve this issue. Basically there will be a way to define a separate and locked withdrawal-address, where any withdrawals and RPL claims will be paid out to. This is an important security feature and should definitely be used for mainnet.

Relevant issue on github about this: https://github.com/rocket-pool/smartnode/issues/83

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