DocsLaunching
How launching works
Every coin gets its own Meteora settings, two transactions you approve once, and nothing counts until Solana confirms it.
Figures on this page are read from this server's own settings and data when the page loads.Every coin gets its own Meteora settings
Every coin launched on Blank gets its own Meteora Dynamic Bonding Curve config: a small settings account on Solana that fixes how the coin trades for its whole life. The server builds it from the options you chose and Blank's fee policy. Nothing has to be set up in advance, and no coin shares settings with another.
- Fee per trade
- 1%, split as shown in Fees
- Supply and decimals
- The amounts you chose; every coin is created at launch
- Creator lock
- Your locked allocation and its unlock schedule, if you chose one
- Graduation threshold
- The SOL the curve must hold before the coin graduates
- Metadata authority
- Locked forever, or editable by your wallet
- Fee claimer
- FyEZCa…dpdXPHThe wallet that can collect Blank's share of fees. It is a recipient only and can never move your coins.
Two transactions, one approval
On Solana a launch is two transactions. Your wallet shows them in one prompt, and you approve them together.
Create the coin's settings account
Signed by your wallet and by a new key your browser makes for the settings account.Create the coin and its pool
The mint, its metadata and the bonding curve pool, and your optional first buy. Your wallet becomes the coin's update authority, so it can change the name, ticker and image later. Signed by your wallet and by a new key your browser makes for the mint.
Blank sends the first, waits until it is confirmed, reads the settings account back and checks every field against what it built. Only then does it send the second.
What you sign, and what Blank never does
- Your wallet pays and owns the pool. It is the fee payer and the pool's creator, so creator fees, if any, can only ever be claimed by it.
- The new keys are made in your browser. Only their public addresses go to Blank's server.
- The server builds, checks and relays. It never signs. It holds no private key, adds no signature and cannot move anything in your wallet.
- Tested before you see it. On Solana, the server simulates both transactions first. If your wallet is short of SOL, or Meteora would refuse a setting, you are told before anything is signed.
- Checked after you sign. Each signed transaction must hash to exactly what the server built. A changed transaction is refused and never sent.
What a launch costs
A launch costs network rent and fees, paid by your wallet. Blank charges no launch fee.
- Settings account rent
- 0.00597408 SOLKept by the settings account for the coin's life. Not refundable.
- Pool, mint, vaults and metadata rent
- 0.01058164 SOL
- Metaplex metadata fee
- 0.01 SOLCharged by the Metaplex program, not by Blank.
- Network fees
- 0.00002 SOLFour signatures: your wallet twice, plus the two keys made in your browser.
- Priority fee
- 0.0000066 SOL20,000 micro-lamports per compute unit, at most 330,000 units.
- Total without a first buy
- 0.01533264 SOL
- With a 1 SOL first buy
- 0.01533264 SOLThe first buy plus the account that holds your new coins.
These are the rent and fee amounts measured on Solana. On a real network the server also simulates your exact transactions before you sign and shows that figure in the review step.
When a coin counts as launched
Blank never shows a launch as done until the network says so. A coin counts as launched only when all of this reads back from the chain:
- the pool exists, with your wallet as its creator, the new mint and the coin's own settings account;
- the settings account matches what was built, field by field: fee claimer, fee, creator share, supply, decimals, lock, metadata authority, liquidity split and graduation threshold;
- the mint has no mint authority and no freeze authority, and the metadata authority is what you chose.
Each step shows a real signature with a link to the explorer for its network.
If a launch stops halfway
If the first transaction landed and the second did not (you rejected it, or it expired), the launch can be resumed. Building it again returns only the second transaction against the settings account that already exists, so its rent is not paid twice.
If neither landed, nothing happened and nothing was spent. A launch that never reaches the network expires after 30 minutes; start a new one when you are ready.