Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
the-modular-blockchain-thesis-explained
Blog

The Future of Execution Environments: Too Many, Too Soon?

The modular thesis promised unbounded scalability through specialization. But the rapid proliferation of custom VMs—Ethereum's EVM, Solana's SVM, Aptos/Sui's Move—is creating a new bottleneck: fragmented developer ecosystems. This analysis argues that without standardization layers, this fragmentation will stall, not accelerate, the next wave of adoption.

introduction
THE EXECUTION LAYER FRAGMENTATION

Introduction: The Modular Paradox

The proliferation of execution environments is creating a user experience and developer burden that threatens to undermine modularity's core value proposition.

Modularity's promise is fragmentation. Separating execution from consensus and data availability creates a Cambrian explosion of specialized chains. This yields optimized performance and sovereign governance, but at the cost of a unified user experience.

The current state is unsustainable. Users face a fragmented liquidity landscape and prohibitive bridging costs. Developers must deploy and maintain code across dozens of incompatible VMs like EVM, SVM, and Move, each with its own tooling and security assumptions.

The paradox is that abstraction layers become the new bottleneck. Solutions like LayerZero's Omnichain Fungible Tokens (OFT) and Circle's Cross-Chain Transfer Protocol (CCTP) abstract bridging, but they centralize security and liquidity into new, critical intermediaries.

Evidence: The Ethereum L2 ecosystem alone has over 40 active chains. Managing assets across Arbitrum, Optimism, Base, and zkSync requires interacting with multiple bridges and paying gas in different native tokens, a clear UX failure.

thesis-statement
THE EXECUTION LAYER BOTTLENECK

Core Thesis: Fragmentation is the New Scaling Limit

The proliferation of execution environments is creating a user experience and capital efficiency crisis that monolithic scaling cannot solve.

Fragmentation is the bottleneck. L2s like Arbitrum and Optimism solved data availability, but they created isolated execution silos. Moving assets between these silos requires slow, expensive bridges like Across or Stargate, negating scalability gains.

Monolithic L1 scaling is insufficient. Solana and Monad achieve high throughput but enforce a single, global state. This creates a winner-take-all market for block space and fails to accommodate specialized execution needs like privacy or gaming.

The future is a unified settlement layer. Ethereum's roadmap positions it as a coordinated settlement base layer, not a competitor to high-throughput chains. Its role is to finalize state proofs from diverse execution environments like Arbitrum, zkSync, and Fuel.

Evidence: The TVL locked in bridges exceeds $20B, a direct tax on interoperability. User sessions that span multiple chains see 90% of gas spent on bridging, not application logic.

THE STATE OF THE STACK

Execution Environment Ecosystem Comparison

A feature and performance matrix comparing the leading execution environments vying for developer mindshare.

Feature / MetricEVMSolana VM (SVM)Move VM (Aptos/Sui)FuelVMCosmWasm

Execution Model

Single-threaded, global state

Parallelizable via Sealevel

Parallelizable via Block-STM

Parallelizable via UTXO model

Single-threaded, IBC-aware

Dominant Language

Solidity

Rust, C, C++

Move

Sway (Rust-like)

Rust

Gas Fee Model

Opcode-based (EIP-1559)

Prioritization fee (localized)

Account-based (parallel discount)

Predicate-based (UTXO)

Wasm opcode-based

State Growth Solution

State expiry (proposed)

State compression (light clients)

State sync via Waypoint

Stateless validation via UTXOs

IBC for interchain state

Time to Finality (approx.)

12-15 sec (L1)

< 1 sec

2-3 sec

~2 sec (on Fuel)

6-7 sec (Cosmos Hub)

Max Theoretical TPS (L1)

~30

65,000+

160,000+ (Sui, theoretical)

Unlimited (theoretical)

~10,000 (theoretical)

Native Account Abstraction

ERC-4337 (Bundlers)

Not native (programs as AA)

