Shared Liquidity

What Is Shared Liquidity?

Shared liquidity is a design paradigm in which trading capital, token balances, or borrowable assets across multiple blockchains, rollups, or protocols are pooled or coordinated so they behave as a single unified reserve. Instead of each chain maintaining its own isolated liquidity pools, shared liquidity systems let users on any connected chain tap into the combined depth of all participating networks.

The concept emerged as a direct response to the multichain era. As Ethereum's rollup ecosystem grew to over 70 active Layer 2 networks and USDC deployed natively on 30+ chains, the same token's liquidity became scattered across dozens of independent venues. A $500K swap on any single chain would only hit that chain's thin pool, producing far worse execution than if the same trade could draw from aggregate depth across all chains. Shared liquidity aims to restore the efficiency of a single, deep market.

How It Works

There is no single mechanism for shared liquidity. Different protocols take fundamentally different architectural approaches, each with distinct trust assumptions and tradeoffs.

Intent-Based Bridges

Users sign declarative "intents" describing what they want (for example, "swap 1 ETH on Arbitrum for USDC on Base") rather than specifying exact execution paths. A competitive network of solvers races to fill these intents from any available liquidity source: on-chain AMMs, private inventory, centralized exchanges, or other chains entirely.

The user experiences execution as if all liquidity were unified, even though the underlying pools remain technically separate. The ERC-7683 cross-chain intent standard, co-authored by Uniswap Labs and Across Protocol and finalized in April 2026, provides a common interface for this pattern. It has been adopted by protocols including Across, UniswapX, and LI.FI, with support from the Ethereum Foundation's Open Intents Framework backed by 30+ teams.

Hub-and-Spoke Models

A central liquidity hub holds pooled assets, and individual "spokes" on different chains connect to it through cross-chain messaging. Users on any spoke can access the hub's full depth without manually bridging assets. Aave V4's Cross-Chain Liquidity Layer, which launched on Ethereum mainnet on June 30, 2026, uses this approach: users can collateralize assets on one chain and borrow on another, with Chainlink CCIP handling the cross-chain coordination.

Burn-and-Mint Models

Token issuers maintain a single canonical supply that can be transported across chains by burning on the source and minting on the destination. Circle's Cross-Chain Transfer Protocol (CCTP) V2 uses this approach for USDC: when a user transfers USDC from Ethereum to Base, the source tokens are burned, Circle's attestation service signs the burn event, and fresh native USDC is minted on the destination. Settlement completes in 8 to 20 seconds with no wrapped tokens and no pool-based slippage.

LayerZero's Omnichain Fungible Token (OFT) standard generalizes this pattern for any token. Issuers deploy OFT contracts across chains, and the standard handles burn-and-mint mechanics through LayerZero's messaging layer.

Aggregation Layers

Protocol-level infrastructure connects multiple chains through shared verification and settlement frameworks. Polygon's AggLayer uses ZK proof aggregation to connect L2s, rollups, and appchains into a unified network where connected chains share TVL automatically. Shared sequencers take a complementary approach: by ordering transactions for multiple rollups simultaneously, they enable atomic cross-rollup swaps that make liquidity pooling across rollups safe without traditional bridges.

Unified Liquidity Pools

Some protocols pool liquidity into a single contract rather than maintaining per-chain reserves. Across Protocol operates a unified liquidity pool on Ethereum mainnet: liquidity providers deposit into one pool, and relayers front capital on destination chains, getting reimbursed from the hub pool via UMA's optimistic oracle. This makes LP capital far more efficient than bridges requiring per-chain liquidity.

The Fragmentation Problem

Shared liquidity exists because multichain deployment creates structural inefficiency. When the same token trades on 30+ chains, each with its own AMM pools, the consequences compound:

• Worse execution for traders: a swap that would produce 0.01% slippage against a deep, unified pool might produce 1% or more against a thin, chain-specific pool
• Lower returns for LPs: fee revenue splits across competing pools, reducing yield per unit of capital deployed
• Cross-chain MEV extraction: arbitrageurs exploit price discrepancies across chains, with cross-venue spreads ranging from 0.3% to 5% compared to 0.01% to 0.15% on a single chain
• Developer burden: teams must deploy, maintain, and bootstrap liquidity on each chain separately

