SyncSwap Keeps ZKsync at the Center of Its Liquidity

As of September 11, 2026, SyncSwap remained a ZKsync-first exchange: its Era deployment processed $5.87 million in spot volume over the trailing 30 days. That represented roughly 70% of SyncSwap’s $8.38 million in cross-chain volume for the same window, according to DefiLlama’s on-chain event aggregation.

The same snapshot placed $6.30 million of the protocol’s $8.78 million total value locked on ZKsync Era, a 71.8% share. Those figures describe capital and completed swaps, not trader motivation; they cannot establish whether the flow came from discretionary users, arbitrage bots or incentive-driven positioning.

What does SyncSwap do on ZKsync?

It gives ZKsync users an automated market maker whose routing can draw from several pool designs rather than forcing every asset pair through one pricing curve. The architecture documented by Syncswap separates pool creation, registration and fee management, allowing the exchange to tune execution for different assets while retaining a common router.

• Classic pools use the constant-product formula associated with general-purpose token trading.
• Stable pools use a hybrid curve intended to reduce slippage between closely priced assets.
• Aqua pools apply a dynamic hybrid curve with automatic rebalancing for volatile assets and liquid-staking tokens.
• Pool Master registers pools and exposes current fee settings through a replaceable Fee Manager.

ZKsync changes the cost envelope rather than the economic bargain. Traders still pay swap fees and price impact; liquidity providers still earn fees while accepting inventory risk and impermanent loss. The rollup can lower execution costs, but its fees also incorporate the cost of publishing data to Ethereum.

Liquidity still clusters on Era

SyncSwap’s aggregate TVL rose 5.5% over the preceding 30 days, yet the September 11 distribution remained concentrated: ZKsync held $6.30 million, versus $1.55 million on Linea, about $910,000 on Scroll and $16,000 on Sophon. Era’s trailing volume was about 93% of its point-in-time TVL, a rough turnover comparison rather than a measure of executable depth.

DefiLlama recorded $12,415 in ZKsync fees and $3,700 in protocol revenue over that 30-day window. Its published volume method sums Swap events from Classic and Stable pools and values the core-asset side. Aqua activity is not identified in that coverage description, so the total may not capture every venue available through the router.

Who gains from the pool design?

No counterparty wins in every market regime. Stable-asset traders benefit when a specialized curve concentrates liquidity near parity. Volatile-pair traders gain if Aqua’s rebalancing keeps capital near the active price, while providers trade greater capital efficiency for more active inventory exposure. Arbitrageurs connect those pools with outside markets, correcting price gaps but extracting value when quotes lag.

The recorded transactions show that assets changed hands and fees accrued. They do not prove that users preferred ZKsync for security, incentives or execution quality. Pool-level reserves, realized slippage and wallet-level flow classification would be needed to separate those explanations.

The unresolved test is usable depth

SyncSwap remains meaningful infrastructure for ZKsync because most of its capital and measured trading still reside there. The verdict is narrower than dominance: $6.30 million can support routine swaps, but TVL alone does not guarantee tight execution during volatility. The next evidence to watch is pool-level depth, Aqua-event coverage, weekly fee retention and whether Era volume grows faster than deposited liquidity without temporary rewards.