Ethereum 2029 Strawmap Guide: Rapid Consensus, Native Privacy, and the "Accelerating Variables" Brought by AI

The Idiot’s Guide to Ethereum’s 2029 Strawmap

James | Snapcrackle

Translated by Ken, Chaincatcher

Ethereum has just released its most detailed upgrade plan in history. Seven upgrades. Five goals. One massive rebuild.

Sketch:

This analogy is worth a deep dive.

The Ship of Theseus is an ancient Greek thought experiment: if you replace every plank of a ship one by one until none of the original planks remain, is it still the same ship?

This is exactly what the Strawmap proposes for Ethereum.

By 2029, every major component of the system will be replaced. But there will never be a “shutdown and rewrite” plan. The goal is to achieve backward-compatible upgrades, keeping the blockchain running in real time while replacing the “planks,” even though each upgrade still requires node operators to update their software, and some edge cases may change. This is essentially a thorough rebuild disguised as incremental upgrades.

Strictly speaking, while the consensus and execution logic are being rebuilt, the state (user balances, contract storage, and history) will be preserved at all fork points. The “ship” is being rebuilt while still carrying cargo. All aboard!

“Why not start from scratch?” Because you can’t reboot Ethereum without losing its core value: the applications already running on it, the flowing funds, and the trust built up. You have to replace the planks while the ship is sailing.

The name “Strawmap” is a combination of “strawman” and “roadmap.” “Strawman” refers to an initial proposal known to be imperfect, meant to invite critique. So, this is not a promise but a starting point for discussion. But it’s the first time Ethereum’s builders have laid out a detailed, structured, time-bound upgrade path with clear performance goals.

The work involves top cryptographers and computer scientists worldwide. And it’s all open source. No licensing fees, no vendor contracts, no corporate sales teams. Any company, developer, or country can build on it. The upgrade that JPMorgan benefits from is the same as what a three-person startup in São Paulo can access.

Imagine a global alliance of top engineers rebuilding the internet’s financial plumbing from scratch, and all you need to do is… connect directly.

How Ethereum Works (60 Seconds)

Before discussing its future, let’s look at how it works today.

Ethereum is essentially a shared global computer. It’s not run by a single company’s servers but by thousands of independent operators worldwide, each running the same software copy.

These operators independently verify transactions. Some are called validators, who also stake their own funds (ETH) as collateral. If a validator tries to cheat, they lose their stake. Every 12 seconds, validators reach consensus on what transactions occurred and their order. This 12-second window is called a “slot.” Every 32 slots (about 6.4 minutes) makes an “epoch.”

The moment transactions become truly final—i.e., irreversible—takes about 13 to 15 minutes, depending on where your transaction lands in the validation cycle.

Ethereum processes roughly 15 to 30 transactions per second, depending on transaction complexity. In contrast, Visa can handle over 65,000 per second. Due to this gap, most Ethereum applications now run on “Layer 2” solutions. Layer 2s are independent systems that batch many transactions and then send summarized data back to Ethereum’s base layer to ensure security.

The system that achieves consensus among all operators is called the “consensus mechanism.” Ethereum’s current mechanism has proven reliable but was designed for an earlier era, limiting the network’s capabilities.

Strawmap aims to fix all these issues. One upgrade at a time.

Strawmap’s Five Core Goals

This roadmap revolves around five goals. Ethereum is already operational, with billions of dollars flowing daily. But it has practical limits on what can be built on top. These five goals aim to eliminate those limits.

1. Fast L1: Finality in seconds

Today, it takes about 13 to 15 minutes for a transaction on Ethereum to reach true finality—meaning it’s irreversible, complete, and cannot be reversed.

Solution: Replace the engine that achieves consensus among all operators. The goal is to achieve finality within each slot through a single round of voting. Minimint is one of the leading candidates under research—a protocol designed for ultra-fast consensus, but its design is still being refined. The key goal: finality within a single slot. Next, the slot duration itself will be compressed: proposed paths are 12 seconds → 8 seconds → 6 seconds → 4 seconds → 3 seconds → 2 seconds.

