Uploads permanent token metadata, requests the official create transaction and submits the wallet-signed version to Solana.
DOCUMENTATION
One form. Independent Solana launches.
Anything Solana reuses your token identity while preserving each launchpad’s own economics, transaction and wallet confirmation. Anything takes 0%.
How multi-launch works
- Connect once.Choose Phantom, Solflare, Backpack, Trust Wallet or another compatible Solana wallet.
- Enter token information once.Name, ticker, image, description, website, X and Telegram are reused across every selected route.
- Review native settings.Each selected launchpad gets its own visual panel containing only the controls its current launch flow needs.
- Approve each launch.Routes are independent. OTC requires two confirmations; most routes require one. Rejecting one does not cancel another.
- Confirm and save.Mint addresses and all transaction signatures are stored only after confirmation and linked to Solscan.
Current integration surface
LaunchpadIntegration methodLaunch requirement
Pump.funOfficial create transactionSquare image, metadata, SOL fee and optional first buy
StonkFunOfficial public launch APIQuote pair, standard/reward mode, optional tax and dev buy
EmberMeteora curve + fee modulesQuote pair, trade tax, graduation level and fee destination
BONK.funOfficial Raydium LaunchLabImage, BONK LaunchLab config, SOL fee and optional first buy
BagsOfficial Bags launch routePrefilled official Bags form, then review and launch on Bags
OTCWallet-signed Pump V2 adapterPump venue, approved reward pair and two wallet approvals
RaydiumOfficial LaunchLab SDKMetadata, SOL network fee and optional first buy
MeteoraOfficial DBC SDKMetadata and one config + pool wallet approval
Connected means the adapter either builds the provider transaction for your wallet or hands a validated launch intent to the provider’s official form. A real launch is complete only after you review, sign and confirm it on mainnet.
Provider behavior
Uses Raydium’s maintained SDK, live LaunchLab config API and BONK platform address. BONK supplies the mint signature; your wallet remains fee payer.
Uses its keyless public prepare → sign → submit flow. A processing result is polled and never repaid.
Uploads metadata through Ember, prepares its Meteora curve launch with the selected fee module, and submits only after your wallet signs.
Creates a custom-quote Pump V2 coin, then asks for a second signature to assign creator fees to OTC’s reward wallet before registration.
Uses Bags’ official launch-intent format to open a prefilled Bags form with the token name, ticker, description, artwork and social links. Review its fee mode and first buy on Bags before launching.
Builds a standard SOL LaunchLab token through Raydium SDK v2 using the live on-chain LaunchLab configuration and an optional first buy.
Uses Meteora’s official DBC SDK to create a new 1B-supply token, DBC configuration and DAMM v2 graduation pool in one wallet-signed transaction.
Confirmed routes are skipped. Failed routes can be retried on their own without starting successful launches again.
Fees, security and launch risk
Every venue keeps its provider, pool and network fees. Anything takes no fee and never requests a private key. Always read every wallet simulation: token creation is irreversible, provider APIs can change, and a launch may require more SOL than the displayed network estimate.