Docs
Everything about change: how a launch is built onchain, what every parameter does, how trading, fees and graduation work, and how to check any launch yourself.
How change works
change is a launchpad on Solana. Every token launched here gets its own Meteora Dynamic Bonding Curve (DBC) pool with a configuration you choose, and graduates into a Meteora DAMM v2 pool whose liquidity is locked forever. change does not run its own trading program: buys, sells, fee claims and migration all execute in Meteora's audited programs. change builds the transactions, shows you exactly what they will do, and reads everything back from chain.
The life of a token
- Launch. One transaction creates a fresh config account with your parameters, a new SPL token mint with your metadata, and the bonding-curve pool. Mint and freeze authority are revoked in the same transaction, so supply is fixed from the first block.
- Trading on the curve. Anyone can buy (SOL in, tokens out) or sell (tokens in, SOL out) against the curve. The price rises as SOL accumulates. Every swap pays the launch fee, which can start high and decay over time.
- Graduation. When the SOL raised reaches the graduation threshold, the curve closes. Meteora's migrator moves the raised SOL and the reserved share of supply into a DAMM v2 pool and locks 100% of its liquidity permanently.
- After graduation. The token trades in its DAMM v2 pool (and through aggregators like Jupiter). The creator and the platform keep earning their share of that pool's fees through their locked LP positions; nobody can withdraw the liquidity.
What is fixed and what you choose
A few things are the same for every launch because they protect buyers: fixed supply, no mint or freeze authority, immutable metadata, no discounted first swap, SOL pricing, migration to DAMM v2 and 100% locked liquidity. Everything else, from supply and decimals to the curve shape, fee schedule, revenue split and creator vesting, is a typed setting you control. See Safety rules and All launch parameters.
Receipts instead of promises
Every launch has a public receipt rebuilt from chain data: the config account, the pool, the mint and the metadata account are read directly and checked against the safety rules. The receipt also shows the sha256 hash of the raw config account so anyone can verify it independently. See Verifying a launch.
Getting started
Wallets
Connect with the button at the bottom of the side panel. Phantom, Solflare, Backpack and any wallet that supports the Wallet Standard and versioned transactions work. change never sees your keys; every transaction is signed in your wallet.
How much SOL you need
- Launching: about 0.027 SOL for account rent and network fees, plus anything you buy afterwards.
- Buying: the amount you spend plus about 0.01 SOL kept back for fees; the first buy of a token also opens its token account (about 0.002 SOL of rent, refundable if you close it).
- Claiming fees: only the network fee. If a claim opens a temporary account, change closes it in the same transaction.
Where things are
Paste any token mint address into the search box at the top of the side panel to jump straight to its page.
Launching: token details
Name, ticker, logo, description and links. All of it is written once and can never change.
Logo
Choose a PNG, JPEG, WebP or GIF (up to 15 MB, at least 64 px on its shortest side). A cropper opens: drag to position, scroll or type a zoom from 100% to 800%, or type exact pixel offsets. The result is a square up to 512 px, compressed to WebP or JPEG under 95 KB so it fits Arweave's free permanent storage. Small square animated GIFs can be kept as they are.
Name and ticker
- Name: up to 32 bytes (emoji and accented letters use more than one byte). Extra spaces are collapsed.
- Ticker: up to 10 characters. A leading $ is removed, spaces are dropped and it is upper-cased.
Description and links
The description (up to 600 characters), website, X and Telegram links are optional. They go into the token's metadata JSON alongside the logo, and that JSON is stored permanently on Arweave (or IPFS if the deployment uses Pinata). The onchain metadata account points to it and is marked immutable, so double-check spelling before you sign.
Launching: supply and decimals
Total supply is the fixed number of tokens that will ever exist (1,000,000 to 100,000,000,000). Type it in full or use shorthand: 1b, 250m, 10k. Decimals (6 to 9) set how finely a token can be divided; 6 is the common choice.
Onchain, amounts are stored in base units: supply × 10decimals. That number must fit in 64 bits (about 1.8 × 1019), so very large supplies need fewer decimals. The form tells you when a combination is too large.
Where the supply goes
There is never any leftover: the config is built so these parts add up to exactly the total supply.
Launching: the bonding curve
How the price moves from the first buy to graduation.
The curve decides the price at every point between launch and graduation. You can define it in one of two ways; both produce a Meteora curve made of constant-product segments, and the launch page shows the exact result in a table: SOL raised, progress, price, market cap in SOL and USD, and the price change between rows.
Shape by SOL raised
- Graduate at (5 to 2,000 SOL, to 0.01): how much SOL the curve collects before it graduates. Default 85 SOL.
- Supply into graduated pool (5% to 80%): the share of supply reserved for the DAMM v2 pool. The rest is sold on the curve. A larger pool share means fewer tokens sold on the curve for the same SOL, so a higher graduation price.
Shape by market caps
- Starting market cap (1 to 100,000 SOL) and graduation market cap (up to 10,000,000 SOL).
- The graduation market cap must be at least 1.5× the starting one. The SOL needed to graduate is then derived from the two.
How the end of the curve works
Buys use Meteora's partial-fill swap. If a buy would push past the graduation threshold, only the part that fits is used and the rest of your SOL stays in your wallet. Once the threshold is reached the curve accepts no more trades and waits for migration.
Some extreme combinations (for example 100B supply with a 2,000 SOL raise and an 80% pool share) overflow the curve math. The form explains the problem and will not let you launch it.
Launching: the launch fee schedule
A trading fee that can start high and fall over time. High early fees make sniping in the first seconds expensive.
The schedule is computed the way the program computes it
The fee table on the launch page comes from the same config the transaction will create, using Meteora's own period math, so every step is the exact fee the program will charge. Exponential decay is rounded onchain, so the last step can land a fraction away from your typed ending fee (for example 100.22 bps instead of 100).
Flat fee
Set the starting and ending fee to the same value, or the decay time to 0, for a single fee that never changes.
The fee clock
Fees are charged by the Solana cluster's clock, not your computer's. change quotes every trade using the chain's own block time, so quotes during the fast-falling first minute match what the program charges.
Launching: revenue and liquidity
Who earns what from trading on the curve and after graduation.
Trading fee split
Meteora always takes 20% of every trading fee. The remaining 80% is split between you and the platform by creator share of trading fees (0 to 100%). At 50%, each fee splits creator 40% / platform 40% / Meteora 20%.
Locked LP after graduation
At graduation the DAMM v2 position is split into two permanently locked positions. Creator share of locked LP (0 to 100%) decides how much of it is yours. Locked means nobody, including you, can ever withdraw the liquidity; what you own is the right to claim that position's share of the pool's trading fees, forever.
Graduation fee
An optional fee of 0 to 50% of the raised SOL, taken at graduation before the pool is created. Creator share of graduation fee splits it between you and the platform. With 0% the full raise goes into the pool.
Graduated pool fee
The fee tier of the DAMM v2 pool after graduation: 25 bps, 30 bps, 100 bps, 200 bps, 400 bps, 600 bps. These are Meteora's fixed migration configs, so only these values are accepted.
Launching: creator allocation
Optionally reserve part of the supply for yourself, locked and vesting.
The allocation is minted into Meteora's locker program when the curve graduates (graduation does this step first if there is an allocation). Each receipt shows the allocation and its schedule, and it is visible to every buyer before they trade.
Withdrawing unlocked allocation is done through Meteora's locker. A withdraw button inside change is planned.
Launching: presets and raw config
Presets
Presets only fill in fields; you can change anything afterwards.
Raw config
The bottom of the launch form shows the whole configuration as JSON. Edit it and press Apply (or Ctrl+Enter). Unknown keys, wrong types and out-of-range values are rejected with the reason, using the same validator the launch transaction uses. Copy it to reuse a configuration for another launch.
Launching: review and sign
- Tick the confirmation that the settings can't be changed after launch, then press Launch.
- Your logo and metadata are uploaded to permanent storage.
- Two new keypairs are generated in your browser, one for the mint and one for the config. They sign their own account creation and are then discarded.
- The server builds the transaction, simulates it against current chain state, sizes the compute budget and sets a priority fee from recent network fees and your speed setting.
- Your wallet asks for one signature. Nothing is sent if the simulation fails; you see the reason instead.
- After confirmation you land on the token page, and the launch appears on the board within seconds.
Cost breakdown
Buying and selling
Trades go straight to the token's Meteora pool.
Amounts
Buys are entered in SOL and sells in tokens. Quick-buy buttons use the four amounts from Settings; Max uses your balance minus about 0.01 SOL kept for fees.
The quote
- You receive: the exact output from the curve at its current state.
- Minimum received: the output after your slippage; the trade fails rather than fill below it.
- Fee now: the scheduled fee at the current chain time, plus any dynamic fee.
- Price impact: how far your trade moves the price compared with the spot price.
Slippage and speed
Slippage (1%, 2%, 5% or 10%, default from Settings) is how far the price may move between quote and execution. Transaction speed sets the priority fee: normal uses the recent 75th-percentile fee, fast 3× and turbo 10×, both capped.
Before you sign
Every trade is built and simulated on the server first. If it would fail (slippage, curve complete, too small), you get the reason and nothing is sent to your wallet. After a buy, wrapped SOL is unwrapped back to normal SOL automatically.
The token page
Header
Name, ticker and status (on curve, graduating, DAMM v2), plus price, market cap, SOL on the curve, curve progress, the fee right now and age.
Price table
Instead of a chart, the price is shown as exact numbers built from the pool's real swaps. Pick 1m, 5m, 15m, 1h or 4h intervals; each row shows open, high, low, close, change, volume, net SOL flow, buy/sell count and distinct wallets. Prices are execution prices in SOL per token.
Tabs
Info rail
Supply, decimals, graduation threshold, starting market cap, pool share; the fee schedule, dynamic fee, the creator / platform / Meteora split, graduated pool fee, graduation fee, fees generated and unclaimed; locked LP shares and creator allocation; and the genuine-activity score.
Trade history loads progressively on public RPCs: the page shows what has arrived and fills in the rest within seconds.
The board
- Click a column header (age, market cap, curve, fees, score) to sort; click again to reverse.
- Quick buy sends a buy of the amount in the toolbar straight from the row, after simulation.
- Unverified shows launches that fail a safety check; they are hidden by default.
- The Network panel shows the live slot, block time, transactions per second, recent priority fees and the SOL price.
Early-wallet analytics
Who bought first, and where their SOL came from.
For each token, change reads the earliest swaps from the pool's history, identifies each buyer from token-balance changes (so it works for direct, aggregator and bot trades), and traces where each buyer's SOL came from shortly before the first buy. Exchanges and bridges are recognised as hubs and ignored as funders.
Flags
- Red: buys in the pool's creation slot (usually bundled with the launch), and buyers funded by the creator or the creator's funder.
- Amber: several early buyers funded by one wallet, or a burst of new buyers in one slot.
- Info: the creator buying early, shown with the share of supply.
Wallet tags
Launch block, creator-linked, shared funder, same slot, fresh wallet and creator. Exact rules are in Analytics thresholds.
These are measurements, not proof. Coordinated wallets can hide behind exchanges; unrelated wallets can share a funder.
Creator fees
Your share of trading fees builds up in the pool until you claim it.
Claiming
Open My launches with the wallet you launched from. Each token shows its unclaimed creator fees with a Claim button; the token page has the same button in its Fees section. The full amount arrives in one transaction: if Meteora's claim opens an empty token account, change closes it again so its rent comes straight back.
Fees arrive as SOL, or partly as the token if you chose output-token fees.
After graduation
- Unclaimed curve fees stay claimable after graduation, from the same button.
- Your locked DAMM v2 position earns its share of the pool fee; claim it from the pool on Meteora (linked from the token page).
- Your share of any surplus and of the graduation fee can be withdrawn with Meteora's DBC tools; a button inside change is planned.
Graduation
- The curve reaches its threshold. The last buy is partially filled so it lands exactly on it.
- If the launch has a creator allocation, a locker is created first.
- Meteora's migrator creates the DAMM v2 pool using the config's fee tier, deposits the raised SOL (minus any graduation fee) and the pool share of supply, and creates two locked LP positions.
- The token page switches to DAMM v2, with links to swap on Jupiter and open the pool on Meteora.
Migration normally happens within moments. If it hasn't, anyone can submit it from the token page; the Graduate button builds the same instructions and the payer only covers network fees (Meteora's pool authority pays the pool's rent).
SOL collected above the threshold is surplus: 80% is split between creator and platform by the creator trading-fee share, and 20% goes to Meteora.
Platform treasury
The platform's fee wallet is named in every launch config. Its share of trading fees, surplus and graduation fees accrues per pool. The Treasury page (visible in the side panel only when the treasury wallet is connected) lists every launch with what can be claimed and collects all of a pool's platform share in one transaction. Only the treasury wallet can sign these claims.
Verifying a launch
Every check on a receipt is read from chain data at the moment you open it. You can reproduce it without change:
- Open the receipt and copy the config address and its sha256 hash.
- Fetch the raw account and hash it:
solana account <CONFIG> --output json \ | jq -r '.account.data[0]' | base64 -d | sha256sum
- Compare the hash, then decode the account with Meteora's DBC IDL or open it on an explorer.
- On the mint, check that mint authority and freeze authority are empty; on the metadata account, that it is not mutable.
The checks themselves are listed in Safety rules and checks.
Settings
Settings are stored in this browser only.
All launch parameters
Every fee, who gets it
Safety rules and checks
Every launch config enforces these, and every receipt checks them against chain data:
Launches that fail any rule are hidden from the board unless you turn on Unverified.
Analytics thresholds
Board ranking
Trending ranks by a 0–100 genuine-activity score that rewards breadth and organic trading over raw volume:
Errors and fixes
Glossary
FAQ
Can a creator mint more tokens or freeze my wallet?
No. Mint and freeze authority are revoked in the launch transaction, and the receipt reads both from the mint account.
Can the creator pull the liquidity?
No. Before graduation the SOL sits in Meteora's pool vault; after graduation 100% of the DAMM v2 liquidity is permanently locked.
Does change stop bots or MEV?
No launchpad can guarantee that. A high starting fee with decay makes the first seconds expensive for snipers, and analytics show launch-block and linked buyers, but neither is a guarantee.
Can I change settings after launch?
No. The config account and metadata are immutable. Use the raw config to copy settings into a new launch.
Why does a new token show no trades yet?
Trade history is read from chain and arrives progressively on public RPCs; it fills in within seconds.
Where do I trade after graduation?
In the token's DAMM v2 pool, or through Jupiter. The token page links to both.
Is there a platform launch fee?
No. You pay only account rent and network fees.
Risks and limits
- Tokens can lose all their value. A fair launch structure does not make a token a good investment.
- Analytics are heuristics. They miss well-hidden coordination and can flag unrelated wallets.
- Everything about a launch is permanent: double-check before signing.
- Public RPCs are rate-limited; history-heavy views can be slow until they load.
- change builds transactions for Meteora's programs; their behaviour is defined by those programs.

change