Futures
Hundreds of contracts settled in USDT or BTC
TradFi
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Futures Kickoff
Get prepared for your futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to experience risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Launchpad
Be early to the next big token project
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
Ethereum 2029 Roadmap Detailed: Rebuild yourself from the ground up, but this ship cannot stop
Author: James/Snapcrackle
Translation: Deep Tide TechFlow
Deep Tide Introduction: Ethereum researcher Justin Drake released “Strawmap”—the first structured upgrade roadmap in history with clear timelines and performance goals. Vitalik called it “very important,” describing its overall effect as a “Ship of Theseus” style reconstruction. This article is currently the clearest popular science explanation of Strawmap, covering its principles, five major goals, and seven upgrades—all understandable even without technical background.
Full text below:
Ethereum has just released its most detailed upgrade plan ever. Seven upgrades, five goals, one large-scale rebuild.
If you’re wondering who this guide is for… it’s for me.
Ethereum researcher Justin Drake published what he calls “Strawmap,” a proposed timeline for seven major upgrades extending to 2029. Ethereum co-founder Vitalik Buterin called it “very important,” describing its cumulative effect as a “Ship of Theseus” style reconstruction of Ethereum’s core.
This metaphor is worth understanding.
The Ship of Theseus is an ancient Greek thought experiment: if you replace each plank of a ship one by one, is it still the same ship?
That’s what Strawmap proposes for Ethereum.
By 2029, every major component of the system will be replaced. But there’s no planned “big shutdown” or overhaul. The goal is backward-compatible upgrades, replacing parts while keeping the chain running—though each upgrade still requires node operators to update their software, and edge cases may occur. This is a complete rebuild disguised as a gradual upgrade. Strictly speaking, both the consensus layer and execution layer logic are being reconstructed, but the state (user balances, contract storage, history) is preserved across all forks. “This ship is being rebuilt while carrying cargo.” Everyone, get on board!
“Why not just restart from scratch?” Because you can’t reboot without losing what makes Ethereum valuable: the applications running on it, the flowing funds, the trust built over time. You must replace the planks while the ship is still sailing.
“Strawmap” is a portmanteau of “strawman” and “roadmap.” A strawman is an intentionally imperfect initial proposal meant for critique. So this isn’t a promise but a starting point for debate. But it’s the first time Ethereum builders have laid out a structured, time-bound upgrade path with clear performance targets.
The work involves the world’s top cryptographers and computer scientists, 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. JPMorgan will benefit from these upgrades just as much as a three-person startup in São Paulo.
Imagine a coalition of top engineers rebuilding the internet’s financial infrastructure from scratch, with you directly connected.
How Ethereum Works (60-Second Version)
Before talking about where it’s headed, let’s clarify what it is today.
Ethereum is essentially a shared global computer. Not operated by a single company on one server, but thousands of independent operators running copies of the same software.
These operators independently verify transactions. Some are called validators, who also stake their ETH as collateral. If a validator tries to cheat, their staked ETH is forfeited. Every 12 seconds, validators reach consensus on which transactions occurred and in what order. This 12-second window is called a “slot.” Every 32 slots (about 6.4 minutes) makes up an “epoch.”
Finality—the point when transactions become irreversible—takes about 13 to 15 minutes, depending on where your transaction falls in the cycle.
Ethereum’s processing speed is roughly 15 to 30 transactions per second, depending on transaction complexity. In comparison, Visa processes over 65,000 transactions per second. This gap is why most Ethereum applications today run on “Layer 2” networks—independent systems that bundle many transactions and submit summaries back to the main chain for security.
All these operators reaching consensus is called the “consensus mechanism.” Ethereum’s current mechanism works well and has been battle-tested, but it was designed for an earlier era, limiting the network’s capacity.
Strawmap aims to fix all these issues, one upgrade at a time.
Strawmap’s Five Core Goals
The roadmap is organized around five goals. Ethereum is already operational, with billions of dollars flowing daily. But it has real limitations on what can be built. These five goals aim to eliminate those limits.
Today, confirming a transaction on Ethereum takes about 13-15 minutes—meaning it’s irreversible and complete only after that time.
Solution: Replace the engine that all operators use to reach consensus. The goal is to achieve finality within each slot through a single round of voting. A leading candidate is Minimmit, a protocol designed for ultra-fast consensus, still under development. The key goal: finality within a single slot. Slot times themselves will also be compressed: proposals are 12 seconds, then 8, 6, 4, 3, 2 seconds.
Finality isn’t just about speed; it’s about certainty. Think of wire transfers—how long between “sent” and “settled”—that window is where errors can occur. If you’re settling a million-dollar payment, bond transaction, or real estate deal, those 13 minutes of uncertainty matter. Compressing this to seconds fundamentally changes what the network can do—beyond native crypto apps, to any value transfer.
Ethereum mainnet currently processes about 15-30 transactions per second, which is a bottleneck.
Solution: Strawmap aims for 1 gigagas (billion operations per second) of execution capacity, roughly translating to 10,000 transactions per second (depending on transaction complexity). The core technology is “zero-knowledge proofs” (ZK proofs).
Simplest way to understand: now, each operator must recompute every transaction to verify correctness—like every employee redoing each other’s work. Secure but highly inefficient. ZK proofs let you check a compact mathematical proof that the computation was correct, with minimal work. Trust is the same, work is vastly reduced.
Current proof generation software is slow—minutes to hours for complex tasks. Speeding this up to seconds (a 1,000x boost) is an active research frontier, involving breakthroughs in math and specialized hardware. Teams like RISC Zero and Succinct are making rapid progress, but it’s still cutting-edge.
A mainnet with 10,000 TPS and fast finality means simpler, fewer components, and less room for errors.
For truly massive throughput (and customization), Layer 2 solutions are still needed. Today, L2 capacity is limited by what the mainnet can process.
Solution: “Data Availability Sampling” (DAS). Instead of every operator downloading all data, they check random samples and verify the full dataset mathematically. Like checking a 500-page book by flipping through 20 random pages—if all are present, you can statistically confirm the rest.
PeerDAS is live on Fusaka, laying the groundwork for Strawmap. Extending this to full capacity involves iterative upgrades: each fork adds more data capacity and tests network stability.
L2 throughput of 10 million TPS opens doors that are impossible on any current blockchain—think global supply chains, where each product or shipment has a digital token; or millions of IoT devices generating verifiable data; or micro-payments costing fractions of a cent. These workloads are too large for existing networks, but at 10 million TPS, they become feasible.
Ethereum’s security relies on math problems that are hard for today’s computers—used in signatures and consensus. Quantum computers, once powerful enough, could break these, allowing forgery or theft.
Solution: Transition to new cryptography methods (hash-based schemes) believed to resist quantum attacks. This is a late-stage upgrade because it affects nearly everything—new signatures are larger (kilobytes vs. bytes), impacting block size, bandwidth, and storage economics.
Quantum threats may still be years or decades away, but for infrastructure holding trillions of dollars, “later” isn’t good enough.
By default, everything on Ethereum is public. Unless you use privacy tools like Railgun or privacy-focused L2s like ZKsync or Aztec, every transaction, amount, and counterparty is visible.
Solution: Build confidential transactions directly into Ethereum’s core. The goal is to verify transaction validity (sender has enough funds, math checks out) without revealing details. You could prove “this is a legitimate $50,000 payment” without revealing who paid whom or for what.
Current workarounds exist. EY and StarkWare announced Nightfall on Starknet in February 2026, bringing privacy to L2. But these add complexity and cost. Building privacy into the base layer eliminates middlemen.
This is also where post-quantum work intersects: any privacy solution must be quantum-resistant. Two hard problems to solve simultaneously. Solving this removes a major barrier to large-scale adoption.
Seven Forks (Upgrades)
Strawmap proposes seven upgrades, roughly every six months, starting with Glamsterdam. Each upgrade is deliberately limited to one or two major changes, so if issues arise, the cause is clear.
After Fusaka (already live, laying groundwork with PeerDAS and data tuning), the first upgrade is Glamsterdam, restructuring how transaction blocks are assembled.
Hegotá follows with further structural improvements. Remaining forks (I to M) extend to 2029, gradually introducing faster consensus, ZK proofs, expanded data availability, quantum-resistant cryptography, and privacy features.
Why until 2029?
Because some problems are genuinely unsolved.
Replacing the consensus mechanism is the hardest. Imagine replacing an airplane’s engine mid-flight with thousands of co-pilots needing to agree on the change. Each change requires months of testing and formal verification. Eventually, compressing cycle times below 4 seconds hits physical limits: signals take about 200 milliseconds to circle the Earth, and at some point, you’re racing the speed of light.
Making ZK proof systems fast enough is another frontier. Current speeds are minutes; the goal is seconds—a 1,000x leap—requiring mathematical breakthroughs and specialized hardware.
Expanding data availability is less difficult but still challenging. The math is understood; the challenge is cautious operation on a network holding trillions of dollars.
Post-quantum migration is a nightmare at the operational level, as new signatures are much larger, changing the entire economic model.
Native privacy adds political sensitivity. Regulators worry privacy tools enable money laundering. Engineers must build solutions that are private enough to be useful but transparent enough to meet compliance, and also quantum-resistant.
All these upgrades depend on each other. You can’t scale to 10,000 TPS without mature ZK proofs, nor expand L2 without data availability solutions. These dependencies shape the timeline.
Considering the scope, three and a half years is already ambitious.
2029?
First, there’s a variable. Strawmap explicitly states: “The current draft assumes human-led development. AI-driven development and formal verification could significantly shorten the timeline.”
In February 2026, a developer named YQ bet Vitalik that a single AI agent could program the entire Ethereum system for the 2030+ roadmap. Weeks later, he released ETH2030: an experimental Go client claiming 713,000 lines of code implementing all 65 items of Strawmap, tested on testnet and mainnet.
Is it production-ready? No. As Vitalik pointed out, it almost certainly has critical bugs, stub implementations, and AI has not attempted full versions. But his response is worth reading carefully: “Six months ago, even such a thing was far beyond possibility. The important thing is the trend… people should remain open to this possibility (not certainty! possibility): Ethereum’s roadmap will be completed much faster than expected, and with higher safety standards than anticipated.”
Vitalik’s core insight is that using AI correctly isn’t just about speed; it’s about splitting the gains—half for faster development, half for safety: more testing, more mathematical validation, more independent implementations of the same system.
The Lean Ethereum project is formalizing some cryptography and proof stacks with machine verification. Bug-free code—long considered an idealistic fantasy—may truly become a basic expectation.
Strawmap is a coordination document, not a promise. Its goals are ambitious, the timeline is visionary, and execution depends on hundreds of independent contributors.
But the real issue isn’t whether each goal is achieved on time. It’s whether you want to build on this trajectory or compete with it.
And all of this—research, breakthroughs, cryptography migrations—is happening openly, freely, and accessible to anyone… which is the part that should be getting far more attention than it currently does.