The payment token determines the units of the market: purchases, fees, reserve and graduation target.
Default and alternate presets
The default preset completes at 15,000 CAPX net reserve. The alternate preset completes at 50,000,000 units of the selected eligible token. The current custom preset supports the required six-decimal Token-2022 configuration; it is not an arbitrary-token listing feature.
The service checks supported graduated markets, including eligible successful legacy launches. The interface pins CAPX and applies a $25,000 market-cap filter to discoverable candidates. That selector filter is distinct from underlying eligibility.
Choosing a payment token changes the economic denomination of the launch. A buyer must hold that asset, a seller receives it, and reserve progress is measured in it. Start with the audience and the intended market relationship, then verify the exact mint. An appealing name or a visible selector entry is not a substitute for understanding the asset being used.
First use can need setup
A payment token without a matching configuration can require a separate setup transaction and rent before launch creation. Subsequent launches can reuse the configuration. If the setup completes and the creator cancels the launch, the setup remains; the two wallet actions are separate.
An optional Dev Buy uses the selected payment token. Check that asset’s mint, the current launch estimate, purchase amount, fees and slippage before signing. The reviewed creation estimate is 0.045 SOL including a 0.03 SOL migration reserve; use the live quote for the amount that applies.
Read the wallet requests as separate commitments. The setup request establishes a reusable configuration; the creation request launches this particular token. If you stop between them, the completed setup has still happened. Keeping the two outcomes separate makes it easier to understand a retry, a cancellation or a later launch using the same payment asset.
Native units are not dollars
Two markets can show the same native price and have very different USD values because their payment tokens have different prices. USD comparisons need the actual quote asset’s conversion source and freshness. A 50,000,000-unit graduation target is not a $50,000,000 target.
For a purely illustrative example, suppose a token costs 0.04 units of its quote asset and one quote unit is worth $0.25. Its converted price is $0.01. Multiplying the native price by a supply figure first produces a valuation in quote-token units. That amount becomes a USD valuation only after the correct quote conversion is applied.
The display should preserve this distinction even when conversion data is missing. Name the payment token, identify the conversion source and make its freshness visible. A dollar sign cannot supply a missing conversion, and a number in CAPX or another token should not silently become a dollar figure.