Free 30-min Web3 Consultation
Book Now
Smart Contract Security Audits
Learn More
Custom DeFi Protocol Development
Explore
Full-Stack Web3 dApp Development
View Services
Free 30-min Web3 Consultation
Book Now
Smart Contract Security Audits
Learn More
Custom DeFi Protocol Development
Explore
Full-Stack Web3 dApp Development
View Services
Free 30-min Web3 Consultation
Book Now
Smart Contract Security Audits
Learn More
Custom DeFi Protocol Development
Explore
Full-Stack Web3 dApp Development
View Services
Free 30-min Web3 Consultation
Book Now
Smart Contract Security Audits
Learn More
Custom DeFi Protocol Development
Explore
Full-Stack Web3 dApp Development
View Services
the-ethereum-roadmap-merge-surge-verge
Blog

Execution Layer Limits Developers Keep Hitting

A technical autopsy of the three fundamental execution layer constraints—computational gas, state bloat, and synchronous composability—that bottleneck smart contract developers today, and how the Surge's roadmap addresses them.

introduction
THE BOTTLENECK

The Merge Was a Sideshow. The Real Fight is in Execution.

Post-Merge, the execution layer is the primary constraint on developer innovation and user experience.

The consensus layer is solved. The Merge delivered a secure, scalable settlement foundation, but this is now a commodity. The execution environment—where smart contracts run—is where all meaningful competition and constraints now exist.

Developers are hitting gas limits. Complex DeFi logic and on-chain games like Parallel and Pirate Nation require more compute and storage per transaction than the EVM's 30M gas block affords. This forces painful architectural compromises.

State growth is unsustainable. Every new contract and storage slot bloats the global state, slowing node sync times. Solutions like Verkle Trees and stateless clients are years from production, creating a scalability time bomb.

The evidence is in rollup migration. Teams building high-throughput apps (e.g., dYdX, Sorare) choose app-specific rollups on Starknet or Arbitrum Orbit. They are voting with their code, abandoning the monolithic chain model for execution sovereignty.

EXECUTION LAYER BOTTLENECKS

The Cost of Constraint: Gas Analysis of Common Operations

A comparison of the gas cost and performance impact of fundamental EVM operations that define protocol design ceilings.

Operation & ConstraintBase Cost (gas)Typical ImpactMitigation Strategy

SSTORE (cold → warm)

22,100 gas

~$1.50 (200 Gwei)

Packing bits, Merkle proofs

SLOAD (warm)

100 gas

~$0.007 (200 Gwei)

In-memory caching, immutable refs

CALL (with value)

at least 21,000 gas

~$1.40 (200 Gwei)

Batching, native transfers

LOG1 (256-bit topic)

375 gas + 8 gas/byte

~$0.03 per event (200 Gwei)

Bloom filter indexing, event compression

Keccak256 (256-bit hash)

60 gas + 12 gas/word

~$0.01 per hash (200 Gwei)

Pre-computation, proof verification off-chain

Contract Deployment (minimal)

~200,000 gas

~$13.50 (200 Gwei)

Proxy patterns (EIP-1167), CREATE2

Revert with message

Gas consumed up to revert point + fee

Wasted user capital, failed UX

Static calls for simulation, invariant checks

deep-dive
THE EXECUTION BOTTLENECK

Beyond Gas: The Silent Killers of State and Composability

Gas fees are a symptom; the underlying constraints on state access and atomic composability are the disease.

State access is the real bottleneck. Every transaction must read and write to a shared database. EVM's linear processing and limited calldata create a hard cap on throughput, independent of gas price.

Atomic composability is broken across chains. A Uniswap swap on Arbitrum cannot atomically trigger a deposit to Aave on Optimism. This forces developers into fragile, multi-step workflows using bridges like Across or LayerZero.

The EVM's storage model is inefficient. SLOAD/SSTORE operations are orders of magnitude more expensive than compute. Projects like Solana and Fuel use alternative models (e.g., UTXO-like) to parallelize state access.

Evidence: Arbitrum Nitro's 2M+ TPS benchmark is for compute; real-world DeFi applications, constrained by state I/O, achieve less than 1% of that.

protocol-spotlight
EXECUTION LAYER BOTTLENECKS

How Builders Are Working Around The Limits

Developers are hitting fundamental constraints in state growth, compute, and latency. Here's how they're building through them.

01

The State Explosion Problem

Global state bloat on L1s like Ethereum creates unsustainable hardware requirements and high sync times. The solution is a shift to stateless clients and verkle trees, which separate execution from state validation.

  • Key Benefit: Reduces node requirements from ~2TB SSD to ~50GB RAM.
  • Key Benefit: Enables lightweight verification, paving the way for zk-EVMs and safer light clients.
~50GB
Node RAM
40x
Sync Speed
02

Parallel Execution is Non-Negotiable

Sequential processing on EVM chains caps throughput at ~100-200 TPS. Projects like Solana, Sui, and Aptos treat parallel execution as a first-principle, while Ethereum L2s like Monad and Sei are building parallelized EVMs.

  • Key Benefit: Unlocks 10,000+ TPS for specific workloads (e.g., DEX arbitrage).
  • Key Benefit: Dramatically reduces latency for complex DeFi transactions, improving user experience.
10,000+
Peak TPS
<1s
Finality
03

Intent-Based Architectures

