Launch: How a coin arrives.

Explanation — not permission to act

Native reward issuance is admitted subject to fresh source, account, custody and cost gates. Standard is existing recovery only; new Pump and adoption admission are deferred.

The mechanics and diagram include historical specification design. Current gates and finalized evidence govern; configuration is not availability or execution proof.

The historical specification describes four arrival paths: StonkFun reward, standard, pump.fun new, and adoption. They are not four currently open launch routes. Native reward issuance itemizes service fees, network/rent and any optional personal buy; it requires no compulsory reserve purchase of the newly issued token. The separate COMPUTER holding prerequisite still applies. Chain confirmation and source adoption determine issuance success, not strategy activation. Applicable service-fee refunds need confirmed failure and reconciliation; network/rent are not refunded and successful issuance is irreversible. Previously funded reserve obligations keep their original recovery terms.

Historical arrival paths

Reward, standard, Pump and adoption are the four specification paths. A source being connected does not open admission.

Current issuance and legacy obligations

Use only the source offered by the current launch review. Old funded reserve obligations retain their original terms, not a new reserve-buy instruction.

Issuance is not strategy activation

A saved intent is not a mint. Confirmed issuance, metadata publication, source adoption and strategy funding or fills are separate evidence.

Reward thesis launch, from intent to confirmed source adoption.
  1. Intent

    One intent id per command; retries return the original result.

  2. Itemized charge

    Service fee, network/rent and optional personal buy recorded separately.

  3. Mint

    Initialize the reward token; an optional personal buy has its own reviewed limit.

  4. Adoption gate

    Launchpad, mode and tax checked; a miss marks the launch defective.

  5. Terminal state

    Adopted or defective, based on finalized chain and source evidence—not reserve holdings.

Practical next reading

Create a token · Resume a launch · Fund the native wallet

The numbers that bound it.

Live configuration is not embedded in this guide. No values are shown rather than guessed. Local settings are not chain, provider or release evidence. Spec defaults are not provider proof.

  • THESIS_TAX_BPS
  • LAUNCH_FEE_USD
  • LAUNCH_FEE_USD_PRO
  • LAUNCH_FEE_PLATFORM_USD
  • DEV_BUY_FEE_BPS

Platform spec reference

Historical source summaries, not a statement of current enforcement.

Applicability and precedence · §6 Launch layer · §27 Decision Ledger (v6.6.1) · §28 Financial Invariants Addendum (v6.6.2)