You can see the current numbers for yourself here: beaconcha.in/pools. One important thing to note is that Ethereum's PoS algorithm uses penalties that are correlated with how many other people do something wrong along with you.
This means that while we can't stop people from staking on AWS, or using the most popular client, etc. we can give them an economic incentive to setup their staking node in a way where their failures are uncorrelated from the rest of the network.
Alongside that, Ethereum's Pos aims for validators to be profitable if they are online >2/3 of the time. This means it is much less risky for folks to stake on non-production-grade infrastructure.
But, to answer explicitly, as of today, we see 26% staking from exchanges, 15% via pools and the rest is a mix.
TL;DR: yes, and we are exploring ways to disincentivize that. Although, to be clear, MetaMask doesn't really matter here given it's not used to perform any staking duties, it's just an Ethereum wallet and there are already a multitude of options for those
Specifically, we are planning to ask validators to provide proofs that they actually have a copy of the data. See here for more details: ethresear.ch/t/a-0-001-bit-…
That is the cost for a single staker, yes, but there are already decentralized staking pools for people who want to stake with less, see @LidoFinance@Rocket_Pool.
Re: the 32ETH min dropping, it hasn't been discussed yet, but I suspect if there was a way to do it without significant downsides, it likely would happen. Very early iterations of the PoS design had a ~1000 ETH min, and when it was discovered we could do less, it was lowered.
The short answer, as with all blockchains, is "social consensus".
The best summary of Ethereum's social consensus around monetary policy is "minimum necessary issuance", which is expanded on here: docs.ethhub.io/ethereum-basic…
This obviously is less straightforward than Bitcoin (though potentially more viable, but that's another debate 😅). EIP-3368, which I mentioned yesterday, is an example of a proposal being rejected because it went against this ethos.
Yes, that sounds roughly right for *issuance*. The wide range is because the issuance is based on how many people are staking. The rewards for staking drop as more people join so that the protocol targets a safe but not excessive number of stakers.
While these numbers are for issuance, it is worth noting that Ethereum will introduce a "fee burn" this summer (EIP-1559). That change could be its own thread, but in short, it burns a large % of all transaction fees, reducing supply. The % burnt increases with blockspace demand.
So, if you had a fairly low issuance from staking and a fairly high burn from transaction fees, the Ether supply could be deflationary, which strikes a nice balance between limiting inflation and ensuring a long-term budget for validator rewards.
If you are looking to dive in deeper, the Eth2 annotated spec I linked right above, this 1559 list hackmd.io/@timbeiko/1559… and @ethhub_io are all great resources!
• • •
Missing some Tweet in this thread? You can try to
force a refresh
First up on the call was Berlin updates 🇩🇪 The Rinkeby fork went well, nothing to report. The mainnet fork block is going to happen on April 14/15, see a countdown here: goto.etherscan.com/block/countdow…
We've got a ton to cover today: two hard forks, eth2 merge requirements, a list of things we should remove from Ethereum by @VitalikButerin and a quick shoutout for the 1559 community call with miners happening next week.
First up is checking in on YOLOv3's status: Besu, OpenEthereum, Nethermind and Geth are all in sync ✅
@crypto_fruit I think it should be "ready to be considered for mainnet" in the next few weeks. See this checklist for what's left to do: github.com/ethereum/pm/bl…
We want to get the "Client Level Open Issues" done before we present it on AllCoreDevs.
@crypto_fruit As you can see on the list, there is only one issue outstanding. We have preliminary results indicating that it should be OK (hackmd.io/@timbeiko/1559…), but next week we're running a proper test.
@crypto_fruit After that, I'd be comfortable proposing 1559 for inclusion to core developers. If everyone agrees, then it would be a candidate for the next network upgrade, and those usually happen every 6-9 months. We'll probably have one over the summer.