Native (via Move's signer)

Native (predicate-based)

Not native (requires custom)

Major Ecosystem Backers

Ethereum Foundation

Solana Foundation

a16z, FTX Ventures (historic)

Fuel Labs

Interchain Foundation

deep-dive
THE INFRASTRUCTURE TRAP

The Real Cost: Tooling Debt and Security Fragmentation

The proliferation of execution environments creates unsustainable overhead for developers and dilutes security for users.

Tooling debt compounds exponentially. Each new environment (Arbitrum, zkSync, Optimism) requires its own SDK, block explorer, and indexer, forcing teams like Uniswap to maintain parallel deployment pipelines.

Security is fragmented, not additive. A user's safety is now the weakest link across a dozen different proving systems and validator sets, unlike the singular security of Ethereum L1.

The interoperability tax is real. Moving assets between these environments via bridges like Across and LayerZero introduces new trust assumptions and failure points with every hop.

Evidence: The EVM ecosystem has one security model and toolchain. The multi-VM future has dozens, each requiring audits for its unique precompiles and state management.

counter-argument
THE EXECUTION LAYER

Steelman: Innovation Requires Breaking Compatibility

A defense of proliferating execution environments as a necessary, if messy, phase for discovering the optimal blockchain architecture.

The current EVM monoculture stifles architectural progress. Parallel execution, native account abstraction, and custom fee markets require breaking from Ethereum's sequential processing model, as seen in Solana, Aptos, and Monad.

Developer tooling and user experience fragment first to consolidate later. The initial chaos of multiple VMs (EVM, SVM, MoveVM) forces the creation of superior, portable frameworks like Foundry and Anchor, which eventually raise the bar for all chains.

Interoperability standards emerge from competition, not design-by-committee. The fight for liquidity between rollups and alt-L1s is what actually drives robust bridging solutions like LayerZero and Wormhole, not theoretical specs.

Evidence: The EVM's dominance is a historical accident, not an optimal design. Its 256-bit architecture and storage model incur significant overhead, a tax that new environments like the FuelVM are built to eliminate.

case-study
THE INTEGRATION TAX

Case Studies: The Integration Tax in Action

Every new execution environment forces developers to pay a hidden cost in security audits, liquidity fragmentation, and user experience complexity.

01

The Solidity Monoculture Problem

EVM's dominance created a single, high-security audit surface. The proliferation of new VMs (Move, FuelVM, SVM) fragments this. Each new environment requires a complete re-audit of core logic, multiplying costs and attack surfaces for cross-chain protocols like LayerZero and Axelar.

  • Security Tax: A $1M EVM audit becomes a $3M+ multi-VM audit suite.
  • Liquidity Fragmentation: Native assets on new VMs suffer from >90% lower initial DEX liquidity than their bridged counterparts.
  • Developer Friction: Teams must master Rust, Move, and Solidity to deploy universally.
3x
Audit Cost
90%
Less Liquidity
02

Intent-Based Architectures as a Solution

Protocols like UniswapX and CowSwap abstract execution away from specific VMs. Users submit intent ("I want this token"), and a solver network finds the best path across any chain or VM, paying the integration tax once on behalf of all users.

  • Integration Burden Shift: Solvers internalize the complexity of bridging across EVM, SVM, and Move-based chains.
  • Unified Liquidity: Aggregates fragmented pools, offering users ~5-15% better effective yields.
  • Future-Proofing: New VMs are integrated at the solver level, not the application layer.
15%
Better Yield
1
Integration Point
03

The Modular Stack's Hidden Cost

Choosing a Celestia DA layer, an EigenLayer AVS, and an Arbitrum rollup seems optimally modular. In practice, each component's unique proving system and light client creates a combinatorial integration nightmare. Bridging assets between two such custom stacks can require 4+ separate trust assumptions and custom messaging layers.

  • Exponential Complexity: N modular components create N² integration points.
  • Time-to-Market Killers: Prototyping a cross-VM dApp can take 6-12 months longer than a single-chain equivalent.
  • VC Blind Spot: The "best-in-class" stack often has the worst composite user experience.
N²
Complexity
12mo
Delay
04

The Appchain Fallacy: Sui & Aptos

Move-based chains Sui and Aptos promised a superior VM but created a walled garden. To access $10B+ of Ethereum DeFi liquidity, projects must build and secure custom bridges, a cost passed to users as >100 bps higher swap fees. This is the integration tax levied on every user transaction.

  • Capital Efficiency Tax: Native assets are stranded, forcing reliance on high-fee canonical bridges.
  • Security Subsidy: Users implicitly pay for the bridge's $500K+ audit and insurance fund via fees.
  • Adoption Ceiling: The tax creates a hard ceiling on TVL for native applications.
100+ bps
Fee Tax
$500K
Security Cost
future-outlook
THE CONSOLIDATION

The Path Forward: Standardization Layers, Not More VMs

The proliferation of execution environments fragments liquidity and developer attention, demanding a shift towards shared standards over isolated innovation.

The proliferation of execution environments fragments liquidity and developer attention. Each new VM like Arbitrum Stylus, Fuel, or a zkVM creates a new silo, forcing developers to choose ecosystems rather than architectures.

Standardization layers like the EVM are the real scaling solution. The EVM's dominance proves that a common runtime environment is more valuable than marginal performance gains from a novel VM that lacks tooling.

The future is shared precompiles and RISC-V cores. Projects like Polygon's zkEVM and Scroll succeed by preserving EVM equivalence, while efforts like the Ethereum Object Format (EOF) upgrade the core without fracturing it.

Evidence: Over 95% of TVL and developer activity resides on EVM-compatible chains. Non-EVM chains like Solana and Sui succeed despite this, but their growth is an exception that proves the rule of network effects.

takeaways
EXECUTION ENVIRONMENTS

Key Takeaways for Builders and Investors

The proliferation of execution layers is a feature, not a bug, but it demands a strategic approach to avoid fragmentation and capture value.

01

The Problem: Fragmented Liquidity and User Experience

Every new environment (EVM, SVM, MoveVM, CosmWasm) creates its own liquidity silo and developer tooling. This scatters capital and forces users to manage multiple wallets and bridges.

  • User Drop-off: Each hop between environments incurs a ~10-30% user drop-off.
  • Capital Inefficiency: TVL is trapped, reducing composability and yield opportunities.
  • Integration Hell: Builders must deploy and maintain across multiple VMs, increasing overhead.
10-30%
User Drop-off
5-10x
Dev Overhead
02

The Solution: Universal Settlement & Intent-Based Routing

Abstract the VM choice from the user. Let settlement layers (like Ethereum, Celestia) provide finality, while specialized execution layers compete on performance. Use intents and solvers (like UniswapX, CowSwap, Across) to route users optimally.

  • Unified Liquidity: Solvers aggregate liquidity across all environments.
  • Best Execution: Users get the optimal route (cost/speed) without manual management.
  • Future-Proofing: New VMs plug into the intent network without fracturing the front-end.
~500ms
Optimal Route
$10B+
Aggregated TVL
03

The Investment Thesis: Bet on Interoperability Primitives

The value accrual will shift from monolithic L1s to the protocols that connect them. Focus on cross-VM messaging (LayerZero, Wormhole), shared sequencing (Espresso, Astria), and generalized proving (Risc Zero, Succinct).

  • Protocol Revenue: Messaging fees scale with cross-environment activity.
  • Infrastructure Moats: These are harder to fork than a single app-chain.
  • Necessary Component: Every multi-chain future requires these building blocks.
1000+
Chains Connected
>50%
Msg Growth
04

The Builders' Playbook: Niche Domination Over Generalization

Don't build another general-purpose EVM chain. Instead, own a specific vertical with a tailored VM. Think dYdX on Cosmos for trading, or a zkVM chain for fully on-chain games. Depth beats breadth.

  • Superior Performance: A custom VM can optimize for a specific workload (~100x faster for target ops).
  • Stronger Community: Attract dedicated users and developers in a focused niche.
  • Sustainable Moats: Harder for generalists to compete on your specialized turf.
100x
Niche Perf
-90%
Bloat
05

The Hidden Risk: Security and Prover Centralization

New VMs, especially zkVMs, introduce new trust assumptions. The security of a zkRollup depends entirely on its prover network and the honesty of its sequencer. A few centralized provers become a systemic risk.

  • Single Point of Failure: A dominant prover can censor or extract MEV.
  • Opaque Costs: Proving costs are volatile and can make economic models untenable.
  • Audit Complexity: Novel VMs have less battle-tested cryptography and larger attack surfaces.
1-3
Major Provers
$$$
Audit Cost
06

The Endgame: Execution as a Commodity, Sovereignty as a Service

Execution will become a cheap, standardized service. The real value shifts to sovereignty—control over your stack, community, and revenue. Rollup-as-a-Service (RaaS) providers like Caldera, AltLayer, and Conduit enable this by abstracting deployment complexity.

  • Faster Time-to-Market: Launch a custom chain in weeks, not years.
  • Revenue Capture: Apps keep 100% of sequencer fees and MEV.
  • Composable Security: Choose your data availability layer (Ethereum, Celestia, Avail) and prover.
<4 Weeks
Chain Launch
100%
Fee Capture
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 Directly to Engineering Team
Execution Environment Proliferation: Fragmentation vs. Innovation | ChainScore Blog