How Much Liquidity Should You Add to Your Token?

How much liquidity should you add at token generation?

We put the day-one float somewhere in the region of 7 to 12% of supply, with the exact point inside that band decided by how much real demand the book shows rather than by a target headline valuation. Below roughly 6 to 7%, in our assessment, a token lands back in the low-float high-FDV cohort and inherits the price behaviour that comes with it. Below 5 to 6% the problem compounds, because the unlock schedule required to climb from there to a normal float tends to break supply-shock thresholds at the cliffs: every later tranche is large relative to what actually trades.

An illustrative set of numbers makes the arithmetic visible. Take a 1B supply token listed at $0.05. That prints a $50M FDV, but with only 100M circulating the real day-one market cap is $5M. The $5M is the figure the order book has to absorb against, and it is the figure every later unlock gets measured against. Sizing the float and sizing the depth that sits around it are the same decision taken twice, which is why we prefer to settle both together rather than fix the float first and discover the liquidity requirement afterwards.

The same illustrative cap table shows why one float number pulls different holders in opposite directions. Seed money in at $0.01, fully vested at month 42 against 600M circulating, breaks even at a $6M market cap. Public money in at $0.05, fully vested at month 18 against 300M circulating, needs $15M. The later, lower-risk capital carries the higher breakeven bar and reaches it first. On our reading that loads the heaviest motivated selling into the earlier part of the schedule rather than into the long-dated cliffs where teams tend to expect it.

Where inside the band a launch sits, we treat as a question the demand evidence answers. A book that fills firmly at the top supports the upper end of the range and the depth that has to be funded alongside it; a book that fills thinly supports the lower end and a smaller headline valuation, a trade-off worth working through alongside how the launch gets priced in the first place. The failure mode we see most often is a float chosen to produce a particular FDV, with the unlock curve reverse-engineered afterwards and the supply-shock problem discovered at the first cliff.

Not investment advice.

How does your FDV decide the liquidity bar you need to clear?

FDV sets the bar because the unlock schedule is denominated in it: a fixed percentage of supply releasing each month is a larger notional at a higher valuation, and the book on the other side has to absorb that notional. We treat launch FDV as something determined by that arithmetic rather than by what the last round implies or what comparable tickers are printing. To put the mechanism in illustrative terms, every additional 10M of FDV raises what each month's unlocks have to clear, and a higher headline number does nothing to add the bid that clears it.

Working backwards from the schedule is the step teams skip. The month carrying the largest cliff, priced at the FDV under discussion, produces a notional figure, and that figure is what venues and the market maker stand against for as long as the release runs. Where the depth available at launch cannot plausibly take that flow without the price gapping, we would call the FDV wrong before anything else is wrong, and no liquidity budget repairs it after the fact. Pricing the launch and sizing liquidity are one decision viewed from two ends.

The second discipline is planning at the base case and treating upside as upside. A model that assumes volume arrives and holds yields a liquidity plan that only functions in the scenario where it was never needed; a model built on quiet conditions yields one that holds in both. Teams who set FDV against the optimistic path tend to fund the gap out of treasury in exactly the months when treasury is least able to fund anything.

Sequencing follows from that. The unlock calendar is fixed first, the per month notional is derived from it, and the FDV is chosen so the heaviest of those months is something the launch book can take. The liquidity figure then falls out of that number, which is a different conversation from negotiating a liquidity figure against an FDV already announced to investors.

Not investment advice.

How much does listing on a major exchange cost in liquidity commitments?

A tier-1 listing stack, counting deposits and market-making requirements together, runs from roughly 400k to 1.5M or more. Public benchmarks put the listing component alone at around 500k for Binance, 1.5M for Bybit, 300k for Gate and about 110k for MEXC, and those figures sit before any market-making capital or obligations are layered on top. The gap between the headline listing number and the all-in number is where most budgets break.

Bybit is the clearest illustration of how the second layer works. Spot listings there carry a 200k to 300k stablecoin security deposit, refundable only if promotional obligations are completed, which means the capital is locked and contingent rather than spent. Its Token Splash programme also excludes the EEA, so a European issuer prices the same listing without the distribution mechanism that partly justifies the ask. We treat that as a straightforward reduction in what the venue is actually delivering, not a footnote.

The discipline we apply is cost basis. A venue asking for a large token allocation on top of fees has to deliver distribution that justifies it, and when the allocation is big while the real distribution is thin, the maths does not work however strong the brand. That comparison is easier to run once the market-making side is quoted separately from the listing side, since the two get bundled in conversation and then disappear into one number nobody can audit. Structuring the market-making engagement before committing to the venue tends to surface what each party is really being paid for.

What follows from a stack priced this way is sequencing. An issuer with a fixed budget chooses between one tier-1 venue with a seven-figure combined ask and several smaller venues at a fraction of that, and the liquidity obligation attached to each venue continues after the listing week, month after month, whether or not volume arrives.

