0x64
There are obviously large staking pools (including decentralized pools), but there is also a substantial community of people who stake from home on a validating node of their own. A good example is the EthStaker community on Reddit [1].
The compute and bandwidth requirements are very permissible (quad-core CPU, 16-32 GB memory, 2-4 TB SSD, 20/20 Mb/s), and the theoretical size of minimum stake has gone down substantially over time due to Rocket Pool [2].
[1] https://reddit.com/r/ethstaker/
[2] https://rocketpool.net/node-staking/rocket-pool-vs-solo-stak...
The minimum cost to acquire an ASIC so that you can even _contribute_ to the consensus is very high (thousands), and to be profitable you have to have close to free electricity. The ironic thing is, that in PoW the "rich get richer" is abstracted away into a combination of economies of scale, and access to free/very cheap power. Plus all the e-waste and wasted power, whereas PoS runs on e-waste people run in their closet, pulling as little as sub-10 watts.
"Actual transaction costs are estimated around 0.001 cent/tx (at high transaction rates, amortized over billions of transactions, excluding migration costs). Note that this is an early estimate -- and could thus easily be 10x higher." [1]
Transactions costing singular cents [2], and very soon fractions of a cent [3], are already doable on public rollups providing actual control of your own funds, with escape hatches in case the system sequencer falls over [4]. These are, of course, still under heavy development. If privacy is a requirement, there's a zk-rollup for that (or, just use Monero). Not to mention support for social recovery.
This is a very PoS-Ethereum-centric (and L2-scaling-centric) view. There are even cheaper chains that trade L1 decentralization for faster blocktimes, instant finality, and/or much cheaper fees.
* Wholegrain oats (1.5 to 2 dl)
* Greek yogurt (1.5 to 2 dl)
* Milk, skimmed/whole (3 dl)
Then, throw in whatever. A sliced banana or berries, honey, a pinch of vanilla extract. Prep it in the evening, chuck it into the fridge, and it's done in the morning.
These relays effectively accept bundles from MEV searchers, which are then sent to the validator running mev-boost as they propose their block.
On top of that, you have to factor in luck: block proposals are randomly assigned to validators, and they include a random amount of tips depending on network activity. You could propose a block that nets you 0.01 ETH in tips, or a block with 50 ETH in tips.
On average, I believe the post-Merge APY has been estimated to be ≈6 % (non-cumulative).
Hardware can be anything. Even a RasPi 4 with 8 GB of memory can be made to work. Any old x64 machine with two or more cores works. 16 GB of memory is recommended, as is a 2 TB SSD to minimize down-time. Storage requirements are likely to go down in the medium-term, as e.g. state expiry get implemented.
I’d recommend an Intel NUC. They use laptop CPUs, so electricity consumption is around 5–20 watts. For networking, you’ll need around 5 Mb/s up and down after the initial sync.
Fees are currently as low as $0.03 on Ethereum layer-2 solutions (!= side-chain) [4]. The fees will further fall as the technology improves, and once L1 gets (data-/dank-)sharding and other L2-scaling oriented upgrades.
[1] https://makerdao.com/en [2] https://reflexer.finance [3] https://www.circle.com/en/usdc [4] https://l2fees.info
So a US CBDC will be decentralized, permissionless, transparent, non-censoring, and run on open-source software based on an open specification?
Attestations occur for every validator once every epoch, i.e. once every 6.4 minutes. It is not related to network activity in any way.
It's an extremely nuanced topic, and it was extensively discussed in the last core-developer call on Thursday. Every single operator has been warned that going against the fork-choice rules could, and ultimately will, result in social mitigations against spec-deviating behavior.
This could be set of socially executed slashings of validators that don't respect the fork-choice rules, or an honest-minority executed hard-fork that effectively causes misbehaving validators to bleed until they start respecting the protocol's rules.
I could be wrong on multiple counts, especially regarding re-orgs, but this is how I've understood the issue.
More on Ethereum light clients from Chainsafe, the builders of Lodestar, a Typescript implementation of an Ethereum consensus client: https://blog.chainsafe.io/the-road-ahead-for-ethereum-light-...
TL;DR: "Light clients enable more people to participate as first-class citizens, verifying on-chain data without relying on single and centralized JSON RPC endpoints."
Well...
- five+ different consensus clients, all with a full PoS implementation and a working PoW -> PoS transition mechanism
- four different execution clients, all with a working PoW -> PoS transition mechanism
- Multiple (dozen+) of successful merges on testnets and shadow forks. Ropsten, an ancient test network, was successfully merged to PoS from PoW a couple weeks ago.
There's two more existing testnets that will be merged soon. Sepolia on the 5th of July, and Goerli on some date TBD. If those are successful and there are no major issues found, it's time for mainnet.
And, Ethereum will transition to PoS by this year, ideally in August. All of the popular nine Ethereum execution/consensus clients should be ready for the merge, and mainnet has already been test-merged five times successfully.
The first existing PoW testnet will be merged on the first week of June. After that, there's two testnets remaining that will be upgraded (Ropsten -> Goerli -> Sepolia), and then it's time for mainnet.