Users shouldn't micromanage transaction paths. UniswapX, CowSwap, and Across use intents—declarative statements of desired outcomes—which are fulfilled by a decentralized solver network.

  • Key Benefit: ~20% better swap rates via MEV capture and optimal routing.
  • Key Benefit: Gasless signing for users, shifting complexity and cost to competitive solvers.
20%
Better Rates
$0
User Gas
04

Modular Data Availability

Rollups are bottlenecked by posting data to expensive L1 calldata. Celestia, EigenDA, and Avail provide specialized, cheap data availability layers, decoupling security from execution cost.

  • Key Benefit: Reduces L2 transaction costs by 80-90% by moving data off the main chain.
  • Key Benefit: Enables sovereign rollups with independent governance and upgrade paths.
-90%
Data Cost
$0.001
Per Tx Goal
05

Shared Sequencer Networks

Individual rollup sequencers create fragmentation, poor UX, and MEV leakage. Espresso, Astria, and Radius are building decentralized sequencer sets that order transactions for multiple rollups.

  • Key Benefit: Enables atomic cross-rollup composability (e.g., a single trade across 3 L2s).
  • Key Benefit: Democratizes MEV revenue and provides censorship resistance through decentralization.
Atomic
Cross-Rollup
Decentralized
MEV Capture
06

The App-Specific Chain Thesis

General-purpose chains force all dApps to compete for the same congested block space. dYdX, Aave, and Frax are migrating to app-chains (sovereign or rollup) for full control over throughput, fees, and governance.

  • Key Benefit: Sub-second block times and zero gas fees for users, funded by protocol treasury.
  • Key Benefit: Custom VM design allows for optimized state models (e.g., orderbook vs. AMM).
0 Gas
For Users
Custom VM
Optimization
future-outlook
THE EXECUTION BOTTLENECK

The Surge Prescription: Verkle Trees, PBS, and a New EVM

Ethereum's current execution layer imposes hard limits on state growth and block building that developers now routinely hit.

State growth is the existential threat. The EVM's Merkle-Patricia Trie forces every node to store the entire state, creating a data availability crisis that limits node count and decentralization.

Verkle Trees are the state solution. They compress witness sizes by ~30x using polynomial commitments, enabling stateless clients and removing the primary barrier to scaling validator participation.

Proposer-Builder Separation (PBS) fixes MEV centralization. Without PBS, block builders like Flashbots and bloXroute centralize power; PBS externalizes block construction to a competitive market.

EVM Object Format (EOF) is the necessary upgrade. The current EVM is a technical debt monolith; EOF introduces a versioned, modular structure enabling parallel execution and WASM compatibility.

Evidence: The current 1.2 TB state size grows by ~50 GB/month. Without Verkle Trees, running a node becomes infeasible for all but institutional actors within 2 years.

takeaways
EXECUTION LAYER BOTTLENECKS

TL;DR for Protocol Architects

The EVM's synchronous, single-threaded design creates predictable but severe scaling limits. Here are the concrete walls developers hit and the architectural shifts needed to break through.

01

The State Contention Wall

Global shared state forces sequential execution, capping throughput at ~50 TPS on Ethereum L1. Every transaction competes for the same memory slots, creating a congestion tax.

  • Problem: Hot contracts (e.g., Uniswap, USDC) serialize all operations.
  • Solution: Parallel execution via optimistic concurrency (Aptos, Sui) or sharded state (Monad, Fuel).
  • Impact: Enables 10,000+ TPS by processing independent transactions simultaneously.
~50 TPS
EVM L1 Cap
200x
Potential Gain
02

The Gas Cost Spiral

Complex logic (DeFi strategies, ZK proofs) hits the 30M gas block limit, forcing protocol logic off-chain or onto expensive L2s. This stifles innovation in-app.

  • Problem: Single transaction cost exceeds $100+ during L1 congestion for advanced ops.
  • Solution: Native account abstraction (ERC-4337) for batching, and L2s with ~10x cheaper execution (Arbitrum, Optimism).
  • Future: Verkle trees and stateless clients will decouple execution cost from state size.
30M
Gas Limit
-90%
L2 Cost
03

The MEV & Atomicity Ceiling

The lack of native transaction ordering control surrenders value to searchers and limits complex cross-contract atomicity. This breaks composability for advanced DeFi.

  • Problem: Frontrunning and sandwich attacks extract $500M+ annually, distorting user outcomes.
  • Solution: Encrypted mempools (Shutter Network), SUAVE, and intents-based flow (UniswapX, CowSwap).
  • Result: Protocols reclaim control over execution, enabling guaranteed atomic bundles.
$500M+
Annual Extract
Secure
Atomic Bundles
04

The Synchronous Composability Trap

EVM's 'everything in one block' model is both its superpower and its kryptonite. It forces protocols into a fragile, interdependent lattice that crashes under load.

  • Problem: A single failing transaction can revert an entire complex DeFi sequence, creating systemic risk.
  • Solution: Asynchronous design patterns via rollups with fast finality (Solana-inspired L2s) and optimistic execution with fallback paths.
  • Shift: Moving from synchronous function calls to message-passing across execution domains.
~12s
Block Time
Async
New Paradigm
ENQUIRY

Get In Touch
today.

Our experts will offer a free quote and a 30min call to discuss your project.

NDA Protected
24h Response
Directly to Engineering Team
10+
Protocols Shipped
$20M+
TVL Overall
NDA Protected direct pipeline