How pads work
padlaunch registers pads on two shared launch programs. On Raydium LaunchLab, the program behind letsbonk.fun, Bankr and Raydium's own launchpad, a pad is a platform account that says who gets paid; the curve is Raydium's. On Meteora DBC a pad is your fee-claimer wallet plus one launch config per quote asset, and the config is the curve.
Quote assets and tokenized stocks
The quote asset is what launched tokens are priced and raised in. Both programs support tokenized stocks, with different rules. Browse everything on the quote assets page.
| Asset | Meteora DBC | Raydium LaunchLab |
|---|---|---|
| SOL, USDC, any plain SPL mint | Permissionless | Only if a Raydium config exists for the mint |
| Tokenized stocks: xStocks by Backed, Backpack Securities, Ondo, PreStocks, Shift | Permissionless when Meteora has issued a token badge for the mint. Over 2,300 mints are badged, covering every xStock, Backpack and Ondo stock. | Around 90 tokenized stocks already have a Raydium config, next to SOL, USDC, USDT and USD1. Every pad can use all of them with no setup, rent or request to Raydium: whoever launches a token picks one in the launch form. A stock without a config needs Raydium's team to create one; a pad cannot add it. |
| Other Token-2022 mints with extensions | Need a badge; without one, not allowed. Mints with a transfer fee are never allowed. | Same: needs a config. |
Accepted is not the same as traded: most badged stocks never see a trade. So every picker on this site starts from a curated list of launchable quote assets, the ones launchers actually trade, in groups (Solana, currencies, xStocks, PreStocks, Backpack and more), kept only where the program can quote in them. On Raydium that list is the whole "Priced in" menu; on Meteora it is the preset buttons, with everything else Meteora accepts one step further down. The quote assets page shows the lists too. They refresh every ten minutes.
Stock tokens carry issuer controls such as a permanent delegate, pausing and transfer hooks. Both programs accept that risk; so does anyone holding them.
Meteora DBC pads
| Setting | Meaning | Limit |
|---|---|---|
| Curve | Built from an opening and a graduation market cap in the quote asset. The gap sets how much supply sells on the curve and how much migrates. | Graduation above opening |
| Trading fee | Fixed, or decaying linearly or exponentially from a high anti-sniper rate. Optional dynamic fee on volatility. | 0.25% to 99% |
| Creator share | Percent of the non-protocol fee that goes to whoever launched the token; you keep the rest. | 0 to 100% |
| Pool creation fee | SOL charged per launch, 90% to you. | 0, or 0.001 to 100 SOL |
| Graduated pool fee | DAMM v2 fee tier: 0.25%, 0.3%, 1%, 2%, 4%, 6%, or custom 0.1% to 10%. | |
| Migration fee | Percent of the raise taken at graduation, split with the creator. | 0 to 99% |
| Liquidity split | Four shares: you and the creator, each locked for good or withdrawable. | Sum 100%, at least 10% locked |
| Token | SPL or Token-2022, 6 to 9 decimals, metadata authority immutable, creator or pad. |
Fixed by Meteora: 20% of trading fees, 10% of creation fees, a 0.2% cut of migrated liquidity, and graduation into DAMM v2, run by Meteora keepers once at least about $750 of quote is raised. Program dbcij3LWUppWqq96dh6gJWwBifmcGfLSB5D4DuSMaqN on both networks. Configs cannot be edited after creation; add a new one instead.
Launching on a config calls client.creator.createPool({ config, baseMint, name, symbol, uri, payer, poolCreator }) from @meteora-ag/dynamic-bonding-curve-sdk. Every pad page has a launch form that does this from the browser (the site signs the new mint key, you sign as creator, and an optional first buy rides in the same transaction), plus the script. Partner fees accrue per launched pool; the pad page lists every pool with its unclaimed trading, creation and migration fees, and the fee-claimer wallet claims each with one signature. Meteora's open-source fun-launch scaffold is a full front-end that takes your config key.
Raydium LaunchLab pads
What you control
| Setting | Meaning | Limit |
|---|---|---|
| Platform fee | Your cut of every buy and sell on the curve, paid in the quote token. | 0% to 5% |
| Creator fee | The token creator's cut of every trade. | 0% to 0.5% |
| LP fees kept or burned | At graduation the liquidity is locked for good. This split decides who holds the fee-key NFT: the kept share lets your pad harvest that pool's LP fees forever, the burned share earns fees for nobody. | Sums to 100%; the creator share is 0 on the current program |
| CPMM fee tier | Raydium fee tier of the pool tokens migrate into. | Any CPMM config account |
| Name, website, logo | Stored on chain, shown by Raydium's UI and indexers. | 64, 256 and 256 bytes |
| Creator fee recipient | After graduation the tier's creator fee goes to the pool's recorded creator: the token launcher by default, or your pad if you set it. | Any address |
| Vesting share | A slice of every launch's locked tokens vesting to your vesting wallet. Needs one createPlatformVestingAccount call per launch after its raise completes, or the slice stays unclaimed. | 0% to 100% of the locked amount |
| Transfer-fee authority | For Token-2022 launches with a transfer tax (max 5%): withdraws withheld fees and, after graduation, controls the tax. Set it before launching such tokens; never rotate it mid-launch. | Any address |
| Curve rules | Opt-in constraints on launch shape per quote config: up to 10 alternative groups of 25 checks over supply, sell rate, raise target, locks, token program, transfer fee and time. While enforced, every launch transaction must include the rule account. | Managed with the SDK |
| Config allowlist | Opt-in restriction to the quote configs you explicitly allow. | Managed with the SDK |
| Wallets | Fee claim wallet, LP NFT wallet, optional vesting wallet. | Any address |
What Raydium fixes
- Constant-product curve. The launch shape is chosen per token: supply, amount sold on the curve, raise target.
- The quote token comes from a Raydium config, chosen by each launch, not by the pad. Raydium's delegated authority has created about 560 on mainnet; the useful ones are SOL, USDC, USDT, USD1 and around 90 tokenized stocks (the rest are quoted in memecoins or unnamed mints, so the launch form hides them). Every platform may use every config at no cost to the pad. New ones need Raydium's team.
- 0.25% protocol fee on every trade, 6 decimals on launched tokens, and graduation into a CPMM pool run by Raydium's migrate wallet.
- Floors per launch: 10M minimum supply, at least 20% sold on the curve, at least 15% reaching the graduated pool, at most 80% locked, and a minimum raise of 24 SOL on the SOL config.
Launching tokens
Every pad page has a launch form. Name, symbol and metadata follow the Metaplex token standard: a name up to 32 bytes, a symbol up to 10 characters, and a link (up to 200 characters) to a JSON file with name, symbol, description and image. The form uploads the image and that JSON to Arweave from your browser: your wallet signs the upload, files up to 100 KB are free (images are shrunk to fit when possible), and larger ones cost a fraction of a cent in SOL, approved in the wallet. Or paste a link to metadata you host yourself. Pad logos on the launch forms upload the same way.
An optional first buy runs in the launch transaction, before anyone else can trade. On Raydium you also choose the quote config (SOL, USDC or a tokenized-stock config), the raise target, and under advanced settings the supply and the share sold on the curve. The defaults are Raydium's own: 1B supply, 79.31% sold, 85 SOL raised on the SOL config. Launched tokens trade on Jupiter and, for LaunchLab, on Raydium's launchpad page.
From a script, use raydium.launchpad.createLaunchpad from @raydium-io/raydium-sdk-v2 with your pad id as platformId. On mainnet the program is LanMV9sAd7wArD4vJFi2qDdfnVhFxYSUg6eADduJ3uj and the SOL config is 6s1xP3hpbAfFoNtUNF8mfHsjr2Bd97JxFJRWLbL6aHuX. Trading uses buyToken and sellToken; the pad's fee applies automatically because the pool remembers its platform.
Below the launch form each pad page has a Build your own front-end brief: a copy-paste prompt for Claude or any coding assistant with the pad's addresses, the SDK calls for listing, launching, trading and claiming, the fee rules, and the pitfalls this site hit.
Claiming fees
Your platform fee applies only while a token trades on the curve. After graduation a pad earns from the locked LP's fee key (the kept share) and, if set, the CPMM creator fee.
On Raydium, platform fees accumulate per quote token in a fee vault owned by the program. The pad page shows every launch routed through the pad and each vault's balance; the fee claim wallet sweeps a vault with one signature, with WSOL unwrapped in the same transaction. Launches from before the August 2026 upgrade keep their fee in the pool's own quote vault and get a per-pool claim button instead. Creators claim their fees with claimCreatorFee. After graduation, the LP NFT wallet harvests the graduated pool's fees through Raydium's lock program.
On Meteora, trading, creation and migration fees are claimed per launched pool by the fee-claimer wallet, from the pad page.
Referral fees
Every curve trade on LaunchLab accepts an optional shareFeeRate up to 1%, paid instantly to a shareFeeReceiver named in the transaction. It is set by whoever builds the trade, so a pad's own front-end can attach it to itself or to affiliates. Raydium's UI uses 0.1% for its share links. It is not stored on the pad and does not carry over to other front-ends.
What your wallet signs
Every transaction is built and simulated on the server, then checked again in your browser before your wallet sees it. Your wallet must be the fee payer, every instruction must target a program this site uses, the only SOL that can leave your wallet is what the form showed (the registration fee, a first buy, rent for accounts you create), and no instruction may move, approve or burn your tokens. If a transaction fails those checks the site refuses to ask for a signature and says why. The site never asks you to sign a message except to upload an image to Arweave.
Which pads are listed
The home and pads pages list the pads created on this site. Every creation transaction the site builds carries a memo naming the pad and a zero-lamport transfer to a fixed marker address, so the marker's transaction history is the registry, read from chain with no database. Pads that owe the registration fee are listed only once the payment is verified inside the same transaction. Pads sort by tokens launched, newest or name; the count is the number of pools launched through the pad. Every pad on chain shows the rest of the ecosystem.
Changing a pad
On Raydium the admin wallet can change every setting after creation. Creator fee and transfer-fee authority go through the program's bulk update that re-sends every field. Raydium's docs note that platform updates are rate-limited per Solana epoch. Changes to the LP split, creator-fee recipient and CPMM tier only affect tokens that graduate afterwards. On Meteora a config is fixed once created; add a new config for a different curve.
Costs
Registering a pad costs a 25 dollar registration fee in SOL, priced when you build the transaction and shown on the form, plus account rent and the network fee. On Raydium the rent is about 0.0075 SOL for the pad account and nothing per quote asset, because launches use Raydium's existing configs. On Meteora it is 0.0014 SOL of branding once per wallet plus about 0.0066 SOL per quote asset, since every quote asset is its own config: ten stocks is about 0.066 SOL, every xStock about 4.9 SOL, signed in batches of 30 per wallet approval. It is the only thing padlaunch ever charges: the site takes no share of any pad's trading fees, on either program. The fee is transferred to the site treasury inside the creation transaction itself, so it cannot be paid without the pad being created, and the pad cannot be created without it. Adding a quote asset to an existing Meteora pad and every later change are free. Launching a token on a pad costs roughly 0.02 to 0.03 SOL of rent plus any first buy.
Network
This deployment talks to Solana mainnet. Everything here creates real accounts and moves real SOL. Every transaction is simulated on the server before your wallet sees it, and readable errors come back instead of failed transactions.