Interoperability is a commodity. Its value accrues to the applications and assets that use it, not the bridge itself. This is why Across, Stargate, and LayerZero compete on fees and speed, not unique technology.
Why Interoperability is a Feature, Not a Product
The future of user-centric blockchain is smart accounts. This analysis argues that cross-chain interoperability will be commoditized as a core feature of this infrastructure, rendering standalone interoperability products obsolete for most applications.
The Interoperability Mirage
Interoperability is a foundational feature that fails as a standalone business model, destined to be commoditized and absorbed by application-layer primitives.
The product is the application. Successful protocols like UniswapX and CowSwap embed cross-chain intents directly into their swap flow. The bridge is an invisible, replaceable component, not the user-facing product.
The end-state is standardization. Just as TCP/IP became a free baseline, cross-chain messaging will be a protocol-level primitive. Rollup stacks like Arbitrum Orbit and OP Stack are already baking in native bridging, making standalone bridges redundant for their ecosystems.
The Three Forces Killing Standalone Interop
Standalone interoperability protocols are being commoditized and absorbed by dominant applications and infrastructure layers.
The Appchain Thesis: Sovereignty Over Convenience
Major ecosystems like Cosmos, Polygon Supernets, and Arbitrum Orbit are baking native, secure interop into their SDKs. The value accrues to the appchain's token and ecosystem, not a standalone bridge.\n- Native Security: Validator sets double as bridge attestors, eliminating third-party trust.\n- Economic Capture: Fees and MEV from cross-chain flows stay within the sovereign ecosystem.
The Aggregator War: UniswapX & The Intent Paradigm
Frontends are abstracting the bridge away. Users express an intent ("swap ETH for SOL"), and solvers compete across liquidity venues and bridges to fulfill it. The best bridge is a hidden implementation detail.\n- User Abstraction: No bridge selection, no gas management on destination chain.\n- Liquidity Fragmentation: Aggregators like CowSwap and 1inch split orders across multiple bridges (LayerZero, Across, CCIP), commoditizing the underlying transport layer.
The L2 Stack Monopoly: Native Bridges as a Primitve
Every major L2 (Optimism, Arbitrum, zkSync) ships with a canonical, upgradeable bridge controlled by its multisig/DAO. It's a mandatory, non-negotiable primitive for security and fund recovery. Third-party bridges are permissionless add-ons that compete on marginal speed or cost, not core security.\n- Security Floor: The canonical bridge sets the base trust assumption for all assets.\n- Commoditized Competition: Fast withdrawal bridges like Hop and Across compete on a thin margin over the native primitive.
From Product to Protocol Primitive
Interoperability's value lies not as a standalone product but as an embedded, commoditized primitive within the protocol stack.
Interoperability is a feature. It is a utility, like a database, that protocols integrate rather than a product users seek. The winner-takes-most dynamics of liquidity and security make standalone bridges unsustainable long-term.
The market demands embedded interoperability. Protocols like UniswapX and CowSwap abstract cross-chain complexity into a user intent. This shifts competition from bridge UX to the quality of the underlying execution layer.
LayerZero and CCIP are becoming infrastructure. Their role mirrors AWS for web2: a foundational service that enables higher-level applications, not the end-user product itself. The protocol primitive absorbs the value.
Evidence: The 2023-24 trend shows bridge volumes consolidating into a few generalized messaging layers (LayerZero, Wormhole, Axelar), while application-specific intents (Across, Socket) capture user-facing innovation.
The Feature vs. Product Dichotomy
Comparing standalone interoperability protocols against integrated infrastructure features, highlighting the economic and technical trade-offs for builders.
| Core Metric / Capability | Standalone Product (e.g., LayerZero, Axelar) | Integrated Feature (e.g., Chainlink CCIP, Hyperlane) | Native L1/L2 Bridge |
|---|---|---|---|
Primary Revenue Model | Direct user/application fees | Infrastructure subscription / value capture | Sequencer fee capture / MEV |
Time to Integrate for App | 2-4 weeks (SDK, audits) | < 1 week (pre-audited modules) | N/A (native to chain) |
Capital Efficiency (Liquidity) | Requires external liquidity pools | Uses canonical asset pools or atomic swaps | Uses canonical mint/burn |
Security Model | External validator set (often permissioned) | Hybrid (decentralized oracles + fallback) | Native chain consensus |
Protocol Overhead (Annual Cost) | $500K - $5M+ in token incentives | Priced into base infra cost (~$0) | Priced into base chain security |
Sovereignty / Customization | High (configurable security, gas) | Moderate (within infra framework) | None (fixed by chain rules) |
Cross-Chain State Access | True (via generic messaging) | True (via pre-built adapters) | False (asset-only) |
The Bridge Builder's Rebuttal (And Why It's Wrong)
Bridges are a commodity feature, not a sustainable standalone business, because their value accrues to the applications they connect.
Bridges are infrastructure commodities. Their core function—moving assets—is a solved, low-margin utility. The real value is in the liquidity and applications they enable, not the pipe itself.
Value accrues to the endpoints. A user bridges to use Uniswap on Arbitrum, not to use the bridge. Protocols like Across and Stargate compete on fees and speed, a race to zero.
The winning model is embedded. Interoperability succeeds as a feature baked into apps. UniswapX and CowSwap abstract bridging away, making the bridge an invisible, replaceable component.
Evidence: LayerZero's omnichain future depends on apps built atop it. Its valuation assumes it becomes the default plumbing, a bet that the feature itself can be a moat.
Who's Building the Future (Feature, Not Product)
Interoperability is being commoditized into a foundational layer, shifting the battleground to user experience and application-specific logic.
The Problem: Fragmented User Journeys
Users must manually bridge assets, manage multiple wallets, and navigate different chain UIs for a single transaction. This kills UX and fragments liquidity.
- Cost: Up to 5-10x the gas fees for a multi-chain swap.
- Time: Manual steps add minutes to a process that should take seconds.
- Risk: Each manual step is a new attack surface for user error.
The Solution: Intents & Abstracted Execution
Let users declare what they want, not how to do it. Protocols like UniswapX and CowSwap use solvers to find the optimal path across chains and liquidity sources.
- Key Benefit: User gets the best outcome without managing complexity.
- Key Benefit: Native cross-chain swaps without manual bridging.
- Key Benefit: MEV protection via batch auctions and private order flows.
The Problem: Security vs. Speed Trade-off
Native bridges are slow but secure. Third-party bridges are fast but introduce new trust assumptions (e.g., multisigs). LayerZero and Axelar offer generalized messaging but with distinct security models.
- Risk: Over $2B+ stolen from bridge hacks.
- Dilemma: Choose between ~15 min optimistic windows or instant but federated verification.
The Solution: Modular Security & Shared Networks
Decouple security from speed. Across uses optimistic verification topped by a bonded relay for instant guarantees. Chainlink CCIP leverages its oracle network's cryptoeconomic security.
- Key Benefit: Capital efficiency via unified security layers (e.g., EigenLayer AVS).
- Key Benefit: Configurable security per application risk profile.
- Key Benefit: Shared cost across many applications reduces fees.
The Problem: Liquidity Silos
TVL is trapped on individual chains. Moving it is expensive and creates arbitrage opportunities that users pay for. Wormhole and Circle's CCTP tackle stablecoins, but generalized assets remain fragmented.
- Impact: $10B+ in bridged assets still represents a fraction of total DeFi TVL.
- Inefficiency: Liquidity pools are duplicated, not unified.
The Solution: Universal Liquidity Layers
Treat all chains as execution environments with a single liquidity backend. LayerZero's Omnichain Fungible Tokens (OFT) and Axelar GMP enable native assets to move seamlessly.
- Key Benefit: Native yield accrues on the canonical asset, not a wrapped derivative.
- Key Benefit: Atomic composability across chains for complex DeFi strategies.
- Key Benefit: Eliminates bridge token risk, reducing systemic fragility.
The Bear Case: Where This Thesis Fails
The promise of seamless cross-chain communication is compelling, but building a standalone business on it faces existential challenges.
The Commoditization Trap
Interoperability infrastructure is rapidly becoming a low-margin commodity. The value accrues to the applications that use it, not the pipes themselves.\n- LayerZero and Axelar compete on price and security, driving fees toward zero.\n- Major L1/L2s like Arbitrum, Optimism, and Polygon are building native bridges, making third-party solutions redundant.\n- The endgame is interoperability as a cheap, bundled feature within larger stacks like EigenLayer or Celestia.
The Security Moat is an Illusion
No interoperability solution has achieved credible, battle-tested neutrality without centralized trust assumptions. Security is the primary bottleneck.\n- Wormhole and LayerZero rely on off-chain validator sets, creating centralization risks.\n- Native validation (like IBC) is secure but imposes heavy integration costs and chain-specific constraints.\n- The industry is converging on shared security models (e.g., EigenLayer AVS), turning security into a rentable resource, not a proprietary moat.
Application-Layer Abstraction
End users don't care about bridges; they care about asset availability. Wallets and major DEXs are abstracting interoperability away.\n- UniswapX and CowSwap use intents and solvers, making the bridge an invisible backend service.\n- Metamask and Rabby integrate multiple bridges, routing for best price/security.\n- The winning interoperability 'product' will be the one that disappears, becoming a seamless SDK for apps like Aave or Lido.
The Modular Stack Consolidation
In a modular world, interoperability is a standard interface between specialized layers, not a standalone network. Value capture shifts to settlement and data availability.\n- Rollups interoperate via their shared settlement layer (e.g., Ethereum L1) or DA layer (e.g., Celestia).\n- Projects like Polygon AggLayer and Cosmos 2.0 are building interoperability as a native layer-0 property.\n- This leaves generic message bridges as a thin, replaceable middleware with no pricing power.
The 2025 Landscape: Invisible Interoperability
Interoperability is shifting from a standalone product into a foundational feature, abstracted away from end-users and developers.
Interoperability is infrastructure. Users do not buy routers; they buy internet access. In 2025, protocols like UniswapX and CowSwap treat cross-chain liquidity as a utility, not a destination. The intent-based architecture of these systems abstracts the bridging mechanics away from the user.
The product is the application. A standalone bridge like Across or LayerZero is a tool for developers, not a consumer brand. The value accrues to the dApp that integrates it seamlessly, making the chain boundary irrelevant for the end-user experience.
Modularity drives commoditization. With standards like IBC and generalized messaging layers, the differentiation collapses to cost and latency. This turns interoperability into a low-margin, high-volume utility, similar to AWS's data transfer pricing.
Evidence: UniswapX processed over $7B in volume by routing orders across chains without user-side bridging. This proves the demand is for the swap, not the bridge.
TL;DR for Busy Builders
Stop building bridges to nowhere. The winning strategy is embedding seamless cross-chain logic into your core product.
The Liquidity Silos Problem
Your dApp's TVL is trapped on a single chain, missing the $100B+ in assets scattered across Ethereum L2s, Solana, and Avalanche. Native bridging UX is a conversion funnel killer.
- Key Benefit: Access fragmented liquidity without user friction.
- Key Benefit: Unlock composability with protocols like Uniswap, Aave, and Curve on any chain.
Intent-Based Architectures (UniswapX, CowSwap)
Users don't want to manage bridges; they want outcomes. Let solvers compete across chains via intent standards. This abstracts away the settlement layer.
- Key Benefit: Better prices via cross-chain liquidity competition.
- Key Benefit: Gasless, non-custodial user experience.
The Shared Security Fallacy
Building a new validator set for your bridge is a $50M+ security budget black hole. Rely on battle-tested messaging layers like LayerZero, Axelar, or Chainlink CCIP as a feature, not your product's core.
- Key Benefit: Inherit security from Ethereum or other established networks.
- Key Benefit: Focus dev resources on application logic, not consensus.
Modular Interoperability Stack
Interoperability is a stack: settlement, messaging, liquidity. Use Celestia for data, EigenLayer for shared security, and Across for bonded liquidity. Compose, don't rebuild.
- Key Benefit: 10x faster time-to-market for new chain deployments.
- Key Benefit: Future-proof against next-gen VMs and DA layers.
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.