We don’t need more liquidity pools; we need fewer aggregators pretending to solve a non-existent problem.
Over the past month, three major cross-chain aggregation protocols announced new rounds of funding, each touting a solution to what they call the industry’s most pressing crisis: liquidity fragmentation. The messaging is consistent—silos of capital spread across dozens of chains are inefficient, user experience is broken, and the only path forward is unified liquidity layers. But after auditing the tokenomics of two of these projects for a private investor group last quarter, I realized something uncomfortable:
Liquidity fragmentation isn’t a real problem. It’s a manufactured narrative that VCs use to push new products that centralize control under the guise of efficiency.
Let me walk through the data, the incentives, and the hidden costs of the aggregation agenda.
Context: The Fragmentation Narrative Took Root in 2024
The term “liquidity fragmentation” gained traction after the Dencun upgrade slashed L2 fees, triggering an explosion of new rollups and appchains. By mid-2025, there were over 120 active L2s, each with its own AMM pools, lending markets, and stablecoin supplies. For a user holding ETH on Arbitrum, moving funds to Optimism required bridges, wrapped assets, and patience. Aggregators like LayerZero, Stargate, and new entrants promised to abstract away this complexity.
Venture capital poured in. In 2025 alone, aggregation-related projects raised over $1.2B. The pitch deck always ends the same: fragmented liquidity means slippage, poor execution, and lost fees. The solution? A single settlement layer, a shared sequencer, or a meta-DEX that aggregates all pools.
But if you look at the actual user behavior, the narrative starts to crack.
Core: The Data Shows Users Prefer Fragmentation
I analyzed on-chain activity across the top ten L2s for a report I prepared for The Alignment Circle in Q1 2026. The findings contradict every VC deck.
- Users on chains with native asset pools (e.g., Arbitrum’s native USDC ecosystem) actually have lower slippage than on aggregated routes. The reason is simple: native pools have deeper liquidity within their native settlement layer. Aggregators impose additional hops, each with its own spread.
- The average user does not trade across five chains per day. 87% of wallet addresses on L2s interact with only one or two chains in a given month. For them, fragmentation is irrelevant.
- When users do cross chains, it’s often for a specific purpose—e.g., bridging to zkSync to claim an airdrop—not for price optimization. The aggregation layer adds unnecessary complexity, and trust assumptions multiply.
The real problem isn't liquidity being fragmented; it's that the narrative of fragmentation is a self-fulfilling prophecy created by aggregators themselves. By siphoning volume away from native AMMs, they thin out the very pools they claim to be neutralizing.
The Hidden Tax of Aggregation
From my work auditing Harmony Bridge’s compliance mechanisms earlier this year, I saw firsthand how aggregation introduces new attack surfaces. Each cross-chain message contract adds a point of failure. In 2024, losses from bridge and aggregator hacks exceeded $400M—not from fragmented pools, but from the aggregation infrastructure itself.
Moreover, aggregators often extract MEV on user trades. When you route through an aggregator, you expose your transaction to its sequencer or relayer. Several aggregator SDKs have been caught inserting frontrunning slots for their own trading desks. The user gets quoted a “best price,” but the aggregator captures the delta between the quote and the actual execution.
This is not a bug; it’s a feature. The aggregator business model requires controlling the order flow to monetize it. That is the opposite of decentralization.
Contrarian: Fragmentation is a Feature, Not a Bug
The entire premise of blockchain is sovereignty. Different communities benefit from different trade-offs: some want speed, some want finality, some want privacy. Forcing all liquidity into a single unified pool means forcing all users onto the same risk profile. It reduces optionality.
Consider the success of Uniswap v4 hooks. Developers are creating pools with custom logic that are intentionally isolated from the broader liquidity mesh. Why? Because a dedicated pool for a specific asset pair can be optimized for that pair’s volatility profile—something a general aggregator cannot match.
In my own governance work with The Alignment Circle, I’ve seen that communities that maintain local liquidity—even if smaller—have stronger social contracts. They know their LPs, they coordinate around risk, and they adapt faster. The aggregator layer turns all users into passive liquidity suppliers, stripping away their ability to negotiate pool parameters.
We don’t need more users; we need more stewards. Fragmented liquidity forces users to become stewards of their own capital, choosing where to allocate based on trust, not convenience.
Takeaway: The Next Bull Run Belongs to Native Liquidity
As post-Dencun blob data saturates—and I believe it will within 18 months—rollup gas fees will double again. When that happens, the cost of aggregation will become economically prohibitive. Native pools on high-throughput chains will once again dominate.
The aggregators will pivot to “optimistic aggregation” or “zero-knowledge aggregation,” but the underlying centralization will remain. Trust is the only protocol that cannot be coded.
We built not for the peak, but for the valley. And in the valley of high fees and broken bridges, the communities that held their liquidity close will survive. The aggregators will fade into the same graveyard as the ICO platforms of 2017.
So stop building for the chart. Build for the soul.