Running volume on a Bags token

What kind of launchpad this is

Solana launchpads split roughly into two families. One optimises for throughput: minimal friction, enormous token counts, audiences that evaluate in seconds. The other optimises for the creator relationship, with fee sharing and attribution as the product rather than as a footnote.

Bags sits in the second family, and that positioning matters for a campaign in one specific way that people consistently miss. It also changes nothing about the mechanics that people worry about most, which is worth stating early so the rest of this page is read in proportion.

Mechanically, the model is the standard one: fixed supply, bonding curve, price as a function of how much has been bought, then migration into a pool once the curve fills. Everything in the launchpad comparison about curve phases and graduation applies here too.

Fee sharing changes the arithmetic, quietly

On a platform where a share of trading fees is directed to the creator, a campaign has a property most campaigns do not: part of what it spends comes back.

The mechanism is simple. Every swap pays a fee. If a portion of that fee is routed to the creator, and the creator is the same party funding the campaign, then a fraction of the fee bill returns rather than leaving entirely. On a campaign of any size that is a real number rather than a rounding error.

Two cautions keep this honest. It is an offset on one line item, not a discount on the campaign, and the largest line item in most campaigns is the venue trading fee rather than anything the platform charges. And fee schedules change; the arithmetic is only worth doing against the current terms rather than against a figure from an article. The fee breakdown covers where the rest of the money goes so the offset can be sized against the right denominator.

The curve phase, and the number nobody budgets for

While a token is still on its curve, execution is contested in a way that pool trading is not. Many participants quote against the same curve state within the same slot, all with tight tolerances because curve pricing moves in fine increments, and only the transactions that land first get the price they quoted. The rest revert.

We sample finalized blocks weekly and count execution errors per venue, and the gap between contested curves and established pools is large and consistent. This is a property of the mechanism rather than of any particular platform, so it applies to a Bags token on its curve exactly as it applies elsewhere.

The budgeting consequence is specific: failed transactions pay their fees and produce no volume, so a curve-phase campaign delivers less confirmed volume per SOL than the same configuration will after migration. Teams that calibrate expectations during the curve phase and then run the same budget afterwards are usually pleasantly surprised, which is a better direction to be wrong in but still worth planning around.

After graduation

Graduation changes more than it appears to. The curve and the migrated pool are separate pairs with separate addresses and separate histories, so every pair-level counter a discovery surface reads starts again at zero.

At the same moment, the structural attention that carried the curve phase disappears. People watching a progress bar were an audience the platform supplied; once the bar is gone, so are they. The token now competes against every other ordinary market with no built-in reason for anyone to look.

That combination, reset counters plus vanished attention plus cleaner execution, is why the week after graduation is the highest-leverage window for activity rather than the curve phase that precedes it. The post-migration guide covers the full checklist, including the links you control that now point at a dead pair.

There is a second, subtler effect of creator-aligned economics that is worth planning around rather than only counting. Platforms built on fee sharing attract creators who intend to stay, which shapes who else is on the board and what its audience expects to find. A token launched there is read against that expectation, favourably if the project is real and unfavourably if it is not. That works in both directions, and it is a reason to match the platform to what you are actually building rather than to whichever fee split looks best on a spreadsheet.

Designing a campaign here

1. Establish which phase you are in. Curve and pool behave differently enough that the same settings produce different results.
2. Check the migrated pool's depth by simulating a realistic buy and reading the price impact, then repeating for the sell.
3. Size swaps well under what moves the pool. Raise wallet count rather than swap size to reach a target.
4. Do the fee-share arithmetic against current terms, so the offset is included rather than assumed.
5. Concentrate rather than spread. A fresh pair reads short windows, so density matters more than duration.
6. Route across every pool the token has, since graduated tokens frequently end up with liquidity in more than one place.

The sixth item on that list deserves a note because it is the one most often skipped for the wrong reason. Routing across several pools looks like an optimisation you can add later, and it is actually the decision that governs failure rate, price impact and how the activity reads, all at once. Adding it afterwards means the first campaign already produced the pattern you were trying to avoid, and that record does not get rewritten by the second one.

What the platform does not change

Three things are identical regardless of where a token was created, and they are the three that decide outcomes.

Depth. If a realistic buy moves the price several percent, everything downstream suffers and no launchpad feature compensates.

Holder distribution. A concentrated holder list ends evaluations in seconds, and creator-friendly economics do not change what that list looks like.

Whether there is anything to arrive to. Attention converts against what a visitor finds, and no platform supplies that on your behalf.

The honest summary is that a creator-oriented launchpad improves the economics at the margin and changes nothing structural. That is a genuine advantage worth having and it is not a substitute for the foundation. If you want to see what a given target produces in swaps and unique addresses on your specific token, the campaign console reads its pools live and prices it in SOL before anything runs.