Launches

Creating a launch

A launch needs a name, a symbol, an image, and its money settings. Creating it does not start it — nothing is spent until you press Start.

The settings

Setting	Default	What it does
Wallet count	15	Total wallets: 1 dev + the rest as buy wallets. Range 10–20.
Dev buy	0.05 SOL	What the creator wallet buys inside the create transaction.
Per-wallet funding	0.02 SOL	SOL sent to each buy wallet. It spends most of this, keeping a small fee reserve.
Minimum buy	0.005 SOL	Floor for each wallet's randomised buy amount.

Above 13 wallets the extra buys fall outside the protected bundle — see how the bundle works before raising it.

Statuses

Status	Meaning
`draft`	Created, nothing spent. Safe to delete or edit.
`funding`	Wallets generated, SOL on its way to them.
`launching`	Token being created and bought.
`bought`	You hold the token. Waiting for you, or for an auto-sell trigger.
`selling`	Wallets are exiting.
`sold`	Exited and swept home.
`failed`	Something went wrong. Often retryable — the tokens or SOL are still in the wallets.

The live log

Progress streams over a websocket into the launch's log as it happens: each wallet generated, the funding transaction, the create, how many buys landed and over how many slots. The connection is authenticated with your login token and joins a private room, so the only events you receive are your own.

Per-user limits

Each account has a ceiling on launches in flight at once (2 by default) and on queued tokens (50). They exist so one user cannot monopolise the shared RPC budget on a server other people are using. An admin can raise them per account.