With over 47% of DeFi TVL having migrated away from Ethereum mainnet by early 2025 and cross-chain transaction volume reaching $56.1 billion in July 2025, fragmentation is not a theoretical concern: it is the defining infrastructure challenge of the multichain era.

Use Cases

Cross-Chain Trading

DEX aggregators and cross-chain swap platforms use shared liquidity to offer traders better prices by sourcing from multiple chains simultaneously. UniswapX achieves a 99.5% fill rate by letting solvers compete to fill orders from the best available source, whether that's an on-chain pool, private inventory, or another chain entirely.

Cross-Chain Lending

Lending protocols can let users collateralize on one chain and borrow on another without manual bridging. This eliminates the need for users to maintain positions across multiple chains and concentrates borrowable liquidity into deeper pools. Aave V4's hub-and-spoke model is the leading implementation of this pattern.

Stablecoin Transfers

Burn-and-mint models are particularly well suited to stablecoins, where the issuer controls the canonical supply. Circle's CCTP V2 enables near-instant USDC transfers across 13+ chains without wrapped tokens or liquidity pool dependencies. This approach eliminates slippage entirely for stablecoin transfers since no pool is traded against.

Netting-Based Settlement

Protocols like Everclear (formerly Connext) match opposing cross-chain flows to reduce redundant liquidity moves. If one user wants to move ETH from Arbitrum to Base while another wants to move ETH from Base to Arbitrum, the system nets these flows rather than executing two separate bridge transactions. This reduces capital requirements and settlement costs.

Shared Liquidity and Bitcoin

Bitcoin's architecture avoids native-asset fragmentation by design. Unlike Ethereum, where ETH exists separately on each rollup, Bitcoin has a single UTXO set on one chain. Spark preserves this property by transferring ownership of on-chain UTXOs through cryptographic key rotation in a 2-of-2 multisig (user plus a distributed operator set using FROST threshold signatures) rather than locking BTC into isolated L2 pools.

This means Spark does not create separate liquidity silos: all Spark BTC shares a single conceptual pool because transfers are key rotations on the same UTXO set, not movements between fragmented venues. Spark's native interoperability with the Lightning Network further ensures that Spark liquidity connects to the broader Bitcoin payment ecosystem rather than fragmenting it.

Risks and Considerations

Bridge and Messaging Risk

Most shared liquidity solutions depend on cross-chain bridges or messaging protocols to coordinate across chains. These introduce trust assumptions and attack surfaces: oracle failures, message verification bugs, or validator collusion can compromise the entire liquidity layer. Bridge exploits have historically accounted for some of the largest losses in DeFi.

Centralization Tradeoffs

Hub-and-spoke models concentrate liquidity and risk in a single hub. Burn-and-mint systems depend on a trusted issuer (the token creator) to attest to burns and authorize mints. Shared sequencers introduce a centralized ordering layer. Each approach trades some degree of decentralization for the efficiency gains of unified liquidity.

Solver and Relayer Dependence

Intent-based systems rely on competitive solver networks to provide good execution. If solver competition is insufficient (during periods of low activity or on less popular chains), users may receive worse prices than expected. Solver liveness failures can also delay order fulfillment.

Smart Contract Complexity

Shared liquidity protocols require complex cross-chain state management, including atomic settlement guarantees, dispute resolution, and timeout handling. Each additional chain increases the attack surface and the difficulty of maintaining consistent state across all connected networks.

Regulatory Uncertainty

Cross-chain liquidity coordination blurs jurisdictional boundaries. Protocols that pool assets across chains may face uncertain regulatory treatment, particularly regarding custody, money transmission, and travel rule compliance across different jurisdictions.

For a deeper look at how cross-chain intent standards are shaping shared liquidity infrastructure, see the research article on ERC-7683 cross-chain intents. For context on how stablecoin issuers approach multichain deployment, see stablecoin multi-chain deployment strategy.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.