Not investment advice.

Does market-maker inventory count as the liquidity you're adding?

Market-maker inventory is not part of the liquidity a project adds. It is a loan of tokens to a counterparty, repayable at the end of the term, and we think it belongs on the supply schedule as a loan rather than inside the pool figure a team quotes when it describes how deep its market is. The tokens sit with the desk, the desk decides moment to moment how much of that inventory is actually quoted, and that is a different thing from capital a treasury has committed to a venue.

We design the seat as a tokenomics input rather than something bolted on in the weeks before listing. In practice that means the inventory is drawn from a dedicated liquidity reserve and never from a marketing pool. Funding a desk out of marketing is the version of this that goes wrong most often in what we see: the same pool gets counted once as growth spend and once as the loan, and when the inventory is returned at the end of the term there is no line it belongs to, so it surfaces as unexplained supply in a wallet that community trackers are already watching. A reserve that exists for the purpose absorbs the return without creating a disclosure problem.

Disclosing the loan separately also keeps the float conversation accurate. Borrowed inventory has not been sold, it is not team allocation, and it is not liquidity the treasury paid for, so collapsing it into any of those three lines overstates one of them. The structure of the deal matters here too, because whether the desk is compensated through options on that inventory or through a flat retainer changes who benefits from the price path over the term, something we have set out in more detail on loan plus options versus retainer arrangements.

When we take a market making seat, the inventory line is sized against the same reserve the pooled liquidity comes from, so a team can state the pool, the loan and the remaining reserve balance as three figures that do not overlap. What follows from that is a dated return: the loan matures, the inventory goes back to the reserve, and the schedule has to say in advance what the reserve does with it on that date.

Not investment advice.

Should you add more liquidity if market conditions are weak right now?

No. Weak conditions are a pricing problem, not a depth problem, and the lever we reach for first is the launch FDV. Because the liquidity bar scales with the valuation a token opens at, cutting FDV cuts the amount of capital that has to stand behind the book, while piling on extra depth at an unchanged valuation only funds a larger defence of a number the tape is not supporting.

Delay is the other instinct, and we think it is the weaker one. Postponing a launch does not move a project to a market with better conditions, it moves the launch to a date whose tape is equally unknown, with a longer runway burned and investor and community expectations held open in the meantime. Our position is that valuation cannot fight prevailing conditions, so the honest response to a thin market is to meet it at a price rather than to wait for it to come back to the price that was modelled in better weeks.

What happens when a team does the opposite is fairly mechanical. Depth deployed to hold a valuation the market disagrees with gets consumed by sell flow at that level, and the capital that was meant to keep spreads tight for months is spent in the first weeks absorbing inventory. The project ends up with both a lower price and less liquidity than if it had opened lower, which is one of the ways launches run out of liquidity in the first place.

The practical sequence we work through with teams facing a soft tape is to reset FDV first, then size the book against the new number, then take that revised commitment back to the venues and the market maker before terms are signed. A lower opening valuation changes what the float is worth, which changes what a credible two sided book costs, and those revisions have to land in the same conversation rather than being bolted on after listing terms are agreed.

Not investment advice.

How much of your launch liquidity should be hedged?

The hedge belongs on locked and vesting tokens, not on the liquidity already sitting in pools or with a market maker, so for most teams the answer is that launch liquidity itself is not the thing being hedged at all. Tokens deployed into a pool or handed to a market maker as inventory are working positions with their own risk profile. The exposure worth hedging is the part of the supply a team cannot touch yet and cannot sell into a bid: founder and investor allocations still inside their cliff, ecosystem tranches that release on a schedule.

We treat the decision as case by case at TGE rather than a standing policy. The shape of the vesting calendar, the depth of the venue where the token trades and whether a perp exists at all change the answer from one launch to the next. Where there is a liquid perpetual market on the token, that is the instrument we would work with, because it prices continuously and can be sized against a known release date. Where there is no liquid perp, we would rather call the exposure unhedged than manufacture a substitute that introduces counterparty risk in place of price risk.

The constraint we hold hardest is that the hedge never runs past the vesting schedule. A short that outlives the tokens it was meant to offset stops being a hedge and becomes a directional position on a team's own asset, funded by the treasury, at exactly the moment the treasury has the least flexibility. Sizing against the schedule means the hedge steps down as each tranche releases and the underlying becomes sellable, rather than sitting on the book at a constant notional while the locked balance shrinks beneath it. The same logic applies to the question of whether a treasury should carry its own token in the first place, which we have written about in more detail in our piece on holding a treasury in your own token.

What this leaves at launch is a fairly narrow mandate: identify the locked balance, match it to dates, check whether a perp with real depth exists on that name, and let the hedge expire as the cliff clears. Teams that come to TGE without a written vesting calendar cannot do the first step, which is usually where the conversation stalls before any instrument gets chosen.

Not investment advice.