Concentrated Liquidity for a Token Launch: 7 Mistakes Teams Make and How to Fix Them

Launching a token on a concentrated liquidity pool (Uniswap v3 and the many AMMs built on the same design) lets you put your capital exactly where trading will happen, which means far more depth per dollar than a classic constant-product pool. It also means you can get it badly wrong in ways that a v2-style pool forgives. Choose the wrong range and your liquidity disappears the moment price moves. Initialise the price inverted and the pool opens at a nonsense valuation. Set it and forget it, and within days you may be providing no liquidity at all.

These are the seven mistakes we see most often when token teams seed their first concentrated liquidity pool, each with the fix. None of them requires exotic tooling. They require deciding things deliberately before launch rather than in the pool creation interface on the day.

How Concentrated Liquidity Changes the Launch Problem

In a constant-product pool, liquidity is spread across every possible price from zero to infinity. Most of it is never used, but the pool is always "in range". In a concentrated liquidity pool, each position covers a price range you choose. Inside that range, your capital provides much deeper liquidity than the same capital would in a v2 pool. Outside it, your position provides none, and it holds entirely one asset: all token if price falls below the range, all paired asset if price rises above it.

For a new token, that trade-off is the whole game. You do not know where price will settle, volatility in the first days is high, and the depth that matters most is near the current price. If you want a refresher on how AMMs price trades in the first place, start with automated market makers explained.

Mistake 1: A Range That Is Too Narrow

The problem. A tight range around the launch price looks great on paper: deep liquidity, tiny slippage, impressive charts in the first minutes. Then price moves a modest amount, which for a newly launched token is almost guaranteed, and the position falls out of range. Depth near the market vanishes. The next trades move price sharply because the only liquidity left is whatever happens to sit further out.

The fix. Size the range to the volatility you expect, not the volatility you hope for. For a launch, that usually means a materially wider range than you would use on an established pair, or several positions layered at different widths: a tighter one around the launch price for depth, and wider ones that keep the pool functional if price moves a long way in either direction. Accept that a wider range means less depth per dollar near mid.

Mistake 2: Initialising the Price Inverted

The problem. Concentrated liquidity pools order the two assets by contract address, not by which one you think of as "the token". Price is stored as the amount of the second asset per unit of the first. If your token's address sorts after the paired asset's, the price you need to enter is the inverse of what you expect. Teams that miss this create a pool that opens at a wildly wrong valuation, and arbitrage bots take the difference within a block.

The fix. Before launch, check which asset is token0 and which is token1 for your exact pair. Calculate the initial price in both directions and confirm the pool interface shows the one you intend, in the orientation you expect. Then do a dry run on a testnet or a fork with the real contracts. The pool's starting price is set once at creation and cannot be undone except by trading, so this is a mistake you cannot recover from cheaply. How you arrive at that price in the first place is covered in our guide on how to set a token listing price.

Mistake 3: Picking a Fee Tier by Habit

The problem. Uniswap v3 offers fixed fee tiers — 0.01%, 0.05%, 0.3% and 1% — and many forks follow a similar structure. Teams often choose the tier they recognise from major pairs, typically 0.3% or 0.05%. Those tiers are designed for pairs with relatively stable or well-arbitraged prices. A new, volatile token carries more risk for liquidity providers, and a low fee does not compensate for it.

The fix. For most new tokens paired against a major asset, a higher fee tier is the more common choice because it better compensates for volatility and adverse selection. Weigh it against your expected trading pattern: very high-frequency, small-size trading is more fee-sensitive than early holders building positions. Whatever you pick, pick one. Seeding the same pair across several fee tiers splits your depth and leaves every pool thinner than it needs to be, while routers and aggregators decide where flow goes.

Mistake 4: Ignoring the Single-Sided Launch Option

The problem. Many teams assume they must supply both the token and a large amount of the paired asset at launch. That ties up treasury capital and, if the range is placed around the current price, hands early buyers a pool of paired asset to sell into immediately.

The fix. A position placed entirely above the launch price holds only your token. As buyers arrive and price rises into the range, the position sells token for the paired asset gradually, on the way up. This single-sided structure is a common launch pattern because it requires little or no paired capital up front and makes price discovery work like an ascending ladder of offers. It has trade-offs: there is no paired-asset liquidity below the launch price, so early sellers face a thin market unless you add a separate position for that side. Decide explicitly how much downside liquidity you want and fund it on purpose.

Mistake 5: Locking a Position You Will Need to Move

The problem. Buyers expect launch liquidity to be locked, and teams respond by locking the position NFT for months or years. With a concentrated position, a lock also freezes the range. If price leaves that range, the locked liquidity is inert until the lock expires, and the pool looks locked but is not actually providing a market.

The fix. Separate credibility from management. Lock a core position with a deliberately wide range, wide enough to stay useful across a large price move, and keep narrower working positions in a disclosed multisig so they can be rebalanced. Our step-by-step guide to locking liquidity for a token launch covers the lock types and how to present the split to buyers.

Mistake 6: Set and Forget

The problem. A concentrated position is not passive. As price trends, the position drifts toward one asset and, eventually, out of range. Fees stop accruing, depth near the market thins, and the pool's quoted slippage on aggregators gets worse. Teams that seed the pool on launch day and do not revisit it for a week often find they have been effectively absent from their own market.

The fix. Define a rebalancing policy before launch: what triggers a range adjustment (price moving a set distance toward the edge, or out of range for a set time), who executes it, and from which wallet. Monitor in-range status, the composition of each position and depth within a few percent of price. Remember that every rebalance realises the current mix of assets, so frequent repositioning in a trending market can lock in losses. The mechanics of that drag are the same ones described in impermanent loss explained, amplified by the narrower range.

Mistake 7: Treating the DEX Pool in Isolation

The problem. Once a token trades on a centralised exchange as well, the DEX pool becomes one venue among several. If the DEX range and the CEX order book are managed by different people with different assumptions, arbitrage traders will close the gaps, using your pool as the cheap side of every trade. A narrow DEX range that falls out of sync with CEX prices is particularly expensive.

The fix. Manage DEX ranges and CEX books as one liquidity plan. Agree on a reference price, decide which venue leads price discovery, and keep DEX ranges positioned around where the combined market actually trades. If a market maker runs your CEX books, they should either manage the on-chain positions too or at least coordinate with whoever does.

Pre-Launch Concentrated Liquidity Checklist

Depth Is Designed, Not Defaulted

Concentrated liquidity is one of the most capital-efficient tools a token team has, but only if the ranges, fee tier and management plan are designed for a volatile new asset rather than copied from a mature pair. Most launch-day problems with these pools trace back to decisions that were made in a few clicks instead of in a plan.

Fibonacci Capital works with token teams on exactly this layer: launch pricing, on-chain liquidity structure, and market making that keeps DEX pools and CEX order books aligned from the first trade. If you are planning a DEX launch and want your liquidity design reviewed before it goes live, reach out through our pre-TGE programme.