Launch a token
The four-step wizard: your token, its config, an optional dev buy, then review and deploy.
Open Launch. The wizard has four steps and a live preview beside them (below them on phones) that shows your board card, your token page and the fee schedule as you fill it in. Nothing is signed until the last step, and you can go back to any step you have reached.
1. Token
| Field | Rules |
|---|---|
| Name | Required, up to 32 characters. |
| Ticker | Required, 2–10 letters or digits. It is upper-cased, and a leading $ and other characters are dropped. BRICK and lookalikes such as BR1CK are reserved for BrickPad's own $BRICK. |
| Image | Required: PNG, JPG, GIF or WebP, up to 2 MB. Square works best. |
| Description | Optional, up to 500 characters. |
| Links | Optional X, Telegram and website links, as full https:// addresses. |
Choose carefully
2. Config
Pick the launch config your pool is created from: BrickPad Standard (selected by default), another registered BrickPad config, or Custom config to set your own anti-sniper schedule and market caps. The fee split, the graduation to Meteora and the locked liquidity are the same on every config. See Launch configs.
3. Dev buy
Optionally buy your own token in the launch transaction, before anyone else can trade, at the 2% minimum fee instead of the anti-sniper fee. The step quotes exactly how many tokens you get. With a dev buy you can also lock those tokens for a set time, so buyers know you cannot sell them early. See Dev buy.
4. Review and deploy
The review lists your token, config, dev buy and lock, each with an edit link, and what the launch costs:
- Rent and network fees
- about 0.03 SOL
- A new config (custom settings only)
- about 0.006 SOL more
- Dev buy
- the amount you chose, if any
- Dev buy lock
- about 0.005 SOL rent, if you lock it
- BrickPad launch fee
- none
Press Deploy and the wizard ticks off a checklist as it goes:
- Upload metadata: your image and token details are stored and get a metadata link.
- Approve in wallet: one approval. On an existing config that is a single transaction; with a custom config it is two (the config, then the pool), signed together.
- Create config: only when your custom settings need a new config.
- Create token and pool: the mint, its DBC pool and your dev buy, in one transaction.
- Lock the dev buy: only when you chose a lock. Once the launch has landed, one more approval locks the tokens your dev buy got.
If the pool step fails after a new config landed, a retry reuses that config and the uploaded metadata, so you do not pay for them twice.
After launch
- Open your token page from the wizard. The token shows up on the board with a New badge.
- Share the contract address (CA) from the token page header: it is the one sure way for people to find your token.
- Every trade earns you half of the trading fee after Meteora's share. Claim it on Rewards.