L2 Liquidity Landscape: Capital Flow from OP Stack to Base
Over the past six months, stablecoin and ETH migration between major L2s has tilted clearly toward Base. We unpack the incentive structure behind the flow.
— K. Chen
Zoom out to a 12-month view and the distribution of stablecoins across L2s is being redrawn. The pre-2025 "OP Stack first, everyone else second" picture has cracked — Arbitrum still holds the TVL crown, but the marginal flow has tilted markedly toward Base.
Base's growth is not incentive-driven — no airdrop, no sequencer-fee rebate. It pulls capital through two channels: Coinbase's on-ramp (USDC moves on with near-zero friction) and the compounding effect of meme and social-asset liquidity on DEXs. It is a clean sample of "app layer attracts users, app layer retains capital".
For an infrastructure layer like F* Protocol the L2 spread is an engineering reality — FundVault sits on Arbitrum Sepolia today because Arbitrum is still the L2 institutions are most comfortable with, holds the largest TVL, and has the most mature bridge tooling. But "follow the user's money" forces the protocol layer to take Base deployment paths seriously.
Arbitrum
INSTITUTIONAL DEFAULTThe default L2 for institutional capital · mature DeFi protocol set · deep bridge support. F* Protocol's current primary deployment.
Base
GROWTH ENGINEThe growth frontier for users and new assets · lowest USDC on-ramp friction · strongest app-layer compounding. F* evaluates a co-deployment in fund-vault v1.1.
Other OP Stack
FRAGMENTEDOptimism / Mode / Mantle share the same tech but fragmented liquidity · Superchain interop is needed to pool them coherently.
We tracked the migration of the major stablecoins (USDC, USDT, DAI, sUSDS, USDe) across five L2s over the past six months, matched against DEX 24-hour volume. The counter-intuitive finding: cross-chain stablecoin migration does not correlate strongly with native bridge fees — the dominant driver is the CEX-to-L2 on-ramp. Coinbase's zero-fee USDC channel into Base visibly accelerated stablecoin inflow into Base.
F* Protocol should not assume a single L2. EVM-generic contract code means the same fund-vault bytecode can be deployed to any L2 — but cross-chain Policy registry and cross-L2 NAV synchronisation need explicit engineering. That is on the v1.1 roadmap.
Data from L2Beat / Dune Analytics / DefiLlama / Coinbase public APIs. Full queries and dashboard links at fund-vault/research/l2-flow/.