Research & Development

A few months ago, we announced a renewed focus of Protocol on three strategic initiatives: Scale L1, Scale blobs, Improve UX. Following previous updates on Scale L1 and Scale blobs, this note relates to our “Improve UX” track, and its mission: Seamless, secure and permissionless experience across the Ethereum ecosystem, for individuals and institutions. We see interoperability, and related projects presented in this note, as the highest leverage opportunity within the broader UX domain over the next 6-12 months, in our position as a public, core Ethereum R\&D group. The near-term strategy focuses on areas we believe will continue to be fundamental components of interop: Intent-based architecture and general message-passing. For both, our aim is to focus on clear, measurable protocol metrics to drive down latency and cost,

Following up from Protocol Update 001, we’d like to introduce our approach to blob scaling. The L1 serves as a robust foundation for L2 systems to scale Ethereum, and a necessary component of secure L2 solutions is data availability provided by the L1. Data availability ensures that updates L2s make back to the L1 can be verified by anyone. Blobs are the unit of data availability in the protocol today, so scaling the blob count per block is a key requirement to usher in a wave of L2 adoption for use cases like real-time payments, DeFi, social media, gaming, and AI/agentic applications. Our work is structured as a series of incremental changes to Ethereum’s blob architecture. To accelerate our rate of scaling, we are expanding from

Since January 2019, the Ethereum Foundation has held a tradition of engaging directly with the community through our "Ask Us Anything" (AMA) series on Reddit, occurring roughly every six months. These AMAs, previously hosted by the EF Research team, have provided a forum for deep dives into the protocol's evolving landscape, direct Q\&A with core contributors, and a transparent look into the ongoing work shaping Ethereum. We are excited to announce the continuation of this tradition. The next AMA will be hosted by the EF Protocol cluster teams, reflecting the evolution of our organizational structure. While "EF Research" accurately described our focus on foundational research, "EF Protocol" encompasses both the cutting-edge research that explores Ethereum's future as well as the critical development efforts that bring these

In June, we introduced Protocol, reorganizing the Ethereum Foundation’s research & development teams to better align on our current strategic goals, Scale L1, Scale Blobs, and Improve UX without compromising on our commitment to Ethereum's security and hardness. Over the coming weeks, we’ll publish updates on each work stream, covering their ongoing progress, new initiatives, open questions and opportunities for collaboration. We start today with Scale L1 --- expect follow-ups about Scale Blobs and Improve UX soon!

Yesterday Ethereum turned 10. Today, lean Ethereum is unveiled as a vision—and personal mission—for the next 10 years. We stand at the dawn of a new era. Millions of TPS. Quantum adversaries. How does Ethereum marry extreme performance with uncompromising security and decentralization? TLDR: next-generation cryptography is central to winning both offense and defense. Disclaimer: This is a Drake take™ aimed at a broad audience. A technical deep dive into hash-based post-quantum signatures and SNARKs will follow. A healthy diversity of views across Protocol, the EF, and the broader Ethereum community is expected and welcome. It strengthens us.

Ethereum’s weekly All Core Developer calls are a lot to keep up with, so this "Checkpoint" series aims for high-level updates roughly every 4-5 weeks, depending on what’s happening in core development. See the previous update here. !we-are-here.png

Thanks to Kevaundray Wedderburn, Alex Stokes, Tim Beiko, Mary Maller, Alexander Hicks, George Kadianakis, Dankrad Feist, and Justin Drake for feedback and review. Ethereum is going all in on ZK. Eventually we expect to migrate to using ZK proofs at all levels of the stack, from consensus layer signature aggregation to onchain privacy with client side proving, and upgrade the protocol to be simpler and more zk-friendly. But the first step will be an L1 zkEVM.

As of today, all Ethereum execution clients support partial history expiry in accordance with EIP-4444. While work on full, rolling history expiry is ongoing, users can expect to reduce the disk space required for an Ethereum node by 300-500 GB by removing the block data prior to the Merge. This will allow a node to fit comfortably on a 2 TB disk. See below for information on each specific client.