Ethereum's first block, also known as Frontier, occurred nearly two years after its ideation.
A large VC fund (The DAO) crowdsourced by the Ethereum community was hacked. A controversial hard fork was implemented to recover the lost funds.
Six hard forks over five years upgraded the EVM and were independent of the Beacon chain, although a few changes at the end were preparatory.
Enabled validator withdrawals from the Beacon Chain, completing the transition to PoS.
Scaled Layer2s through EIP-4844 with Blobs + other auxiliary improvements.
The community is still debating what exactly to include. Could go live at the end of 2024.
Originally part of Prague-Electra, and then Pectra 2/B. EOF + PeerDAS + More.
Far out, but likely Verkle Trees
This marked the beginning of Ethereum's transition to a proof-of-stake consensus mechanism, and the genesis of what is now the consensus layer.
The first upgrade to the Beacon Chain. It introduced several improvements, including sync committees.
A preparatory upgrade for the Beacon Chain that set the stage for the merge.
The transition from proof-of-work to proof-of-stake, triggered by reaching the Terminal Total Difficulty, and was not a hard fork.
Enabled validator withdrawals from the Beacon Chain, completing the transition to PoS.
Scaled Layer2s through EIP-4844 with Blobs + other auxiliary improvements.
The community is still debating what exactly to include. Could go live at the end of 2024.
EOF, PeerDAS, and more
This hardfork is tentatively being reserved for Verkle Trees.
Part I, Part II, Part III, Part IV, Part V
For decentralization and redundancy sake, Ethereum opted for a multi-client approach. Every Ethereum upgrade must be coordinated and developed in tandem with the five teams in the appropriate layer.