Back in February, Vitalik dropped a statement that’s been rattling around in my head ever since: the rollup-centric roadmap that positioned L2s as the way Ethereum would scale “no longer makes sense.”
As someone who’s been building L2 infrastructure at Polygon Labs and Optimism for the past 6 years, this felt like whiplash. We spent half a decade optimizing rollups, and now the narrative is shifting? But after digging into what’s actually happening on-chain and what’s coming with Glamsterdam, I think Vitalik’s reframing is spot-on—though the implications are more nuanced than “L2s failed.”
What Actually Changed?
Let’s start with the facts. According to L2BEAT data, Ethereum L2s are collectively processing around 100,000 TPS—a 6,500x improvement over mainnet capacity. Base alone handles 60%+ of L2 activity (142 TPS with 38.7% growth), Arbitrum sits on $16-19B TVL (41% of the L2 market), and the total L2 ecosystem holds $38-44B in value locked.
By traditional metrics, we absolutely nailed scaling. L2 fees dropped 90%+ post-EIP-4844 blobs (now $0.001-$0.05 vs mainnet), we’re processing ~2M daily transactions across L2s vs ~1M on L1, and proof generation improved 60x in 2026.
But here’s what Vitalik actually said: scaling Ethereum should mean creating “large quantities of block space that is backed by the full faith and credit of Ethereum.” If your connection to L1 is “mediated by a multisig bridge,” then you’re not scaling Ethereum—you’re building a separate chain that uses Ethereum for marketing.
That stung, but it’s technically correct. And it gets to the heart of the problem: fragmentation.
The Fragmentation Problem
We now have Base with 70% of L2 active addresses, 34 OP Stack chains live on the Superchain, and dozens more L2s competing for liquidity. But cross-L2 communication remains siloed—you need bridges, which means UX friction + security risk + MEV extraction on every hop.
From a technical standpoint, we created dozens of isolated execution environments that happen to settle to the same L1. Is that really “Ethereum scaling” or is it “Ethereum brand fragmentation”?
Meanwhile, Solana’s sitting over there with a monolithic approach: single execution layer, unified liquidity, no bridges, simpler mental model. Developers building on Solana don’t think about “which L2?” because there’s only one chain. And honestly? That’s a better developer experience, even if it sacrifices some of Ethereum’s modularity benefits.
Glamsterdam Changes the Equation
The Glamsterdam upgrade (targeting H1 2026) is a game-changer:
- ePBS (EIP-7732): Enshrined Proposer-Builder Separation could reduce MEV extraction by up to 70%
- BALs (EIP-7928): Block-Level Access Lists for better state management
- Performance target: 10,000 TPS on L1 with 78% lower gas fees
If L1 can deliver 10K TPS with $0.01 transactions and built-in MEV protection, what’s the L2 value proposition beyond experimentation?
Vitalik’s answer: L2s should focus on providing value beyond basic scaling. Privacy features, application-specific design, ultra-fast transaction confirmation (<100ms instead of 12s blocks), non-financial use cases. Think of L2s as “specialized service providers” rather than “Ethereum’s only scaling path.”
That reframing makes sense. Optimistic rollups were always a pragmatic compromise (7-day withdrawal delays, fraud proof complexity). ZK rollups are elegant but computationally expensive. If L1 can scale directly, rollups become an optimization for specific use cases—not the only path forward.
So… Did We Scale Wrong?
I don’t think we scaled “wrong”—I think we’re maturing. The rollup-centric roadmap was the right bet in 2020 when L1 fees hit $200+ and scaling was existential. L2s bought us time and proved that modular architectures can work.
But now that EIP-4844 dropped blob costs by 90%+, proof generation improved 60x, and Glamsterdam promises L1 scaling + MEV protection, the calculation changes. If you’re building a new DeFi protocol today, do you:
- Launch on L1 (expensive but maximum composability)?
- Pick a specific L2 (cheaper but siloed liquidity)?
- Go multi-L2 from day one (complex but maximum reach)?
Increasingly, the answer might be “just launch on L1” if Glamsterdam delivers on its promises.
The Real Question
For those of us building L2 infrastructure, Vitalik’s statement isn’t “you failed”—it’s “your job changed.” Instead of pure scaling, L2s need differentiated value:
- Privacy-focused L2s (Aztec, Railgun)
- Gaming chains with custom execution (IMX, Ronin)
- Ultra-low-latency L2s for DeFi (<150ms finality)
- Application-specific rollups with custom precompiles
The question isn’t “did we scale wrong?”—it’s “what should L2s optimize for in a world where L1 can scale?”
Curious what other L2 builders think. Are we pivoting toward specialization? Should Ethereum Foundation prioritize L1 scaling over L2 interoperability? And if we’re honest, was cross-L2 fragmentation always the wrong trade-off?
cc: other L2 engineers who’ve been through this journey—what’s your read on Vitalik’s reframing?
Sources: CoinDesk coverage of Vitalik’s L2 statement, L2BEAT activity data, Ethereum Foundation Glamsterdam upgrade documentation, 21Shares L2 research, QuickNode analysis