Docs

bagggr is a launchpad on Solana. A creator names a token, pairs it with any SPL token they like (SOL, a stablecoin, a tokenized stock, another meme), and launches. The token trades on a linear bonding curve until a graduation target is reached; then the reserve and the held-back supply are seeded into a Raydium CPMM pool, the LP is burned, and the pair trades everywhere.

Nothing is custodial. Every trade and every launch is a transaction you sign. The protocol is a set of programs; this site reads their state and builds transactions for your wallet.

1. Token info. Name (2–32 characters), ticker (2–10 letters or numbers), an optional description and image (PNG, JPG, WebP or GIF, up to 4 MB), and optional links. The image and a metadata JSON are pinned to IPFS before the transaction is built; the token carries the metadata URI on chain.
2. Pair with. Paste the mint of any SPL token. Well-known assets are verified; anything else is read from the chain (name, symbol, decimals, logo) and shown as unverified. The pair asset is the token buyers pay with, and the asset your rewards are paid in.
3. Rewards. Choose where the reward stream goes, your fee wallet, the holders (all, or the top 100), or a buyback that burns the token, and how often it is pushed: every 15 or 30 minutes, hourly, or every 6, 12 or 24 hours. These are fixed at launch, like the 1.5% tax itself.

Supply is 1,000,000,000. 800,000,000 sell on the curve; 200,000,000 are held back to seed the pool. The curve's virtual reserves are chosen so that the held-back tokens against the whole raise open the pool at exactly the curve's final price; the 1.5% transfer tax on the way into the pool nudges the opening price up by about that much.

Price follows the tokens sold:

raised(s) = v0 · s / (vt0 − s)        price(s) = v0 · vt0 / (vt0 − s)²

A constant product with virtual reserves, the shape pump.fun uses: the curve behaves like a pool that opens with v0 of the pair asset against vt0 tokens, so the price crawls while the first tokens sell and accelerates toward the end. Buying Δ tokens from s costs raised(s + Δ) − raised(s); selling pays the same amount back. The graduation target is about $9.6K of the pair asset; v0 and vt0 follow from it and the supply split, so the curve raises exactly the target by the time it sells out, starting near a $3K market cap, rising 16× and bonding at $48K.

The site runs the same formula the program does, against the curve's live state, so the estimate you see before you sign is the fill you get, minus whatever moves in the same block. A 1% fee is taken on the quote side of every curve trade, and the token's 1.5% transfer tax is withheld from the tokens that change hands, so a buyer receives 98.5% of what the curve sells. On a token paired with something other than SOL, the panel offers to pay with SOL (or to receive SOL on a sell): Jupiter swaps the pair asset in the same transaction, and the curve trade is sized by the swap's guaranteed minimum, so a better fill leaves a little of the pair asset in your wallet.

The pusher is automatic and pays for itself, in SOL. It harvests the tax the token program withheld, sells it, and pushes on schedule; money never leaves the program except to recipients, the treasury and the pusher's own transaction fees. The sale of the pot is a transfer of the token, so its own 1.5% folds into the next push. Nobody is left holding the token.

When the reserve reaches the target, trading on the curve stops. In the graduation transaction the reserve and the 200,000,000 held-back tokens are deposited into a new Raydium CPMM pool at the curve's final price, and the LP tokens are burned. Nobody, including the creator and bagggr, can withdraw that liquidity.

From then on the token page keeps its chart and its Rewards tab, and points at the pool for trading.

The site is a Next.js app. It exposes a few server routes so the browser never holds a provider key:

Building a terminal, a bot or an aggregator? The integration guide has the program id, the account layouts, the exact pricing math, the buy and sell instructions, the events and the IDL.