annotated-spec

I know about that but thanks for your comment - I’ll clarify what I mean. It’s just the specifics of how this works - slashing is part of the protocol in the sense that I described: when you are chosen to create a new block and you have proof that someone violated the rules then you include this proof in your proposed block and update balance. Any validator can do it including the smallest of home stakers. More details here. https://github.com/ethereum/annotated-spec/blob/master/phase... Here we have slashing fields in the block body where you insert your proofs of slashable offense. There are functions with a “slash” in the name that describes precise state transition. The hard part of slashing is finding these proofs because you have to do more work than necessary to detect slashing and produce proofs - that’s what this software does.

Great question. You can check here how the 32 ETH came to be: https://github.com/ethereum/annotated-spec/blob/master/phase...

According to Eth docs: > One validator is randomly selected to be a block proposer in every slot. This validator is responsible for creating a new block and sending it out to other nodes on the network. Also in every slot, a committee of validators is randomly chosen, whose votes are used to determine the validity of the block being proposed. The annotated code for this can be found in [2]. [1] https://github.com/ethereum/annotated-spec/blob/master/phase... [2] https://notes.ethereum.org/@vbuterin/Sys3GLJbD#Misc

The crux of the article is that the front-ends are all routing calls through centralized APIs to get their message included on the blockchain. Infura and Alchemy don't do much. They just pass a JSON-RPC message to an Ethereum node running on their servers. There is some additional indexing services they provide, but there are many open, decentralized alternatives for that such as TheGraph Protocol. And it's not unfeasible for an application to run its own Postgres instance to index data from the ETH blockchain. As for full-fat clients on normal mobile devices, the main issue is the data requirements. Running a full node can take hundreds of gigabytes. It is possible on light hardware. People are running Beacon chain nodes on Raspberry Pis. But you do need the storage and that tends to be scarce on mobile. Meanwhile, the Ethereum core devs

Even a relatively light reading of the Annotated Specs for Eth2[1] and/or the Eth Org's Proof of Stake FAQs[2] suggests the designers (and independent implementer-teams who gave feedback to designers, who gave direction to the implementers... lather, rinse, repeat) understand it's important to consider the overall system "outside of the comfort zone". [1] one such: https://github.com/ethereum/annotated-spec/blob/master/phase... [2] https://eth.wiki/en/concepts/proof-of-stake-faqs

https://github.com/ethereum/annotated-spec/blob/master/phase... After withdrawal is completed, your node would no longer be in the set of active validators and from that time could not validly propose a block or submit an attestation (or, more accurately, be selected as a block proposer, etc.)

I agree about the energy use of PoW. On Ethereum, the PoS beacon chain has been live for almost a year now [1], with the merging of the PoW and PoS networks happening next year. We're now at the point where the specs for the merge transition are ready [2], clients are already being modified to target the release-spec [3], and the first long-lived testnet will go live by December. I'd personally expect the Merge to happen by May. [1] https://beaconcha.in [2] https://github.com/ethereum/annotated-spec/blob/master/merge... [3] https://notes.ethereum.org/@djrtwo/kintsugi-milestones