How to Launch a Token on Bags (bags.fm)
How a Bags launch works - token info, the fee-share config, the Meteora curve - what the dev wallet needs extra, and how to launch with bundle and snipe buys.
Bags (bags.fm) is built around one idea: the creator - or whoever the creator chooses - earns a share of the trading fees for as long as the token trades. Technically a Bags token is created through the Bags API on a Meteora Dynamic Bonding Curve, and its address ends in BAGS. This guide covers what is different about a Bags launch and how to do one with bundle and snipe buys.
How a Bags launch works
A Bags launch is three on-chain steps instead of one:
- Token info. Bags stores the name, ticker, image and description and reserves a mint address ending in
BAGS. Bags generates and keeps that mint key, which is why you can't bring your own address. - Fee-share config. Before the token exists, a config is created on-chain that says who receives the creator share of trading fees. With a plain launch that is the dev wallet. Creating it costs some rent, which is why the dev wallet needs about 0.03 SOL more than on pump.fun.
- Create and buy. The token is created on its own Meteora bonding curve with that config, and the dev buy goes in with it.
The numbers
- 1 billion tokens with 9 decimals (pump.fun and LetsBonk use 6).
- The curve completes at 85 SOL raised.
- After the curve, the token migrates to a Meteora DAMM v2 pool and keeps trading on bags.fm, Meteora and aggregators (how Meteora DBC works).
- Mint and freeze authority are revoked on Bags tokens, like on pump.fun and LetsBonk (why that matters).
- Buys go through wrapped SOL, so each buying wallet needs about 0.002 SOL extra, refunded in the same transaction.
Step by step in SolBundle
- Pick Bags on the first step of the Launch wizard.
- Fill in the token details. Bags allows a longer description (up to 1000 characters); name and ticker follow the usual 32/10 character limits (metadata checklist).
- Choose the dev wallet and its buy. Remember the ~0.03 SOL extra for the fee-share config.
- Add bundle wallets (up to 8 in the launch block, all-or-nothing) and snipe wallets (up to 200, right after). Each short wallet gets a Fund button with the exact amount.
- Review and launch. The wizard creates the token info and fee-share config first, then sends the launch bundle. The result card shows the
...BAGSmint, links to bags.fm and Solscan, and a Trade on bags.fm link.
Creator fees on Bags
Because the fee-share config points at the dev wallet, that wallet earns the creator share of trading fees, both on the curve and after migration. Bags creator fees are claimed on bags.fm with the dev wallet. Keep that wallet - and its key - safe: it is the one that gets paid. (Pump.fun coins work differently; see claiming pump.fun creator fees.)
After the launch
On the curve, the Terminal buys and sells the token from many wallets at once (badge Bags curve). After it migrates to Meteora, trade it on bags.fm. Check how the launch looks to buyers with the holder checker.
Frequently asked questions
Why does a Bags token address end in BAGS?
Bags generates the mint address when the token info is created and uses a ...BAGS vanity address as its signature. Bags keeps the mint key, so the address can't be chosen by the creator.
Why does the dev wallet need more SOL on Bags?
A Bags launch creates a fee-share config on-chain before the token. Its accounts need rent, so the dev wallet needs about 0.03 SOL more than on pump.fun.
Where does a Bags token go after the bonding curve?
When the curve raises 85 SOL, the token migrates to a Meteora DAMM v2 pool and keeps trading on bags.fm, Meteora and aggregators.
How are creator fees claimed on Bags?
On bags.fm, with the wallet named in the fee-share config - the dev wallet for a plain launch.
Ready to build your launch?
Configure wallets, bundle execution and launch from one workspace.