Bags runs on Meteora, not on a program of its own
Bags.fm did not write its own bonding curve. It builds on Meteora's dynamic bonding curve and layers the royalty and social verification work on top. That makes it the third distinct decoding problem among the major Solana launchpads, after Pump.fun's own program and the Raydium LaunchLab rails that carry LetsBonk.
Three venues, three programs. This is the whole reason launchpad coverage is expensive to build honestly and cheap to claim dishonestly. A bot that decodes one and lists ten is listing nine venues it will never see a launch on.
What the Meteora base gives you
- A curve engine that is used by more than one launchpad, so the decoder has reuse beyond Bags itself.
- Dynamic curve configuration, which means the same caution applies here as on LaunchLab: read the launch, do not assume the venue.
- A graduation path into Meteora liquidity, so your post-graduation exit runs through pools rather than a bespoke AMM.
The 1% that never stops
Every token minted on Bags carries an embedded fee-sharing configuration. By default one percent of all trading volume on that token is routed back to the designated recipients, paid in SOL, for as long as the token trades. Not one percent of the curve phase. One percent of the volume, afterwards included.
Most launchpad fees are a toll you pay at the gate. This one is a toll on the road. It is the clearest economic difference between Bags and every venue that stops charging once the pool exists.
| Where the fee applies | Pump.fun style venue | Bags |
|---|---|---|
| Curve buy | Platform fee | Platform fee plus royalty |
| Curve sell | Platform fee | Platform fee plus royalty |
| After graduation | Pool fee only | Pool fee plus royalty, permanently |
| Who receives it | The platform | Named recipients set at launch |
It cuts the other way as well. A creator earning on volume has a reason to keep the token traded rather than to exit and disappear, which is a genuinely different incentive from a launchpad where the creator's only payday is the supply they held back.
Reading the fee split before you buy
Bags lets a creator designate several fee recipients at launch, each with a percentage allocation, so collaborators can be paid automatically. That configuration is attached to the token, which means it is readable, which means it is screening material.
This is unusual and worth exploiting. On most launchpads a sniper is guessing at intent from behaviour. Here part of the intent is written down before the first trade.
- 1Count the recipientsOne wallet taking everything reads differently from a split across a named group. Neither is automatically good, but the shape tells you how the launch was organised.
- 2Check whether recipients are fresh walletsA royalty pointed at an address created minutes earlier is a different proposition from one pointed at a wallet with history.
- 3Compare royalty to the defaultThe default sits at one percent. A launch configured well above that is telling you what the token is for, and it is not trading.
- 4Tie recipients to the deployerIf the fee recipients and the deployer share a funding source, the social framing and the economic reality are not the same thing.
What a round trip actually costs on Bags
Add it up honestly before you decide the edge is there. The royalty applies in both directions, the curve moves against your own size, and every attempt costs the priority bid you attached to it whether or not it lands.
| Cost | Applies | Notes |
|---|---|---|
| Creator royalty | Every trade, forever | 1% by default, configurable up |
| Curve or pool fee | Every trade | Depends on phase |
| Curve convexity | Curve phase | Scales with your size |
| Priority fee and tip | Every attempt | Paid on failures too |
| Base network fee | Every attempt | Small but per attempt |
The row that surprises people is the first one. A strategy that works on a venue charging only at the gate can be underwater on a venue charging on the road, and the difference shows up in the trades you hold longest rather than the ones you flip.
What Bags snipers get wrong
- 1Pointing a Pump.fun or LaunchLab listener at itBags is on Meteora rails. Neither of the other two decoders sees these launches at all.
- 2Modelling the royalty as a launch feeIt does not end at graduation. Every future trade in that token carries it, which changes long holds more than quick flips.
- 3Ignoring the fee recipient listIt is readable before the first trade and it tells you how the launch was organised. Skipping it throws away the venue's best screening signal.
- 4Treating verification as safetyA linked social account is evidence about identity, not about intent. It does not answer what the opening buys did.
- 5Assuming one fixed curveMeteora curves are dynamic and configured per launch, so the same caution that applies on LaunchLab applies here.
Questions people ask
These come up in the ticket queue often enough to answer once, properly. If yours is not here, send it over and it probably ends up on this page.
Meteora's dynamic bonding curve program, because that is what Bags.fm builds on. A listener subscribed to Pump.fun's program or to Raydium LaunchLab will not see a single Bags launch.
Key takeaways
- Bags builds on Meteora's dynamic bonding curve, so it is a third distinct decoder alongside Pump.fun and Raydium LaunchLab.
- A creator royalty of one percent by default is charged on trading volume in perpetuity, not only during the curve phase.
- That royalty applies to your trades too, so it is a permanent haircut on every round trip in the token.
- Fee recipients and their percentage splits are set at launch and readable, which makes them genuine screening material.
- Social verification gives identity evidence that most venues lack, but it is a tiebreaker rather than a substitute for behavioural screening.
The one venue where identity is a real signal
Bags positions itself around creator rights and fee attribution rather than pure permissionlessness, and adds a social verification layer on top of the curve. On a venue where anyone can mint anonymously, screening has to infer who the creator is from on-chain crumbs. Here there is sometimes an actual claim to check.
Treat it as evidence, not proof. A verified handle tells you an account was linked. It does not tell you the account belongs to somebody who will still be around next week, and it does not override a funding graph that says the opening buys were coordinated.