consensus-specs VS rocketpool

I think its 1 million: https://github.com/ethereum/consensus-specs/issues/2137

how "radically decentralized" the development of the Ethereum core is. In the past half a decade only 133 devs have contributed to Ethereum source code. 2 devs have written 25% of the code. The first 10 developers have written 70% of the Ethereum code. Consensus specifications the ones that all the clients implement. Half are Consensys employees https://github.com/ethereum/consensus-specs

I think this will be defined here: https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/fork-choice.md

Clients dependent on Consensys core and ETH management repo. A client is just the implementation directed by Consensys written in a different language. Fact is about 10 developers are the only reason those clients will update with staking. https://github.com/ethereum/consensus-specs

Exits are processed at 7 per epoch (currently). There is no queue for withdrawals. See https://github.com/ethereum/consensus-specs/pull/3068

https://github.com/ethereum/consensus-specs/blob/dev/specs/p...

For that, we have to take the vanilla deposit contract from the consensus specs: deposit_contract.sol, get the Solidity compiler version 0.6.11, compile the binary of the runtime part, and create an empty deposit tree.

The PoS consensus specification

And yes, you can swap your rETH back with the protocol directly on www.rocketpool.net

Discord is a must for anything Rocketpool related. There is a link on the website at www.rocketpool.net

You can check the official rEth to Eth ratio at www.rocketpool.net

The source code of the contract can be revised here: github repo

when deciding to take part in a staking pool that allows them to run a Validator with just 16Eth instead of 32 for sharing their staking rewards 50/50 + commission as displayed on www.rocketpool.net for years now.

The Merge - finished initial contract changes for The Merge based on this research: https://github.com/rocket-pool/rocketpool-research/blob/master/Post%20Merge/Merge%20Implementation%20Research.md For those who are interested, here is the branch: https://github.com/rocket-pool/rocketpool/tree/merge-ready Please note that it is under code review, requires further testing, and is unaudited at this stage.

All Rocket Pool code has been open source over more than 4 years, longer than any other major ETH project.

Website: https://www.rocketpool.net/

Review their smart contract code, but since that’s complicated, research their auditors and audit reports.