Finality isn’t just about speed; it’s about certainty. Think of wire transfers: the window between “sending” and “settling” is when problems can occur.

If you’re transferring millions of dollars, settling bonds, or completing real estate transactions on-chain, that 13-minute uncertainty is a big problem. Shortening it to a few seconds would fundamentally change what this network can do. Not just for native crypto apps, but for any value transfer.

2. Gigagas: 300x expansion

Ethereum’s mainnet currently handles about 15-30 transactions per second. That’s a bottleneck.

Solution: Strawmap’s goal is to reach 1 gigagas (billion gas) execution capacity per second, roughly translating to 10,000 TPS (depending on transaction complexity, as different operations consume different gas). The core idea involves a technology called “zero-knowledge proofs.”

The simplest way to understand: today, each operator must re-execute every computation to verify correctness. It’s like every employee in a company redoing everyone else’s math problems. Safe? Yes. Efficient? No.

ZK proofs allow you to verify a compact mathematical “receipt” that proves the computation was correct. The same level of trust, but with minimal work.

Current proof-generation software is still slow—taking minutes to hours for complex tasks.

Reducing this to a few seconds (roughly 1000x faster) is an active research frontier, not just an engineering challenge. Teams like RISC Zero and Succinct are making rapid progress, but it’s still cutting-edge.

A mainnet with fast finality and up to 10,000 TPS means a simpler system with fewer moving parts, and fewer chances for issues.

3. Teragas L2: Cross “fast lane” with millions of TPS

For truly massive transactions (and custom use cases), Layer 2 networks are still needed. Currently, L2s are limited by how much data the Ethereum mainnet can handle.

Solution: A technique called “Data Availability Sampling” (DAS). Instead of requiring each operator to download all data for verification, they check random samples and use math to verify the entire dataset’s integrity. Imagine flipping through 20 random pages of a 500-page book to confirm it’s on the shelf; if those pages are present, you can statistically trust the rest.

PeerDAS has been delivered in Fusaka upgrades, laying the infrastructure for Strawmap. Scaling further involves iterative capacity increases at each fork and stress-testing network stability.

Cross-L2 ecosystems capable of 10 million TPS would open doors that no current blockchain can.

Imagine a global supply chain where each product and cargo has a digital token; or millions of connected devices generating verifiable data; or micro-payments of fractions of a cent. These workloads are too large for existing networks. But with 10 million TPS, they become manageable.

4. Post-quantum L1: Preparing for quantum computers

Ethereum’s security relies on math problems that are extremely hard for today’s computers. This applies to user signatures and validator consensus signatures. Once quantum computers become powerful enough, they could crack these signatures, enabling attackers to forge transactions or steal funds.

Solution: Transition to new cryptographic methods believed to resist quantum attacks (hash-based schemes). This is a late-stage upgrade because it affects nearly every part of the system, and the new methods use larger data sizes (kilobytes instead of bytes), changing the economics of block size, bandwidth, and storage.

Quantum attacks on current cryptography might still be decades away. But if you’re building infrastructure meant to last decades—potentially carrying trillions of dollars—“wait and see” isn’t a real option.

5. Privacy L1: Achieving transaction confidentiality

All information on Ethereum is public by default. Unless you use privacy tools like Railgun, or privacy-focused Layer 2s like ZKsync or Aztec, every transaction, amount, and counterparty is visible to anyone.

Solution: Embed confidential transaction capabilities directly into Ethereum’s core. The goal is to enable the network to verify transaction validity, sender’s funds, and correctness of calculations without revealing actual details. You could prove “this is a legitimate $50,000 payment” without revealing who paid, who received, or the purpose.

