How much liquidity to seed at launch
This number gets set by whatever budget was left over, which is how most tokens end up with a pool that punishes everyone who tries to use it. There is a way to derive it instead, and it takes about two minutes.
Work backwards from the buy
The usual approach is forwards: decide how much capital can be spared, put that in the pool, and find out afterwards what it supports. That produces a number with no relationship to anything and it is why so many launches end up with a pool that punishes participation.
The better method starts at the other end and takes about two minutes.
- Decide the largest buy you want to support comfortably. Not your best case: the ordinary upper end of what a genuinely interested person might send.
- Decide what movement is acceptable for that order. A percent or two is comfortable; several percent is the point where people size down or leave.
- Work out what depth produces that. On a constant product pool, impact is roughly the ratio of your order to the reserve on the side being bought, so the arithmetic is direct.
- Seed at least that. Anything less is a decision to make that buy unpleasant.
The output is a number you can defend, derived from the experience you want a buyer to have rather than from what happened to be available. The impact explainer covers why the relationship is not linear, which matters because doubling an order more than doubles the movement it causes.
The ratio that actually matters
Liquidity is frequently discussed as a ratio to market capitalisation, and the ratio is a useful sanity check as long as it is read correctly.
A valuation is a claim about what the token is worth. Liquidity is the capital available to act on that claim. When the second is very small relative to the first, the valuation is not supported by anything anyone can transact against, and that gap is visible to everyone in the form of price impact.
The practical version does not require a formula. Simulate a realistic buy against the pool you intend to seed and read the impact. If a modest order moves the price several percent while the token claims a substantial valuation, the ratio is wrong regardless of what any published guideline says, because the test measures the thing the ratio was a proxy for.
What happens at each level
| Depth relative to interest | What a buyer experiences | What the chart does |
|---|---|---|
| Very thin | Large impact on any order | Discrete steps, looks manipulated |
| Thin | Ordinary buys move price noticeably | Jagged, volatile on low volume |
| Adequate | Ordinary buys execute cleanly | Smooth, moves on real flow |
| Deep | Even large orders barely register | Stable, hard to move |
Most launches land in the top two rows and most teams intend the third. The gap is usually not a decision; it is the result of treating the pool as the last item on a budget rather than the first.
The bottom row has its own trade-off worth naming. A very deep pool is pleasant to trade and slow to move, which frustrates anyone hoping the price will run. That is a legitimate preference and it should be a deliberate choice rather than an accident, because it also means a large buyer can enter without the chart telling anyone.
Both sides, and what they mean
A pool holds two assets and the ratio between them sets the starting price. That gives you two levers at launch and they are frequently confused.
Seeding more of the paired asset relative to tokens sets a higher starting price. Seeding more tokens relative to the paired asset sets a lower one. The total value of both sides determines the depth; the ratio between them determines where trading starts.
The mistake worth avoiding is choosing a high starting price by seeding few tokens against little capital. That produces a token with an impressive headline valuation and a pool that cannot absorb anything, which is the configuration most likely to look like a deliberate setup even when it is only inexperience.
A worked example makes the arithmetic concrete. Suppose you want a 5 SOL buy to move the price by no more than about two percent. On a constant product pool that implies a SOL-side reserve in the region of a couple of hundred SOL, because impact tracks the ratio of the order to that reserve. If the capital available is a tenth of that, then the honest conclusion is not that the pool is slightly small; it is that a 5 SOL buy will move your price by a great deal and you should either raise the capital or lower the size of buyer you are designing for. Both are legitimate answers. Discovering it after launch is not.
Three expensive mistakes
Seeding whatever is left. The pool ends up sized by subtraction rather than by intent, and the number is uncorrelated with the buys it needs to support. This is the most common one by a wide margin.
Seeding thin deliberately to make the price move. It works once. The resulting chart is a vertical line followed by whatever happens when the first real seller arrives, and it is permanent. Every future evaluator sees it, and the liquidity guide covers why every subsequent campaign against that pool costs more for less.
Announcing before the pool exists. Attention arriving at a token with no market sends motivated people to a dead end at the exact moment they were most willing to act.
What to do after launch
The seeding decision is not permanent, and treating it as a single irreversible choice makes it more stressful than it needs to be.
Depth can be added later, and adding it is usually cheaper than any campaign you might run against a pool that is too thin. Depth can also be removed, which is why locking matters as a signal and why the timing of that lock is read carefully. If you intend to lock, doing it at seeding is stronger than doing it after a gap, because the gap is a window that anyone doing diligence will notice and ask about.
Two habits are worth keeping afterwards. Re-run the impact test periodically, because depth changes as trading moves the reserves and as other providers enter or leave. And check both directions each time, since a pool that started balanced can become asymmetric after a period of one-sided flow, at which point buys and sells stop behaving the same way. The launch checklist puts this in the order it belongs, which is before anything that costs money to promote.
Frequently asked questions
01How much liquidity should I add at launch?
Enough that the largest buy you realistically want to support moves the price by an acceptable amount. Work backwards from that order size rather than forwards from a budget, because the number that matters is the experience a buyer has and not the figure displayed on a screener.
02What is a good liquidity to market cap ratio?
Rather than a fixed ratio, use the impact test: if an ordinary buy moves the price more than a percent or two, the pool is thin relative to the valuation being claimed. A high valuation supported by a shallow pool is the configuration that produces jagged charts and disappointed buyers.
03Can I add liquidity later instead?
Yes, and many projects do. The cost of starting thin is that launch-day attention arrives against a pool that cannot absorb it, and launch-day attention is the one form of attention nobody has to pay for. Adding depth afterwards fixes the market and does not recover that.
04Does more liquidity mean less price movement?
Yes, in both directions, and that is the trade-off. A deep pool makes buying pleasant and also means the price rises less on the same buying. Teams hoping for dramatic early movement sometimes seed thin deliberately, which works exactly once and leaves a chart that argues against the token afterwards.
05What happens if I seed too much?
The capital is tied up and the price moves slowly. That is a real cost and it is recoverable, since liquidity can be withdrawn. It is a considerably better problem than seeding too little, where the damage lands on buyers and on the chart rather than on your balance sheet.
06Should the pool be locked from the start?
If you intend to lock at all, doing it immediately is stronger than doing it later, because a gap between seeding and locking is a window anyone performing diligence will notice. Publish the transaction rather than only announcing it.
Keep reading
Check what the pool can actually absorb
The console reads real depth for your mint, which is the number every other decision depends on.
Open the volume console