From 240310b771b15187060ef253ed282fd78d05e58d Mon Sep 17 00:00:00 2001 From: Ifeoluwa Date: Mon, 23 Feb 2026 16:32:10 +0100 Subject: [PATCH 1/4] lean consensus --- .../lean-ethereum-and-state-proving.md | 211 ++++++++++++++++++ 1 file changed, 211 insertions(+) create mode 100644 docs/wiki/research/lean-ethereum-and-state-proving.md diff --git a/docs/wiki/research/lean-ethereum-and-state-proving.md b/docs/wiki/research/lean-ethereum-and-state-proving.md new file mode 100644 index 00000000..38db2142 --- /dev/null +++ b/docs/wiki/research/lean-ethereum-and-state-proving.md @@ -0,0 +1,211 @@ +# Lean Ethereum & State Proving + +## Overview + +**Lean Ethereum** is a long-term technical roadmap for the Ethereum base layer proposed by Ethereum Foundation researcher Justin Drake and published on the EF blog on July 31, 2025. It reframes Ethereum's development priorities around two strategic imperatives: + +- **Fort Mode** — Hardening security to survive nation-state threats and quantum computing advances. +- **Beast Mode** — Achieving extreme performance (targeting 10,000 TPS on L1, 1M+ TPS on L2) without sacrificing decentralization. + +The roadmap restructures all three protocol sublayers — **Consensus**, **Data**, and **Execution** — around a unified cryptographic primitive: **hash-based SNARKs**. + +> Note: Lean Ethereum evolved from the "Beam Chain" proposal that Justin Drake introduced at Devcon 7 in Bangkok (November 2024). Beam Chain specifically referred to a redesign of the consensus layer, now called **Lean Consensus**. The "Lean Ethereum" umbrella was introduced in mid-2025 to encompass all three layers. + +--- + +## The Three Pillars + +### 1. Lean Consensus + +A complete redesign of Ethereum's consensus (Beacon Chain) layer. Key goals: + +- **Post-Quantum Cryptography**: Replace BLS signatures (based on elliptic curves, vulnerable to quantum attacks) with hash-based signature schemes that can be efficiently aggregated using SNARKs. +- **3-Slot Finality (3SF)**: Reduce finality from ~15 minutes to seconds. 3SF is a practical alternative to single-slot finality (SSF) that balances speed, security, and implementation complexity. +- **Reduced Validator Requirements**: Lower the minimum stake from 32 ETH to 1 ETH to increase decentralization. +- **Attester-Proposer Separation (APS)**: Decouple block proposer and attester roles to reduce centralization pressure from MEV. +- **Rainbow Staking**: A novel staking mechanism designed to further enhance decentralization. + +**Key resources:** +- Lean Consensus Roadmap: [leanroadmap.org](https://leanroadmap.org) +- 3-Slot Finality paper (Feb 2023) +- Post-Quantum signature aggregation research series (2025) + +--- + +### 2. Lean Data + +Upgrade Ethereum's data availability (DA) layer: + +- **Blobs 2.0**: Expanding blob throughput initiated by EIP-4844 (Dencun upgrade). +- **PeerDAS**: Peer-to-peer data availability sampling to scale blob capacity without requiring all nodes to download all data. + +--- + +### 3. Lean Execution (State Proving) + +This is where **state proving** becomes central. The goal is to "snarkify" Ethereum's execution layer — replacing full re-execution by every validator with cryptographic proofs of correctness. + +--- + +## State Proving: What It Is and Why It Matters + +### The Problem with Re-Execution + +Currently, every Ethereum validator independently re-executes every transaction in every block to verify the resulting state is correct. This: + +- Requires significant CPU and memory resources. +- Sets a hard upper limit on how much computation (gas) can fit in a block, because validators must finish execution before the next slot. +- Creates high hardware requirements, threatening validator decentralization. + +### The Solution: zkEVMs on L1 + +A **zkEVM (Zero-Knowledge Ethereum Virtual Machine)** allows a specialized actor (a **prover**) to execute a block and generate a short cryptographic proof that the execution was correct. All other validators then only need to verify this proof — which is orders of magnitude cheaper than re-execution. + +``` +Current flow: Block → All validators re-execute → Agree on new state +Future flow: Block → Prover executes + generates ZK proof → All validators verify proof +``` + +This enables: +- **Higher gas limits** (more transactions per block) without burdening validators. +- **Lighter validator hardware** (just proof verification). +- **Full validation on mobile devices** or in a browser tab. +- **Native rollups**: L2s whose state transitions can be verified directly by L1 validators. + +### Type 1 vs Other zkEVM Types + +Vitalik Buterin defined a spectrum of zkEVM types based on Ethereum-compatibility: + +| Type | Compatibility | Proving Speed | Notes | +|------|--------------|---------------|-------| +| **Type 1** | Fully Ethereum-equivalent | Slowest | Zero modifications — works with all existing contracts and tooling | +| **Type 2** | Fully EVM-equivalent | Faster | Minor internal changes, almost all apps work | +| **Type 3** | Almost EVM-equivalent | Faster | Some contract modifications needed | +| **Type 4** | High-level language equivalent | Fastest | Compiles Solidity/Vyper directly to ZK-friendly format | + +For L1 enshrinement, **Type 1** is the target — full equivalence with no changes to existing applications. + +--- + +## Real-Time Proving + +The central technical challenge for state proving is **real-time proving**: generating a ZK proof for an entire Ethereum block within the 12-second slot time. + +### Why 12 Seconds Is Hard + +Ethereum blocks can contain complex, varied computations. A zkVM must prove every EVM opcode executed across all transactions. The proof must be: +- Generated in under ~10 seconds (to leave time for propagation). +- Using less than 10 kW of power. +- With at least 128-bit security. +- From open-source code. + +### 2025: The Breakthrough Year + +Real-time proving was achieved in 2025 across multiple competing zkVM teams, with multiple projects independently reaching the milestone. As of late 2025: + +- **Pico Prism** proved 99.6% of Ethereum blocks in real-time using 64 RTX 5090 GPUs with an average time of 6.9 seconds. +- **SP1 Hypercube** (Succinct) proved 93% of 10,000 mainnet blocks in real-time on a cluster of 200 GPUs. +- Teams including Risc0, OpenVM, Brevis, Snarkify, ZisK, ZKM, and ZKsync all achieved or approached the milestone. + +**ethproofs.org** was launched by the EF to benchmark and compare zkVM performance on real Ethereum blocks. + +### The Proving Pipeline + +The EF blog post "Shipping an L1 zkEVM #1: Realtime Proving" (July 2025) laid out the phased approach: + +1. **Phase 1 — Off-chain proof verification**: Validators optionally run clients that verify proofs generated by zkVMs instead of re-executing. This requires a "pipelining" mechanism (targeted for the Glamsterdam upgrade) to decouple block verification from immediate execution, giving provers more time within a slot. + +2. **Phase 2 — Multi-proof diversity**: Instead of trusting a single prover, validators verify proofs from multiple zkVMs implementing different EVM clients. This extends Ethereum's existing client diversity model to the proving layer. + +3. **Phase 3 — Protocol enshrinement**: zkEVM proofs become a first-class protocol primitive. + +### The L1 zkEVM 2026 Roadmap + +Published by the EF's zkEVM team (via Ethereum Magicians, early 2026), the concrete 2026 milestones include: + +- Standardizing interfaces between execution and consensus layers for proof requests and verification. +- Researching prover markets, censorship resistance, and economic incentives for provers. +- Formal verification of zkEVM circuit correctness. + +--- + +## Cryptographic Foundations + +Lean Ethereum's design is unified around **hash-based cryptography** for both quantum resistance and SNARK efficiency. + +### Why Move Away from Current Primitives + +| Current Primitive | Vulnerability | Lean Replacement | +|------------------|---------------|-----------------| +| BLS signatures (elliptic curve) | Quantum-breakable (Shor's algorithm) | Hash-based signatures | +| KZG polynomial commitments | Elliptic curve, quantum-vulnerable | Hash-based commitments | +| Poseidon hash function | Under active cryptanalysis | Poseidon2 + ongoing bounty program | + +### Key Proof Systems + +- **SNARKs (Succinct Non-Interactive Arguments of Knowledge)**: Short proofs verifiable quickly. Used for both execution proving and consensus signature aggregation. +- **STARKs / FRI / WHIR**: Transparent (no trusted setup), post-quantum secure proof systems. WHIR is an improvement over FRI used in Plonky3 and similar frameworks. +- **Binius**: A SNARK system operating over binary fields, highly efficient for hash-based computations. +- **Formal Verification with Lean 4**: The mathematical proof assistant "Lean" (different from Lean Ethereum — coincidental naming!) is being used to formally verify the security of FRI, WHIR, and other proof systems used in the zkEVM. + +--- + +## State Proving in Context: The Full Stack + +``` +┌─────────────────────────────────────────────┐ +│ Lean Ethereum Stack │ +├─────────────────────────────────────────────┤ +│ CONSENSUS (Lean Consensus) │ +│ • Hash-based PQ signatures via SNARKs │ +│ • 3-Slot Finality (3SF) │ +│ • Reduced stake (1 ETH), APS │ +├─────────────────────────────────────────────┤ +│ DATA (Lean Data) │ +│ • Blobs 2.0 / PeerDAS │ +│ • Data Availability Sampling │ +├─────────────────────────────────────────────┤ +│ EXECUTION (Lean Execution / State Proving) │ +│ • L1 zkEVM (Type 1) │ +│ • Real-time block proving (<12s) │ +│ • Prover markets & incentives │ +│ • Native rollups (long-term) │ +└─────────────────────────────────────────────┘ +``` + +--- + +## Key Links & Resources + +### Primary Sources +- **Lean Ethereum EF Blog Post** (Jul 31, 2025): https://blog.ethereum.org/2025/07/31/lean-ethereum +- **Lean Consensus Roadmap**: https://leanroadmap.org +- **Shipping an L1 zkEVM #1: Realtime Proving** (Jul 10, 2025): https://blog.ethereum.org/2025/07/10/realtime-proving +- **EF zkEVM Portal**: https://zkevm.ethereum.foundation +- **L1-zkEVM Roadmap 2026** (Ethereum Magicians): https://ethereum-magicians.org/t/l1-zkevm-roadmap-2026-integrating-zkevm-proofs-into-ethereums-core-protocol/27595 +- **ethproofs.org** (benchmark tracker): https://ethproofs.org + +### Audio / Video +- **Episode 391 — Introduction to Lean Ethereum with Justin Drake** (Bankless / referenced podcast) +- **Beam Chain @ Devcon 7 Bangkok** (Nov 2024) — Justin Drake's original presentation + +### Research Papers +- *A Simple Single Slot Finality Protocol for Ethereum* (Feb 2023) +- *3-Slot Finality: SSF Is Not About Single Slot* (Nov 2024) +- *Hash-Based Multi-Signatures for Post-Quantum Ethereum* (Jan 2025) +- *Integrating 3SF with ePBS, FOCIL, and PeerDAS* (Aug 2025) +- *WHIR* — Sep 2024 (fast polynomial commitment scheme) + +--- + +## Open Research Questions + +1. **Prover decentralization**: Who generates proofs and how to prevent centralization around large GPU clusters? +2. **Prover incentives**: What is the right economic model for prover markets? +3. **Handling unproable blocks**: What happens when a block cannot be proved in time (e.g., pathological input)? +4. **Security during transition**: How to safely migrate from re-execution to proof-based verification without introducing new attack surfaces? +5. **Poseidon security**: The EF has an active bounty program and ongoing cryptanalysis of the Poseidon hash function used inside SNARK circuits. +6. **Native rollups**: Long-term, how can L2 state transitions be verified natively by L1 validators? + +--- + From 430a3eb1417c34dbbc0eaa453ab67084fcb833ed Mon Sep 17 00:00:00 2001 From: Ifeoluwa Date: Tue, 24 Feb 2026 12:02:22 +0100 Subject: [PATCH 2/4] update to fix the errors --- .../lean-ethereum-and-state-proving.md | 28 +++++++++---------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/docs/wiki/research/lean-ethereum-and-state-proving.md b/docs/wiki/research/lean-ethereum-and-state-proving.md index 38db2142..76728374 100644 --- a/docs/wiki/research/lean-ethereum-and-state-proving.md +++ b/docs/wiki/research/lean-ethereum-and-state-proving.md @@ -2,12 +2,12 @@ ## Overview -**Lean Ethereum** is a long-term technical roadmap for the Ethereum base layer proposed by Ethereum Foundation researcher Justin Drake and published on the EF blog on July 31, 2025. It reframes Ethereum's development priorities around two strategic imperatives: +**Lean Ethereum** is a long-term technical roadmap for the Ethereum base layer proposed by Ethereum Foundation researcher Justin Drake and published on the EF blog on July 31, 2025. It reshapes Ethereum's development priorities around two strategic imperatives: - **Fort Mode** — Hardening security to survive nation-state threats and quantum computing advances. - **Beast Mode** — Achieving extreme performance (targeting 10,000 TPS on L1, 1M+ TPS on L2) without sacrificing decentralization. -The roadmap restructures all three protocol sublayers — **Consensus**, **Data**, and **Execution** — around a unified cryptographic primitive: **hash-based SNARKs**. +The roadmap restructures all three protocol sub-layers — **Consensus**, **Data**, and **Execution** — around a unified cryptographic primitive: **hash-based SNARKs**. > Note: Lean Ethereum evolved from the "Beam Chain" proposal that Justin Drake introduced at Devcon 7 in Bangkok (November 2024). Beam Chain specifically referred to a redesign of the consensus layer, now called **Lean Consensus**. The "Lean Ethereum" umbrella was introduced in mid-2025 to encompass all three layers. @@ -26,7 +26,7 @@ A complete redesign of Ethereum's consensus (Beacon Chain) layer. Key goals: - **Rainbow Staking**: A novel staking mechanism designed to further enhance decentralization. **Key resources:** -- Lean Consensus Roadmap: [leanroadmap.org](https://leanroadmap.org) +- Lean Consensus Roadmap: [leanroadmap.org](https://leanroadmap.org) - 3-Slot Finality paper (Feb 2023) - Post-Quantum signature aggregation research series (2025) @@ -103,15 +103,15 @@ Ethereum blocks can contain complex, varied computations. A zkVM must prove ever Real-time proving was achieved in 2025 across multiple competing zkVM teams, with multiple projects independently reaching the milestone. As of late 2025: -- **Pico Prism** proved 99.6% of Ethereum blocks in real-time using 64 RTX 5090 GPUs with an average time of 6.9 seconds. +- **Pico Prism** proved 99.6% of Ethereum blocks in real-time using 64 RTX 5090 GPUs with an average time of 6.9 seconds. - **SP1 Hypercube** (Succinct) proved 93% of 10,000 mainnet blocks in real-time on a cluster of 200 GPUs. -- Teams including Risc0, OpenVM, Brevis, Snarkify, ZisK, ZKM, and ZKsync all achieved or approached the milestone. +- Teams including Risc0, OpenVM, Brevis, Snarkify, ZisK, ZKM, and ZKsync all achieved or approached the milestone. -**ethproofs.org** was launched by the EF to benchmark and compare zkVM performance on real Ethereum blocks. +**ethproofs.org** was launched by the EF to benchmark and compare zkVM performance on real Ethereum blocks. ### The Proving Pipeline -The EF blog post "Shipping an L1 zkEVM #1: Realtime Proving" (July 2025) laid out the phased approach: +The EF blog post "Shipping an L1 zkEVM #1: Real-Time Proving" (July 2025) laid out the phased approach: 1. **Phase 1 — Off-chain proof verification**: Validators optionally run clients that verify proofs generated by zkVMs instead of re-executing. This requires a "pipelining" mechanism (targeted for the Glamsterdam upgrade) to decouple block verification from immediate execution, giving provers more time within a slot. @@ -121,7 +121,7 @@ The EF blog post "Shipping an L1 zkEVM #1: Realtime Proving" (July 2025) laid ou ### The L1 zkEVM 2026 Roadmap -Published by the EF's zkEVM team (via Ethereum Magicians, early 2026), the concrete 2026 milestones include: +Published by the Ethereum Foundation's zkEVM team (via Ethereum Magicians, early 2026), the concrete 2026 milestones include: - Standardizing interfaces between execution and consensus layers for proof requests and verification. - Researching prover markets, censorship resistance, and economic incentives for provers. @@ -144,8 +144,8 @@ Lean Ethereum's design is unified around **hash-based cryptography** for both qu ### Key Proof Systems - **SNARKs (Succinct Non-Interactive Arguments of Knowledge)**: Short proofs verifiable quickly. Used for both execution proving and consensus signature aggregation. -- **STARKs / FRI / WHIR**: Transparent (no trusted setup), post-quantum secure proof systems. WHIR is an improvement over FRI used in Plonky3 and similar frameworks. -- **Binius**: A SNARK system operating over binary fields, highly efficient for hash-based computations. +- **STARKs / FRI / WHIR**: Transparent (no trusted setup), post-quantum secure proof systems. WHIR is an improvement over FRI used in Plonky3 and similar frameworks. +- **Binius**: A SNARK system operating over binary fields, highly efficient for hash-based computations. - **Formal Verification with Lean 4**: The mathematical proof assistant "Lean" (different from Lean Ethereum — coincidental naming!) is being used to formally verify the security of FRI, WHIR, and other proof systems used in the zkEVM. --- @@ -179,11 +179,11 @@ Lean Ethereum's design is unified around **hash-based cryptography** for both qu ### Primary Sources - **Lean Ethereum EF Blog Post** (Jul 31, 2025): https://blog.ethereum.org/2025/07/31/lean-ethereum -- **Lean Consensus Roadmap**: https://leanroadmap.org -- **Shipping an L1 zkEVM #1: Realtime Proving** (Jul 10, 2025): https://blog.ethereum.org/2025/07/10/realtime-proving +- **Lean Consensus Roadmap**: https://leanroadmap.org +- **Shipping an L1 zkEVM #1: Real-Time Proving** (Jul 10, 2025): https://blog.ethereum.org/2025/07/10/realtime-proving - **EF zkEVM Portal**: https://zkevm.ethereum.foundation - **L1-zkEVM Roadmap 2026** (Ethereum Magicians): https://ethereum-magicians.org/t/l1-zkevm-roadmap-2026-integrating-zkevm-proofs-into-ethereums-core-protocol/27595 -- **ethproofs.org** (benchmark tracker): https://ethproofs.org +- **ethproofs.org** (benchmark tracker): https://ethproofs.org ### Audio / Video - **Episode 391 — Introduction to Lean Ethereum with Justin Drake** (Bankless / referenced podcast) @@ -202,7 +202,7 @@ Lean Ethereum's design is unified around **hash-based cryptography** for both qu 1. **Prover decentralization**: Who generates proofs and how to prevent centralization around large GPU clusters? 2. **Prover incentives**: What is the right economic model for prover markets? -3. **Handling unproable blocks**: What happens when a block cannot be proved in time (e.g., pathological input)? +3. **Handling unprovable blocks**: What happens when a block cannot be proved in time (e.g., pathological input)? 4. **Security during transition**: How to safely migrate from re-execution to proof-based verification without introducing new attack surfaces? 5. **Poseidon security**: The EF has an active bounty program and ongoing cryptanalysis of the Poseidon hash function used inside SNARK circuits. 6. **Native rollups**: Long-term, how can L2 state transitions be verified natively by L1 validators? From 4564635318db888d247b86003e886f5dbcae3266 Mon Sep 17 00:00:00 2001 From: Ifeoluwa Date: Tue, 24 Feb 2026 12:31:53 +0100 Subject: [PATCH 3/4] chore: remove unintended files from branch --- docs/_sidebar.md | 37 +++++++++++-- docs/eps/archive.md | 106 ------------------------------------- docs/eps/epstownhall25.ics | 19 +++++++ docs/eps/intro.md | 74 +++++++++++++++++++++++--- docs/eps/schedule.md | 76 ++++++++++++++++++++++++++ docs/readme.md | 8 +-- wordlist.txt | 9 +++- 7 files changed, 208 insertions(+), 121 deletions(-) delete mode 100644 docs/eps/archive.md create mode 100644 docs/eps/epstownhall25.ics create mode 100644 docs/eps/schedule.md diff --git a/docs/_sidebar.md b/docs/_sidebar.md index beebcb94..50a9d20a 100644 --- a/docs/_sidebar.md +++ b/docs/_sidebar.md @@ -1,8 +1,39 @@ - [Home](readme.md) -- [Contributing](contributing.md) - **Study Group** -- [Join the studies](/eps/intro.md) -- [Study Group archive](/eps/archive.md) +- [Start here](/eps/intro.md) +- [Study Group content](/eps/schedule.md) + - **Introduction** + - [Prepare for studies](/eps/week0.md) + - [Protocol intro and overview](/eps/week1.md) + - [CL intro](/eps/week3.md) + - [EL intro](/eps/week2.md) + - [Using clients](/eps/nodes_workshop.md) + - [CL/EL specs](/eps/week6-dev.md) + - [Testing and security](/eps/week4.md) + - [Local prototyping](/eps/week9-dev.md) + - [Research overview](/eps/week5.md) + - **Consensus Layer** + - [Gasper](/eps/day16.md) + - [CL client architecture](/eps/week8-dev.md) + - [CL Data structures](/eps/day22.md) + - [libp2p](/eps/day19.md) + - [Validator Client](/eps/day20.md) + - **Execution Layer** + - [EL client architecture](/eps/week7-dev.md) + - [EVM](/eps/day17.md) + - [EL Data](/eps/day23.md) + - [devp2p](/eps/day18.md) + - [Engine API](/eps/day21.md) + - [EL precompiles](/eps/week10-dev.md) + - **Research** + - [Upcoming upgrades](/eps/day24.md) + - [Sharding and DAS](/eps/week6-research.md) + - [Verkle trees](/eps/week7-research.md) + - [MEV and censorship](/eps/week8-research.md) + - [Purge and Portal Network](/eps/week9-research.md) + - [SSF and PoS Upgrades](/eps/week10-research.md) + +- [Contributing](contributing.md) - **Protocol Wiki** - The Protocol - [Prehistory](/wiki/protocol/prehistory.md) diff --git a/docs/eps/archive.md b/docs/eps/archive.md deleted file mode 100644 index 6b934af0..00000000 --- a/docs/eps/archive.md +++ /dev/null @@ -1,106 +0,0 @@ - - - **Introduction** - - [Prepare for studies](/eps/week0.md) - - [Protocol intro and overview](/eps/week1.md) - - [CL intro](/eps/week3.md) - - [EL intro](/eps/week2.md) - - [Using clients](/eps/nodes_workshop.md) - - [CL/EL specs](/eps/week6-dev.md) - - [Testing and security](/eps/week4.md) - - [Local prototyping](/eps/week9-dev.md) - - [Research overview](/eps/week5.md) - - **Consensus Layer** - - [Gasper](/eps/day16.md) - - [CL client architecture](/eps/week8-dev.md) - - [CL Data structures](/eps/day22.md) - - [libp2p](/eps/day19.md) - - [Validator Client](/eps/day20.md) - - **Execution Layer** - - [EL client architecture](/eps/week7-dev.md) - - [EVM](/eps/day17.md) - - [EL Data](/eps/day23.md) - - [devp2p](/eps/day18.md) - - [Engine API](/eps/day21.md) - - [EL precompiles](/eps/week10-dev.md) - - **Research** - - [Upcoming upgrades](/eps/day24.md) - - [Sharding and DAS](/eps/week6-research.md) - - [Verkle trees](/eps/week7-research.md) - - [MEV and censorship](/eps/week8-research.md) - - [Purge and Portal Network](/eps/week9-research.md) - - [SSF and PoS Upgrades](/eps/week10-research.md) - - - - -The study group was originally run as a 10-week study program with 16 sessions in total. The original sessions are divided into 3 areas, each covering one part of the Ethereum protocol curriculum. - -Watch each lecture sequentially, study supplied materials and exercises. We recommend making notes and in case of any extra information, explanation needed, come to ask to Office Hours or a discord channel. - -## Schedule - -Each session is created by a core developer or researcher, comes with reading materials to get you familiar with the topic context and some also include exercises to strengthen and practice your understanding. More resources on each topic can be found in the wiki section and if they are any missing, contribute to add them. - -During first 2 weeks, participants watch previous videos and study existing materials for the given day in their own time. Every day at _3PM UTC we will hold a daily office hours running for 2 hours_ where everyone can discuss their learnings, ask questions, exchange knowledge, etc. Join at the [Office Hours call link](https://meet.ethereum.org/eps-office-hours). - -#### Protocol introduction - -The first part of the Study Group is an introduction to the protocol, overview of its parts and development process. - -| Topic | Speaker | -| --------------------------------------------------- | -------------------------------------------------------------------------------------- | -| [Intro to EPS and Ethereum protocol](/eps/week1.md) | [Mario Havel](https://github.com/taxmeifyoucan) | -| [Consensus layer intro](/eps/week3.md) | [Alex Stokes](https://github.com/ralexstokes) | -| [Execution layer intro](/eps/week2.md) | [Lightclient](https://github.com/lightclient) | -| [Using clients, nodes](/eps/nodes_workshop.md) | [Mario](https://github.com/taxmeifyoucan) | -| [Consensus and Execution specs](/eps/week6-dev.md) | [Hsiao-Wei Wang](https://github.com/hwwhww), [Sam Wilson](https://github.com/SamWilsn) | -| [Testing and security](/eps/week4.md) | [Mario Vega](https://github.com/marioevz) | -| [Local prototyping](/eps/week9-dev.md) | [Parithosh](https://github.com/parithosh) | -| [Roadmap and research overview](/eps/week5.md) | [Domothy](https://github.com/domothyb) | - -#### Consensus layer - -The consensus layer track covers all parts of the CL, including overview of the proof-of-stake implementation, networking and data. - -| Topic | Speaker | -| -------------------------------------------------- | ----------------------------------------------- | -| [Gasper](/eps/day16.md) | [Ben Edgington](https://github.com/benjaminion) | -| [Consensus client architecture](/eps/week8-dev.md) | [Paul Harris](https://github.com/rolfyone) | -| [CL Data structures](/eps/day22.md) | [Michael](https://github.com/michaelsproul/) | -| [libp2p](/eps/day19.md) | [DappLion](https://github.com/dapplion) | -| [Validator Client](/eps/day20.md) | [James](https://github.com/james-prysm) | - - -### Execution layer - -Every part of the execution layer, the original Ethereum itself. - -| Topic | Speaker | -| -------------------------------------------------- | ------------------------------------------------------------------------- | -| [Execution client architecture](/eps/week7-dev.md) | [Dragan Pilipovic](https://github.com/dragan2234) | -| [EVM](/eps/day17.md) | [Pawel Bylica](https://github.com/chfast) | -| [EL Data](/eps/day23.md) | [Gary](https://github.com/garyschulte), [Karim](https://github.com/matkt) | -| [devp2p](/eps/day18.md) | [Felix Lange](https://github.com/fjl) | -| [Engine API](/eps/day21.md) | [Mikhail](https://github.com/mkalinin) | -| [EL precompiles](/eps/week10-dev.md) | [Danno Ferrin](https://github.com/shemnon) | - - -### Research - -The research track provides a technical explanation of active area of research, covering major important items from most [Ethereum roadmap](https://epf.wiki/#/wiki/research/roadmap) tracks. - -| Topic | Speaker | -| -------------------------------------------------- | -------------------------------------------------- | -| [Upcoming upgrades overview](/eps/day24.md) | [Marius](https://github.com/MariusVanDerWijden) | -| [Sharding and DAS](/eps/week6-research.md) | [Dankrad Feist](https://github.com/dankrad) | -| [Verkle trees](/eps/week7-research.md) | [Josh Rudolf](https://github.com/jrudolf) | -| [MEV and censorship](/eps/week8-research.md) | [Barnabe Monnot](https://github.com/barnabemonnot) | -| [Purge and Portal Network](/eps/week9-research.md) | [Piper Merriam](https://github.com/pipermerriam) | -| [SSF and PoS Upgrades](/eps/week10-research.md) | [Francesco D'Amato](https://github.com/fradamt) | - - -### Streams and recordings - -Talks and calls are announced week in advance based on the schedule above. Recordings of all talks can be found on [Youtube](https://www.youtube.com/@ethprotocolfellows) or [StreamEth](https://streameth.org/archive?organization=ethereum_protocol_fellowship) archive. - -Apart from weekly lectures, there are less regular, ad-hoc hangout calls for informal chats and calls for wiki contributors working the content. Join the Discord group to get notified about all of these events. diff --git a/docs/eps/epstownhall25.ics b/docs/eps/epstownhall25.ics new file mode 100644 index 00000000..d630cf4c --- /dev/null +++ b/docs/eps/epstownhall25.ics @@ -0,0 +1,19 @@ +BEGIN:VCALENDAR +VERSION:2.0 +PRODID:-//ical.marudot.com//iCal Event Maker +CALSCALE:GREGORIAN +BEGIN:VEVENT +DTSTAMP:20250206T151639Z +UID:1738854242598-64367@ical.marudot.com +DTSTART:20250212T150000Z +DTEND:20250212T160000Z +SUMMARY:Town Hall - Ethereum Protocol Studies +DESCRIPTION:An information session and Q&A about the 2025 Ethereum Protocol Studies group. +LOCATION:https://meet.ethereum.org/eps-town-hall-25 +BEGIN:VALARM +ACTION:DISPLAY +DESCRIPTION:Town Hall - Ethereum Protocol Studies +TRIGGER:-PT15M +END:VALARM +END:VEVENT +END:VCALENDAR \ No newline at end of file diff --git a/docs/eps/intro.md b/docs/eps/intro.md index a7e93eec..f14131db 100644 --- a/docs/eps/intro.md +++ b/docs/eps/intro.md @@ -6,23 +6,83 @@ The protocol evolves and grows quickly, it's an always-changing infinite garden. Originally started in 2024, the study group is a participatory educational program that aims to improve core protocol education by introducing a curriculum focused on all parts of the Ethereum stack, building a wiki knowledge base and creating a community focused on learning about the protocol. -> The Study Group is active for 2 months starting February 23rd 2026, meeting live and creating new content. Join our [community chat](https://discord.gg/8RPnPGEQtJ) and start your studies journey +> The Study Group is active for 2 months a year, meeting live and creating new content. But meanwhile, you can use all existing content for your own studies and join our [Discord server](https://discord.gg/8RPnPGEQtJ) to chat about it ![Ethereum Protocol Studies](https://raw.githubusercontent.com/eth-protocol-fellows/protocol-studies/376d1fca6907d2796da0a7876703b525ef528727/docs/images/EPS2-1080.jpg) -## Learn and participate +## Program Structure -The study group content is structured into 3 modules. Introduction with high level overview of the protocol, development process and research. Then it dives deeper into each part of the protocol in consensus and execution layer. +The study group content is structured into 4 tracks. Introduction with high level overview of the protocol, development process and research. Then it dives deeper into each part of the protocol in consensus, execution and research. ### Study Group content -**The study group curriculum is available at https://study.epf.wiki** +Each session is created by a core developer or researcher, comes with reading materials to get you familiar with the topic context and some also include exercises to strengthen and practice your understanding. More resources on each topic can be found in the wiki section and if they are any missing, contribute to add them. -This is a learning platform that contains interactive sessions, excercises, quizes and more resources to get you started learning about the protocol in depth. +> We recommend watching videos from the study group using faster playback speed, 1.25 or 1.5x to save some time -The original study group content that was present here is still available under [archive.md]. +#### Protocol introduction -### Program structure +The first part of the Study Group is an introduction to the protocol, overview of its parts and development process. + +| Topic | Speaker | +| --------------------------------------------------- | -------------------------------------------------------------------------------------- | +| [Intro to EPS and Ethereum protocol](/eps/week1.md) | [Mario Havel](https://github.com/taxmeifyoucan) | +| [Consensus layer intro](/eps/week3.md) | [Alex Stokes](https://github.com/ralexstokes) | +| [Execution layer intro](/eps/week2.md) | [Lightclient](https://github.com/lightclient) | +| [Using clients, nodes](/eps/nodes_workshop.md) | [Mario](https://github.com/taxmeifyoucan) | +| [Consensus and Execution specs](/eps/week6-dev.md) | [Hsiao-Wei Wang](https://github.com/hwwhww), [Sam Wilson](https://github.com/SamWilsn) | +| [Testing and security](/eps/week4.md) | [Mario Vega](https://github.com/marioevz) | +| [Local prototyping](/eps/week9-dev.md) | [Parithosh](https://github.com/parithosh) | +| [Roadmap and research overview](/eps/week5.md) | [Domothy](https://github.com/domothyb) | + +#### Consensus layer + +The consensus layer track covers all parts of the CL, including overview of the proof-of-stake implementation, networking and data. + +| Topic | Speaker | +| -------------------------------------------------- | ----------------------------------------------- | +| [Gasper](/eps/day16.md) | [Ben Edgington](https://github.com/benjaminion) | +| [Consensus client architecture](/eps/week8-dev.md) | [Paul Harris](https://github.com/rolfyone) | +| [CL Data structures](/eps/day22.md) | [Michael](https://github.com/michaelsproul/) | +| [libp2p](/eps/day19.md) | [DappLion](https://github.com/dapplion) | +| [Validator Client](/eps/day20.md) | [James](https://github.com/james-prysm) | + + +### Execution layer + +Every part of the execution layer, the original Ethereum itself. + +| Topic | Speaker | +| -------------------------------------------------- | ------------------------------------------------------------------------- | +| [Execution client architecture](/eps/week7-dev.md) | [Dragan Pilipovic](https://github.com/dragan2234) | +| [EVM](/eps/day17.md) | [Pawel Bylica](https://github.com/chfast) | +| [EL Data](/eps/day23.md) | [Gary](https://github.com/garyschulte), [Karim](https://github.com/matkt) | +| [devp2p](/eps/day18.md) | [Felix Lange](https://github.com/fjl) | +| [Engine API](/eps/day21.md) | [Mikhail](https://github.com/mkalinin) | +| [EL precompiles](/eps/week10-dev.md) | [Danno Ferrin](https://github.com/shemnon) | + + +### Research + +The research track provides a technical explanation of active area of research, covering major important items from most [Ethereum roadmap](https://epf.wiki/#/wiki/research/roadmap) tracks. + +| Topic | Speaker | +| -------------------------------------------------- | -------------------------------------------------- | +| [Upcoming upgrades overview](/eps/day24.md) | [Marius](https://github.com/MariusVanDerWijden) | +| [Sharding and DAS](/eps/week6-research.md) | [Dankrad Feist](https://github.com/dankrad) | +| [Verkle trees](/eps/week7-research.md) | [Josh Rudolf](https://github.com/jrudolf) | +| [MEV and censorship](/eps/week8-research.md) | [Barnabe Monnot](https://github.com/barnabemonnot) | +| [Purge and Portal Network](/eps/week9-research.md) | [Piper Merriam](https://github.com/pipermerriam) | +| [SSF and PoS Upgrades](/eps/week10-research.md) | [Francesco D'Amato](https://github.com/fradamt) | + + +### Streams and recordings + +Talks and calls are announced week in advance based on the schedule above. Recordings of all talks can be found on [Youtube](https://www.youtube.com/@ethprotocolfellows) or [StreamEth](https://streameth.org/archive?organization=ethereum_protocol_fellowship) archive. + +Apart from weekly lectures, there are less regular, ad-hoc hangout calls for informal chats and calls for wiki contributors working the content. Join the Discord group to get notified about all of these events. + +## Participate The study group is an open and permissionless, and it is up to each participant as to how they want to approach it. Whether you want to learn as much as possible, focus only on certain topics or share your knowledge with others, you are welcomed. diff --git a/docs/eps/schedule.md b/docs/eps/schedule.md new file mode 100644 index 00000000..4b7c9a92 --- /dev/null +++ b/docs/eps/schedule.md @@ -0,0 +1,76 @@ +# Study Group Schedule + +The study group was originally run as a 10-week study program with 16 sessions in total. The original sessions are divided into 3 areas, each covering one part of the Ethereum protocol curriculum. + +Watch each lecture sequentially, study supplied materials and exercises. We recommend making notes and in case of any extra information, explanation needed, come to ask to Office Hours or a discord channel. + +## Schedule + +Each session is created by a core developer or researcher, comes with reading materials to get you familiar with the topic context and some also include exercises to strengthen and practice your understanding. More resources on each topic can be found in the wiki section and if they are any missing, contribute to add them. + +During first 2 weeks, participants watch previous videos and study existing materials for the given day in their own time. Every day at _3PM UTC we will hold a daily office hours running for 2 hours_ where everyone can discuss their learnings, ask questions, exchange knowledge, etc. Join at the [Office Hours call link](https://meet.ethereum.org/eps-office-hours). + +> We recommend watching videos from the study group using faster playback speed, 1.25 or 1.5x to save some time + +#### Week 1 + +The first week will cover the first five weeks of previous Study Group content. The first day provides an introduction to the Study Group and the protocol itself. Then, we will dive into each part of the protocol. On Wednesday, the node workshop will also be held live during office hours. + +| Day | Topic | Speaker | +| ------------- | --------------------------------------------------- | ----------------------------------------------- | +| Day 1, Feb 17 | [Intro to EPS and Ethereum protocol](/eps/week1.md) | [Mario Havel](https://github.com/taxmeifyoucan) | +| Day 2, Feb 18 | [Consensus layer](/eps/week3.md) | [Alex Stokes](https://github.com/ralexstokes) | +| Day 3, Feb 19 | [Execution Layer](/eps/week2.md) | [Lightclient](https://github.com/lightclient) | +| Day 3, Feb 19 | [Using clients, nodes](/eps/nodes_workshop.md) | [Mario](https://github.com/taxmeifyoucan) | +| Day 4, Feb 20 | [Testing and security](/eps/week4.md) | [Mario Vega](https://github.com/marioevz) | +| Day 5, Feb 21 | [Roadmap and research](/eps/week5.md) | [Domothy](https://github.com/domothyb) | + +#### Week 2 + +The second week of the study group provides an overview of developer experience in Ethereum protocol. It covers the development track of the previous study group and provides an insight into various parts of the development process - from specification, CL/EL client architecture to hands on devops and testing. + +| Day, Date | Topic | Speaker | +| -------------- | -------------------------------------------------- | -------------------------------------------------------------------------------------- | +| Day 6, Feb 24 | [Consensus and Execution specs](/eps/week6-dev.md) | [Hsiao-Wei Wang](https://github.com/hwwhww), [Sam Wilson](https://github.com/SamWilsn) | +| Day 7, Feb 25 | [Execution client architecture](/eps/week7-dev.md) | [Dragan Rakita](https://github.com/rakitadragan) | +| Day 8, Feb 26 | [Consensus client architecture](/eps/week8-dev.md) | [Paul Harris](https://github.com/rolfyone) | +| Day 9, Feb 27 | [Devops and testing](/eps/week9-dev.md) | [Parithosh](https://github.com/parithosh) | +| Day 10, Feb 28 | [EL precompiles](/eps/week10-dev.md) | [Danno Ferrin](https://github.com/shemnon) | + + +### Week 3 + +Third week covers the research track and it's the last week using the original study group materials. Each lecture provides a technical explanation of an active area of research, covering major important items from most [Ethereum roadmap](https://epf.wiki/#/wiki/research/roadmap) tracks. + +| Day, Date | Topic | Speaker | +| ------------- | -------------------------------------------------- | -------------------------------------------------- | +| Day 11, Mar 3 | [Sharding and DAS](/eps/week6-research.md) | [Dankrad Feist](https://github.com/dankrad) | +| Day 12, Mar 4 | [Verkle trees](/eps/week7-research.md) | [Josh Rudolf](https://github.com/jrudolf) | +| Day 13, Mar 5 | [MEV and censorship](/eps/week8-research.md) | [Barnabe Monnot](https://github.com/barnabemonnot) | +| Day 14, Mar 6 | [Purge and Portal Network](/eps/week9-research.md) | [Piper Merriam](https://github.com/pipermerriam) | +| Day 15, Mar 7 | [SSF and PoS Upgrades](/eps/week10-research.md) | [Francesco D'Amato](https://github.com/fradamt) | + +### Week 4 + +Starting week 4, we are entering the main part of the study group that dives deeper into each part of the protocol. This week starts with talks diving into the core function of each layer. + +| Day, Date | Topic | Speaker | +| ------------- | -------------------------------- | -------------------------------------------------- | +| Day 16, Mar 10 | [Gasper](/eps/day16.md) | [Ben Edgington](https://github.com/benjaminion) | +| Day 17, Mar 12 | [EVM](/eps/day17.md) | [Pawel Bylica](https://github.com/chfast) | + +### Week 5 + +Week 5 continues deeper dive to each part of the protocol with lectures on networking. + +| Day, Date | Topic | Speaker | +| ------------- | -------------------------------- | -------------------------------------------------- | +| Day 16, Mar 17 | [devp2p](/eps/day18.md) | [Felix Lange](https://github.com/fjl) | +| Day 17, Mar 19 | [libp2p](/eps/day19.md) | [DappLion](https://github.com/dappplion) | + +### Week 6 + +| Day, Date | Topic | Speaker | +| ------------- | -------------------------------- | -------------------------------------------------- | +| Day 16, Mar 24 | [Validator Client](/eps/day20.md) | [James](https://github.com/james-prysm) | +| Day 17, Mar 31 | [Engine API](/eps/day21.md) | [Mikhail](https://github.com/mkalinin) | diff --git a/docs/readme.md b/docs/readme.md index 7bba655d..5dd962ee 100644 --- a/docs/readme.md +++ b/docs/readme.md @@ -4,9 +4,9 @@ The EPF Wiki is a collection of technical resources about the Ethereum protocol. ## Protocol Study Group -Ethereum Protocol Study Group (EPS) is an open study program for anyone interested in learning about internals of the protocol. The study group resources are available as self study curriculum but there is also live Study Group organized annualy between February-April. Following blog.ethereum.org for announcements to join a community of students. +Ethereum Protocol Fellowship Study Group (EPFsg) is an open study program for anyone interested in learning about internals of the protocol. The study group resources are available as self study curriculum but there is also live Study Group organized annualy between February-April. Following blog.ethereum.org for announcements to join a community of students. -**Study Group 2026** is starting on February 23rd with 8 weeks of content. Learn with us at [study.epf.wiki](https://study.epf.wiki) +**[Start your studies](/eps/intro.md) by diving into providing resources** and get ready for live study group in 2026! > The study group is not just a list of resources but a community of people maintaining them and learning about the core protocol. **Join the community in our [Discord server](https://discord.gg/8RPnPGEQtJ)**. @@ -19,8 +19,8 @@ Protocol Wiki is a technical documentation of the main parts of Ethereum core de > ## Protocol Fellowship - -[Ethereum Protocol Fellowship](/wiki/epf) (EPF) is a program for developers and researchers deeply interested in working on the protocol. It's an opportunity to work directly with client teams on their and contribute by building projects with larger scope. It's 5 month program, normally organized annualy June-November. Stay tuned for announcement for applications. +[ +Ethereum Protocol Fellowship](/wiki/epf) (EPF) is a program for developers and researchers deeply interested in working on the protocol. It's an opportunity to work directly with client teams on their and contribute by building projects with larger scope. It's 5 month program, normally organized annualy June-November. Stay tuned for announcement for applications. ![](https://raw.githubusercontent.com/eth-protocol-fellows/protocol-studies/wiki-pages/docs/images/epfsg_hero.jpg) diff --git a/wordlist.txt b/wordlist.txt index 12e9d041..cb848608 100644 --- a/wordlist.txt +++ b/wordlist.txt @@ -1028,4 +1028,11 @@ eas alt asm bn -sys \ No newline at end of file +sysethproofs +leanroadmap +Plonky +Binius +Brevis +ZisK +ZKM +unprovable From 52d01a87eb6f1fb4d78415ff5c2f4a6690408f2e Mon Sep 17 00:00:00 2001 From: Ifeoluwa Date: Tue, 24 Feb 2026 12:53:56 +0100 Subject: [PATCH 4/4] chore: fix wordlist and restore unintended files --- wordlist.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/wordlist.txt b/wordlist.txt index cb848608..67600a1d 100644 --- a/wordlist.txt +++ b/wordlist.txt @@ -1036,3 +1036,4 @@ Brevis ZisK ZKM unprovable +ethproofs