There's no magic number for initial liquidity, but there is a right question: how big a buy should your pool absorb without punishing the buyer? Answer that, and the math hands you your number. This guide works through the sizing logic, the USDC-pairing specifics on Arc, and the launch-killing mistake of treating liquidity as a cost to minimize rather than the market you're building.
What does initial liquidity actually do?
Your pool is your market. In an AMM, the paired reserves — your token plus USDC — are the only thing trades execute against, and depth determines how violently each trade moves the price: a buy that's 1% of pool depth moves price gently; the same buy against a pool a tenth the size is a spike, followed by the mirror-image crash when someone sells. Thin liquidity therefore doesn't just inconvenience buyers with price impact — it manufactures the exact chart pattern (vertical pump, vertical dump) that reads as a scam, deters the next buyer, and hands early snipers outsized profits at your community's expense. Liquidity isn't a launch expense; it's the product's trading experience, and it's the first thing sophisticated buyers size up (it's on their checklist).
How do you size it?
Work backward from your expected buyer. Estimate a plausible early buy — not your dream whale, the ordinary enthusiastic buyer your marketing will actually produce — and decide the price impact you'll accept for them; a common comfort target is keeping a typical buy under 1–2% impact. As a rough AMM rule, a trade's price impact tracks its size relative to the pool's depth, so a $500 typical buy at ~1% impact implies roughly $25,000–50,000 of paired depth ($12,500–25,000 of USDC plus the token side). Sanity-check the result two ways: against your projected early market cap (seeded liquidity in the region of 10–20% of initial market cap is a widely used credibility band — far below that and the float is a facade), and against your community size (a thousand people who might buy $100 each need a pool that can absorb clusters of those buys in the same hour). These are reasoning bands, not laws — but a launch outside them should know why it is.
What's specific to Arc?
Three things, all favorable. Pairing is dollar-native: your pool pairs against USDC — the gas token and unit of account — so your liquidity commitment, your price, and your depth are all denominated in dollars with no gas-asset beta muddying the chart (why launches budget cleanly here). Infrastructure costs are rounding errors: pool creation and the liquidity lock cost cents plus flat USDC fees, so effectively 100% of your liquidity budget is depth rather than overhead. And concentrated liquidity is available day one: on Uniswap v3-style pools you can concentrate depth around the launch price range, making each USDC of liquidity do more work — with the trade-off that the position needs management as price moves, and it locks as a position NFT. For a first launch, a full-range position is the simpler, harder-to-mismanage default; concentration is an optimization for teams who understand it.
What are the non-negotiables around the number?
Whatever size you land on, three rules outrank it. Lock all of it, immediately: an unlocked pool of any size is worth less to buyers than a locked pool of half the size — depth measures trade quality, but the lock is what proves the depth will still exist tomorrow (lock in the same session you pool). Don't fake it: seeding thin and planning to "add later from trading fees" reads exactly as it is, and staged additions without published commitments get read as exit liquidity management. And if capital is genuinely the constraint, size the whole launch to the pool you can afford — a smaller, honest market cap with real depth outperforms an inflated one on a puddle, on any chain, and especially in front of Arc's verification-minded audience. If you need outside capital specifically to fund liquidity, that's the legitimate case for a structured raise (fair launch vs presale).
FAQ
What's the minimum liquidity to launch on Arc? Mechanically, almost anything — the pool costs cents to create. Practically, enough that your typical expected buy stays under a few percent of price impact; below that, the chart itself becomes your worst marketing.
Should liquidity be in USDC or my token? Both — an AMM pool is paired. You deposit both sides; the USDC side is the dollar commitment people quote when they talk about your "liquidity."
Is 10–20% of market cap in liquidity a rule? A widely used credibility band, not a law — useful as a sanity check. What buyers actually experience is depth versus their trade size; optimize for that.
Can I add more liquidity after launch? Yes, and deepening over time is healthy — announce it and lock the additions like the original. Only quiet removals are toxic; additions are good news worth claiming.
Does concentrated liquidity change how much I need? It makes each dollar of depth more effective near the current price, at the cost of management complexity. Sensible for experienced teams; full-range is the safer first-launch default.
Sized your pool? Create it, then lock it in the same session — Team Finance liquidity locks on Arc, flat USDC fees, proof in under a second.Open Team Finance →Sources: docs.arc.network, arc.io (chain economics); AMM sizing logic reflects standard industry practice. Verified August 2026.
Last verified: August 2026