Some stopgap solutions exist. EY and StarkWare announced in February 2026 the launch of Nightfall on Starknet, bringing privacy-preserving transactions to Layer 2. But stopgaps increase complexity and costs. Building privacy into the infrastructure can eliminate the need for middleware altogether.

This is also where post-quantum work intersects: any privacy solution must be quantum-resistant. These are two intertwined challenges. Once solved, a major barrier to widespread adoption will be gone.

Seven Forks (Upgrades)

Strawmap proposes seven upgrades, roughly every six months, starting from Glamsterdam. Each is deliberately scoped to change only one or two major aspects, because if problems arise, you need to know exactly what caused them.

Following Fusaka (already released, laying groundwork via PeerDAS and data tuning), the first upgrade is Glamsterdam, which restructured how transaction blocks are assembled.

Next is Hegotá, with further structural improvements. The remaining forks (from I* to M*) will continue through 2029, gradually introducing faster consensus, zero-knowledge proofs, expanded data availability, post-quantum cryptography, and privacy features.

Why wait until 2029?

Because some issues remain unsolved.

Replacing the consensus mechanism is the hardest. Imagine changing an engine mid-flight with thousands of co-pilots needing to agree on every modification. Each change requires months of testing and formal verification. Pushing cycle times below 4 seconds faces a physical limit: signals take about 200 milliseconds to cross the Earth—you’re essentially fighting the speed of light.

Making ZK proofers fast enough is another frontier challenge. Current speeds (minutes) are about 1000 times slower than the target (seconds). It requires breakthroughs in mathematics and specialized hardware.

Scaling data availability is difficult but more manageable. The math is sound. The challenge is operating cautiously on a real-time network worth hundreds of billions of dollars.

Post-quantum migration is a logistical nightmare, as new signatures are large and change the entire economic model.

Native privacy isn’t just technically hard; it’s politically sensitive. Regulators worry privacy tools could facilitate money laundering. Engineers must build systems that are private enough to be practical but transparent enough to meet compliance, and also quantum-resistant.

These upgrades can’t all happen simultaneously. Some depend on others. Without mature ZK proofs, scaling to 10,000 TPS isn’t possible. Without data availability improvements, L2 scaling stalls. These dependencies shape the timeline.

For all this effort, three and a half years is already quite aggressive.

2029?

First, there’s a variable. Strawmap explicitly states: “The current draft assumes a human-led development model. AI-driven development and formal verification could significantly compress the timeline.”

In February 2026, a developer named YQ bet Vitalik that an AI agent could write a complete Ethereum system targeting the 2030+ roadmap. Weeks later, he delivered ETH2030: an experimental Go client claiming 710,000 lines of code, implementing all 65 projects on Strawmap, marked as testnet and mainnet ready.

Is it production-ready? No. As Vitalik pointed out, the code almost certainly contains critical vulnerabilities, and in some cases, it’s just a stub implementation—AI didn’t even attempt a full version.

But Vitalik’s response is worth noting: “Six months ago, this was pure fantasy, and the trend is what matters… People should remain open to this possibility (not certainty!)—the completion of Ethereum’s roadmap could happen much faster than expected, and security standards could surpass expectations.”

His core insight: AI should not be used just for speed. Half of AI’s benefits should go toward increasing speed, the other half toward enhancing security—more testing, more mathematical validation, and multiple independent implementations of the same functionality.

The Lean Ethereum project is working on formal verification of parts of cryptography and proof stacks. The “bug-free code” long considered an ideal may actually become a basic expectation.

Strawmap is a coordinating document, not a promise. Its ambitious goals and timelines are aspirational, relying on hundreds of independent contributors.

But the real question isn’t whether each goal is achieved on time. It’s whether you want to build on a platform with this trajectory, or compete with it.

And all of this—the research, breakthroughs, cryptographic migrations—is happening openly, freely, and for everyone… That’s the part of this story that truly deserves much more attention than it gets now.