Choose a starting price and liquidity layout
Choose total supply, opening valuation and quote asset before allocating liquidity. In the app, these become Supply, Opening market cap and the pool's quote. Start with one pool so you can inspect its full simulation before adding another.
1. Turn valuation into a token price
The launch's opening fully diluted valuation (FDV) is the opening token price multiplied by total minted supply, including tokens allocated to distant ranges. It is not cash raised or cash deposited: launch positions begin with only the new token.
price in USD per token = FDV in USD / total token supply
price in quote per token = price in USD per token / quote's USD priceFor the app's 1 billion Simple supply, a $15,000 target and an illustrative $2,500/WETH rate:
| Quantity | Calculation | Result before tick rounding |
|---|---|---|
| USD per token | $15,000 / 1,000,000,000 | $0.000015 |
| WETH per token | $0.000015 / $2,500 | 0.000000006 WETH |
| USDG per token, assuming $1/USDG | $0.000015 / $1 | 0.000015 USDG |
The wizard's default/minimum is $15,000, with $15K/$25K/$50K/$100K/custom choices. SDK examples instead use $5,000 through EXAMPLE_TARGET_MARKET_CAP_USD. With 1 million supply, that is $0.005/token, or about 0.00000201 WETH/token at an illustrative $2,486.49/WETH.
Neither default establishes a safe cap or protection against early buyers. With the same normalized liquidity shape, a higher opening valuation generally gives the same spend a smaller share of supply. Preview the intended buy size.
2. Check decimals, address order and rounding
A WETH quote uses 18 decimals; USDG uses 6. The launch token uses 18. The pool orders token0/token1 by numeric address: the lower address is token0. The SDK's confusingly named launchedTokenIsQuote / launched_token_is_quote is true when the launch token is token0.
For human quote-per-launch-token price q, launch decimals dL and quote decimals dQ:
raw quote units per launch unit = q * 10^(dQ - dL)
raw token1/token0 ratio = that value if launch token is token0, otherwise its reciprocal
sqrtPriceX96 = floor(sqrt(raw token1/token0 ratio) * 2^96)Use deriveLaunchPoolRecipe / derive_launch_pool_recipe to align the opening to the pool's tick grid. Rounding can change the implied FDV. This pure Python example prices 1 million tokens against a $1, six-decimal quote and allocates half the supply to that pool:
from black_market_sdk import derive_launch_pool_recipe
recipe = derive_launch_pool_recipe(
paired_token_decimals=6,
paired_token_usd_price_x18=10**18,
target_market_cap_usd_x18=5_000 * 10**18,
launched_token_is_quote=True,
fee=3_000,
supply=1_000_000 * 10**18,
token_budget=500_000 * 10**18,
)
print(recipe.launch_tick, recipe.tick_lower, recipe.tick_upper)The output is -329280 -329280 887220. Its aligned FDV is about $5,014.95, not exactly $5,000. Reversing the address orientation gives opening tick 329280 and range [-887220, 329280]. These ticks belong to this supply, quote decimals and fee spacing; do not copy them into a WETH pool.
For canonical Abyss pools, the fee grid is:
| Trading fee | Fee pips | Tick spacing |
|---|---|---|
| 0.01% | 100 | 1 |
| 0.05% | 500 | 10 |
| 0.30% | 3,000 | 60 |
| 1% | 10,000 | 200 |
| 2% | 20,000 | 400 |
| 5% | 50,000 | 1,000 |
| 10% | 100,000 | 2,000 |
| 15% | 150,000 | 3,000 |
V4 has its own configured spacing. A zero LP fee does not mean zero tick spacing. Show the aligned opening price and FDV, using the current quote/USD observation, before signing.
3. Split inventory, not valuation
For a 1 billion supply at $15,000 FDV, a two-pool allocation could be:
| Pool | Token budget | Opening quote price at the illustrative rates above |
|---|---|---|
| WETH | 700,000,000 tokens (70%) | 0.000000006 WETH/token |
| USDG | 300,000,000 tokens (30%) | 0.000015 USDG/token |
| Total | 1,000,000,000 tokens | One $15,000 valuation |
Each pool values the whole supply at $15,000; the two FDVs do not add to $30,000. Advanced uses one shared valuation and converts it into each quote. The low-level /launch/multi editor and SDK can set prices independently; mismatched quote/USD seeds can invite immediate arbitrage.
Market budgets must sum to supply, and position caps must sum to each market budget. Tokens left after integer mint rounding are burned before opening buys, not paid to a creator reserve. Adding pools divides the same inventory and adds setup work.
4. Cover the buying path through the boundary
A position supplies liquidity only within its range. At launch, every position must require zero quote deposit. For launch token0, ranges start at or above the opening tick and buying moves upward. For launch token1, ranges end at or below opening and buying moves downward.
The SDK's default admission for a new market requires:
- Positive buy-side liquidity at opening.
- Aligned tick boundaries and valid nonzero liquidity.
- Continuous coverage from opening in the buying direction; adjacent and overlapping ranges both work.
- At least one funded range reaching the highest usable price, the finite protocol tick boundary. The SDK calls this the permanent tail.
The boundary-reaching range stops the price from running past the last liquidity; it is not a price forecast or unlimited depth. Extend the range that starts at the opening, not a high band or a separate tail position. A token-only range from tick a holds 1.0001^((a - t) / 2) of its tokens above tick t, so a range that starts at the opening has almost nothing left at very high ticks, while a separate range starting near the top holds its whole allocation there. Use the app's liquidity profiles, or SDK deriveLaunchPositionRanges / derive_launch_position_ranges. For SDK early-scarcity and staircase recipes, choose positionGaps: "adjacent" / position_gaps="adjacent" to satisfy default admission; keep the final range extended to the boundary. App Layered is a different algorithm from SDK early-scarcity, staircase and smooth-ramp.
Read the Simple Layered layout
At 1% / spacing 200, the six-position Simple Layered shape for a 1 billion-token pool is:
| Position | Share of pool | Start (ticks above opening) | End |
|---|---|---|---|
| 1 | 18.04% | 0 | Maximum tick |
| 2 | 17.90% | 24,400 | 111,000 |
| 3 | 17.65% | 48,800 | 111,000 |
| 4 | 16.74% | 73,200 | 111,000 |
| 5 | 12.47% | 97,600 | 111,000 |
| 6 | 17.20% | 84,000 | 157,000 |
Ticks count in the quote-per-token price direction; for a launch token1 the raw ticks decrease. For scale, from an unrounded $15,000 opening the starts correspond to roughly $15,000 / $172,075 / $1.97M / $22.6M / $260M, tick 84,000 to about $67M, tick 111,000 to about $1B and tick 157,000 to about $98B. These are range endpoints, not expected prices or cash balances.
This layout opens like the published Layered curve: the first $1,000 buys about 4.9% of supply, about 11% is sold by $100,000 and half by about $28M. Position 6 holds the supply that used to sit in a tail above ~$3B, so a $100,000 buy at a $1B market cap still moves the price only about 0.4%, and effectively no supply remains above $100B. Advanced uses eight positions on the same pattern. When a Simple Uniswap launch must drop to 4, 3 or 2 positions to fit one transaction, the ranges widen but the early distribution stays the same; native Abyss keeps six. Even spread and Higher ground follow the same structure with adjacent bands.
Contract geometry and SDK admission are different
A contract-valid token-only layout can contain interior gaps or stop short of the boundary. The SDK rejects those layouts by default. For unstarted plans, allowTopologyGaps / allow_topology_gaps permits interior gaps; allowMissingPermanentTail / allow_missing_permanent_tail waives the tail requirement. Neither waives opening coverage, grid alignment or token-only geometry. These options do not change an already-begun plan.
5. Review the opening buy as a share of supply
Simulate buys in their committed order, through the exact ranges and fees. Review spend, token output, output / total supply, average execution price, final spot price and gas. A small smoke buy says little about a $100 or $1,000 buy. A buy comparable to the opening quote-denominated FDV can acquire a large part of the supply.
For example, a simulated 10,000,000-token output from 1 billion supply is 1%. At 50 bps slippage, the committed minimum is 9,950,000 tokens:
minTokenOut = floor(simulated token output * (10000 - buySlippageBps) / 10000)buySlippageBps / buy_slippage_bps needs activation inside the proven simulation prefix. A conversion minimum protects the ETH→quote swap, not the later quote→launch-token buy. A minimum of 1 wei offers effectively no token-buy protection. Do not remove the minimum just to make an unproven activation proceed.
After checking the aligned prices, budget sums, final positions and buy minima, review wallet steps and launch.
Reference: plan limits
The lifecycle supports at most 16 markets, 32 total positions, 64 ordered buys, eight funding entries and eight fee assets. Fee assets include the launch token and every quote, leaving at most seven distinct quotes. V4 allows one market per quote; canonical Abyss market identities cannot repeat.
Ticks lie within [-887272, 887272], narrowed to usable multiples of the selected spacing. Position liquidity must fit a positive signed 128-bit amount and per-tick limits, with rounded token debits below its cap. These are geometry and schema limits, not a guarantee that activation fits gas. See the TypeScript or Python reference for codec and profile-specific limits.
For the ordinary fixed V4 profile, spacing is 1–32,767 and LP/hook rates are each below 1,000,000 pips; 10,000 pips is 1%. Its oracle configuration must be registered, with capacity 2–4,096. The standard menu is P1 (1, 4096), P2 (6, 4096) and P3 (17, 4096): maximum absolute recorded tick move and observation capacity. A newly initialized pool still has new history; capacity is not elapsed history.