If we ship FOCIL (EIP-7805), Frame Transactions (EIP-8141), Keyed Nonces (EIP-8250) and Recent Roots (EIP-8272) in Hegota, we get native, trustless, censorship resistant private transactions on Ethereum next year.

Native UTXOs on Ethereum. Payments should be one-shot objects, not permanent state. Bitcoin got this right. Ethereum can bring the same idea to payments: prove existence from history, keep only a spent bit in state, and reduce permanent state by ~99.8%. Check out the blog post for details.

Two weeks ago, Ethereum researchers met in Berlin to continue charting the protocol's long-term trajectory, following along discussions with client teams in Svalbard in April. The updated strawmap is at and I attached a picture of it to this post. My own high-level takeaways: * "Lean Ethereum" is not a single one-shot upgrade, it is a collection of improvements that will come online to the Ethereum network over the course of three or four years. But make no mistake, this IS the third major iteration of Ethereum in the same way that the Merge was the second. Almost every major piece of the protocol will be replaced: - Verification through recursive STARKs, rather than direct re-execution. Recursive STARKs become an enshrined first-class core component of the protocol - Replacing everything quantum-vulnerable with quantum-safe alternatives - Consensus: decoupled available chain and finality, one or two-round finality. Theoretically optimal security properties, simpler than today, and faster than today - Multidimensional gas - State: not just tree structure, but what *types* of state are available - Changes to client architecture ... At the same time, simplification, cleanup and future-proofing. And this will all be done in a way that minimizes disruption to existing application. We've done this before (the Merge), we can do it again. * H-star (aka Hegota) is probably Ethereum's last thematically "pre-Lean" fork. Starting from I-star, most of everything we do will have a very strong "Lean" feel to it in one way or another. * Privacy is no longer an afterthought, it is a first class goal. When designing Frames, the mempool, additions to the state tree, we explicitly ask the question "okay, how do quantum-safe, intermediary-free privacy protocol transactions go through this, and what is the overhead?" * Formal verification of everything for security. * FV also makes us much more comfortable with canonicalization (having pieces of the protocol that are directly defined as a piece of bytecode expressed in some language). evm-asm is being written in part to become a canonical proof system for the EVM. * Quantum safety has shifted up a LOT in priority. This adds a lot of work (eg. finalizing a quantum-safe blobs design has become urgent; this work has already been ongoing for months) * Probably the single most disruptive part of the plan is the changes to state. There is growing consensus around leaving present-day-style "dynamic state" mostly unchanged, but scaling it only a medium amount, and adding new types of state that are more scalability-friendly (eg. no need for builders to sync/store all of it) but more restrictive, and that will scale a large amount. eg. possible Ethereum in 2030: 2 TB of present-day-style (dynamic) state, and 100 TB of new-style (scalable but restrictive) state This "new-style" state would work very well for ERC20s, NFTs, many defi use cases, but not eg. highly "central" objects like Uniswap contracts, or onchain order books, or other complex things (which are crucial for Ethereum but which only take up a small percentage of state) Hence, it will not be *necessary* to rewrite any apps, but it will be *very cost-effective* to eg. rewrite an ERC20 token into a newer design that uses a new type of UTXO storage that is currently being explored, so that it will have >10x lower txfees. Design of these new state types (current ideas: keyed nonces, ring buffers, UTXOs, statically accessible state, temp state) is an area where we will need a lot of feedback from application developers (incl. privacy-friendly application developers) and probably several rounds of rethinking and iteration. * In the context of a much larger total state size, we need to figure out the incentive issues around who stores this state and what motivates them to. Even saying "each node stores 1%" is not good enough - why do they store that 1% and why are they willing to serve it? This is being elevated as a first-class research area. * Ethereum will need to have a "VM" other than EVM in one form or another - at the very least, we need something like leanISA for recursive STARKs - and the gains are large in exposing it to users so that we support programmable privacy and better scalability. Right now, the most likely contenders are leanISA and RISC-V. My own ideal is that in this world, we adjust the protocol so that the EVM becomes a high-level-language compiler-level feature, and the protocol only "sees" RISC-V / leanISA directly. But this is still far away. * Gas limit increases, blob increases and slot time decreases will happen many times over the next ~5 years. We expect a large gas limit increase with Glasterdam. Each step of increased scale or decreased slot time is a matter of getting to the point where it is safe to do it, which comes from a combination of client optimization and protocol changes. Ethereum is CROPS. Ethereum is scaling. Ethereum is reinventing itself. Onward.

Looking back at Nethermind's core development journey over the years makes me incredibly proud of what the team has accomplished. The Resiliency Phase Before the Merge, there was effectively no alternative to Geth. It was by far the most stable and performant execution client, and execution client diversity barely existed. That concentration posted a major risk to Ethereum's resilience and one of its core properties: never going down. Today, Nethermind stands alongside Geth as one of the leading execution clients, with each accounting for roughly 30% of the network. The Ethereum Scaling Phase Once execution client diversity became a reality, the next major challenge was scaling Ethereum. Ethereum had been stuck at around a 30M gas limit for a long time. Nethermind led much of the performance engineering effort, demonstrating that Ethereum could safely operate at significantly higher throughput. Beyond setting an example, many of our optimisations and ideas were adopted by other client teams, helping raise performance across the whole Ethereum. Just as importantly, we helped establish a performance engineering culture within Ethereum core development, bringing a more data-driven approach to gas limits and gas pricing. That work was later adopted and expanded by the EF. Ethereum still has plenty of room to scale, but we're moving in the right direction. What's Next We’re now focused on the next set of challenges: 1. Executing on the Strawmap while leveraging AI as much as possible and exploring how AI agents can make Ethereum development increasingly autonomous. 2. Making Ethereum post-quantum resilient. It's part of the Strawmap, but it's important enough to deserve a separate point. 3. Accelerating institutional adoption of Ethereum. 4. Improving RPC layer - from hardening and design to making it verifiable.

Announcing Ethlabs: a non-profit R&D lab for Ethereum and ETH Our mission is to make Ethereum the settlement layer of the global economy. The internet became global because shared protocols created a common language between networks. Private systems remained useful, but bounded. Finance is approaching a similar moment. As value, assets, and markets become digital, the world needs shared settlement infrastructure. Ethereum is uniquely positioned to become that shared base layer, the neutral foundation on which users, institutions, and agents can transact without intermediation. What we believe: • We believe credible neutrality matters. Ten years of uptime and the lowest counterparty risk. Ground that cannot be pulled away by any one country, institution, company, or person. • We believe ETH matters. The most valuable, programmable store of value. A decade of broad distribution, deep liquidity in onchain markets, and maximally trustless asset on Ethereum. • We believe DeFi matters. Markets, liquidity, credit, exchange, and coordination, open to anyone. • We believe adoption matters. Principles do not change the world until people benefit from them. We sit between two worlds: real usage from the builders at the frontier, and the protocol that has to support it. We work with users, applications, wallets, L2s, infrastructure teams, institutions, ETH holders, core devs and researchers, then turn what they actually need into protocol work, shared standards, infrastructure, and shipped products. Ethlabs is independent but Ethereum is a shared project. We are one node in a much larger network of stewards. This is the multi-node future. We have spent the better part of the past decade contributing to Ethereum core research and development. We are opinionated and transparent. We move with urgency, learn in public, and course-correct when we’re wrong. We are building a lean, talent-dense team for people who want to do the most important work of their careers: join@ethlabs.org