pm VS annotated-spec

Get involved in the next public testnet. Holešky testnet (Goerli successor) first launch coordination call June 15, targeting September genesis https://github.com/ethereum/pm/issues/803

Attend some All Core Dev meetings if you have doubts https://github.com/ethereum/pm

EIP4844 readiness checklist: https://github.com/ethereum/pm/blob/master/Breakout-Room/4844-readiness-checklist.md

Dencun upgrade with EIP4844 is likely later this year, which will bring lower cost Layer 2 transactions. Follow the readiness of EIP4844: https://github.com/ethereum/pm/blob/master/Breakout-Room/4844-readiness-checklist.md Prague + E starname upgrade is probably 2024, possibly focused on EOF, then followed by a Verkle tree focused upgrade, but none of this has been decided.

There's an EIP 4844 readiness checklist.

The live date for the Shanghai upgrade is likely to be April 12, occurring at epoch number 620,9536. This was announced during the All Core Developers Execution Layer #157 call on 16 March 2023.

On December 8, 2022, the Ethereum core team held an All Core Developers (ACD) meeting. The Ethereum team agreed to target March 2023 as the release date for Shanghai’s mainnet launch. However, this is a tentative date based on the assumption that the Zhejiang, Sepolia, and Goerli testnets are successful.

Shanghai is the next major upgrade for the Ethereum network, following the Merge in September 2022. Key highlights of what to expect include:

My current understanding: The Sync Committee selects 512 validators to continually sign off on block header. Any block headers that get >2/3 are "valid"1, such that Light Clients using this header for verification can trust it.

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. It’s more expensive to run a slasher but you need only one and it does not matter who runs it, anyone can run it. The link that you sent says that this slasher broadcasts proofs by default - that way anyone can include it.

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

Here's some more info on Sync committees if you are interested. https://github.com/ethereum/annotated-spec/blob/master/altair/sync-protocol.md

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 are aware of this issue and are actively working towards it. They shipped the Altair hard fork this year that has adds sync committees which make it possible to do without needing the whole chain history (using merkle trees): https://github.com/ethereum/annotated-spec/blob/master/altai...

The light client to follow from those improvements is forthcoming:

It's not about validators going offline, it's about the validator set changing. To quote the annotated specs

Even a relatively light reading of the Annotated Spec[1] for Eth2 and/or the Eth Org's Proof of Stake FAQs[2] suggests the designers (and independent implementer-teams who gave feedback to designers... lather, rinse, repeat) understand it's important to consider the overall system "outside of the comfort zone".

[1] https://github.com/ethereum/annotated-spec/blob/master/phase...

[2] https://eth.wiki/en/concepts/proof-of-stake-faqs

Alpha leak: I am currently finishing up a full revision of my annotated specification for Altair, and plan to get it published in a couple of weeks. Meanwhile Vitalik's annotated spec has some info on how base rewards work under Altair.