{"version":1,"source":"https://memefees.com","scope":"Published platform facts, reviews and referral guides. Live figures are available through /api/v1/catalog. Editorial dates are preserved from the original records.","terms":"https://memefees.com/methodology#data-license","count":1,"documents":[{"id":"review:meteora-dbc","kind":"review","slug":"meteora-dbc","title":"Meteora DBC review","url":"https://memefees.com/reviews/meteora-dbc","updatedAt":"2026-10-01","sources":[{"label":"Meteora docs","url":"https://docs.meteora.ag/get-started"},{"label":"Meteora DBC fees","url":"https://docs.meteora.ag/core-products/dbc/fees/overview"},{"label":"Meteora DBC migration and liquidity","url":"https://docs.meteora.ag/core-products/dbc/migration-and-liquidity"},{"label":"Meteora DBC universal curve","url":"https://docs.meteora.ag/core-products/dbc/universal-curve"},{"label":"Solana Compass on Bags/DBC","url":"https://solanacompass.com/projects/BAGS"},{"label":"Believe DBC fee-adapter scope","url":"https://github.com/DefiLlama/dimension-adapters/blob/master/fees/believe/index.ts"}],"markdown":"Launch infrastructure for builders, not a consumer pad: how Meteora's programmable bonding curve works under Believe and Bags.\n\n### Verdict\n\nMeteora DBC sits underneath other launchpads rather than facing users directly. The tracked Believe and Bags datasets include DBC activity; that data relationship does not establish either frontend's current launch terms. A builder configures the curve, up to 16 segments, sets the fee schedule and picks a quote token, and DBC handles the trading and the migration to a Meteora DAMM v2 pool once the threshold is hit.\n\nThis review targets builders choosing launch infrastructure, not a retail creator picking where to launch a memecoin. A creator should verify the selected frontend's current launch flow and terms as well as the infrastructure underneath it. DBC's fee numbers also overlap with the frontends built on it, so do not add a DBC total to a Believe or Bags total: that would count the same trades twice.\n\n### Pros\n\n- Programmable bonding curve with up to 16 configurable segments, more flexible than a fixed curve\n- Automatic migration to a Meteora DAMM v2 pool once the configured quote threshold is reached; new configs can no longer pick DAMM v1\n- Fee schedule and quote token are both configurable per integrating frontend\n- DBC activity is represented in other tracked datasets, including Believe and Bags\n- Partner and creator trading fees can be claimed as they accrue, without waiting for migration\n\n### Cons\n\n- DBC is built for launchpads. launch.meteora.ag is a config tool for partners, so a retail creator normally launches through a frontend such as Bags or Moonshot\n- Meteora takes 20% of every curve trading fee and a fixed 0.2% of the liquidity at migration, on top of what the frontend charges\n- Activity history does not verify the current availability or terms of an integrating frontend\n- The curve fee can be anything from 0.25% to 99%, so the cost of a trade depends entirely on the frontend's config\n\n### Best for\n\n- Builders who want programmable bonding-curve infrastructure instead of writing their own launch contract\n- Teams designing a custom launch frontend that needs configurable fee schedules and quote tokens\n- Anyone researching what actually sits underneath Believe or Bags, rather than choosing where to launch a token\n\n### Skip it if\n\n- You are a retail creator looking for a place to launch a token directly. DBC is infrastructure, not a frontend\n- You are comparing fee totals across launchpads. DBC's numbers overlap with Believe and Bags, so counting both double-counts the same trades\n- You need proof that an integrating frontend still offers its earlier launch flow; historical DBC activity cannot establish that\n\n### What Meteora DBC is\n\nMeteora DBC, short for Dynamic Bonding Curve, is Meteora's permissionless token launch program on Solana. A launchpad creates a reusable config, and creators launch tokens from that template. The tracked Believe and Bags datasets include DBC activity, and Moonshot's help center points to DBC to explain how its Create coins bond.\n\n### How the curve works\n\nA team integrating DBC configures a bonding curve with up to 16 segments, a fee schedule, and a quote token. Tokens trade on that curve from launch, priced against whichever quote token the integrator chose.\n\nWhen trading reaches the configured quote threshold, curve trading stops and the liquidity migrates into a Meteora DAMM v2 pool. Meteora deprecated DAMM v1 as a target for new configs; only older pools still migrate there. The config also decides how the migrated liquidity splits between partner and creator, and how much of it is locked or vested.\n\n### Fees and who earns what\n\nThe frontend sets the curve fee: a fixed fee, a linear or exponential fee that falls over time, and an optional dynamic fee for volatility. The base fee must be at least 0.25%, and the total is capped at 99%. Meteora's protocol share is 20% of the total trading fee; a referrer, when present, gets 20% of that protocol share. The rest goes to the partner and the creator, at the creator percentage the config sets.\n\nA partner can also charge a pool creation fee and a migration fee, and Meteora takes a fixed 0.2% of the liquidity at migration. Launch costs and creator rewards therefore depend on the frontend. Current Believe terms are unverified here; the DBC integration alone does not establish its fees, payouts or creation availability.\n\n### Why the numbers overlap with Believe and Bags\n\nDBC sits underneath Believe, Bags, and other integrating frontends, so trading fees generated through those frontends are also DBC activity. Reading a DBC total next to a Believe or Bags total and adding them together double-counts the same trades.\n\nTreat DBC's tracked numbers as a view into the infrastructure layer, not as activity separate from what shows up on Believe's or Bags' own pages.\n\n### Who this is actually for\n\nThis page is useful to builders evaluating DBC integration and readers checking the source coverage of Believe or Bags metrics. A retail creator should verify a frontend's current availability and terms before following a launch guide.\n\nThe closest alternative for builders is Raydium's program; see Raydium LaunchLab vs Meteora DBC. LetsBONK runs on LaunchLab, while Bags and Moonshot point to DBC. Older Believe launch descriptions and historical DBC observations do not establish that the same frontend workflow is still available.\n\n### Frequently asked questions\n\n### Can I launch a token directly on Meteora DBC?\n\nNot as a retail creator. A launchpad sets up a DBC config, for example with Meteora's launch.meteora.ag tool, and creators launch from that config through the launchpad's site. Check the frontend's current terms; Believe activity in the DBC data does not confirm that a Believe creation flow is available.\n\n### What happens when a DBC bonding curve fills?\n\nOnce the quote reserve reaches the threshold in the frontend's config, curve trading stops and the liquidity moves into a Meteora DAMM v2 pool. Meteora keeps a fixed 0.2% of that liquidity as a migration fee.\n\n### Should I add DBC's fee numbers to Believe's or Bags' numbers?\n\nNo. DBC settles trades for both frontends, so its fee numbers overlap with theirs. Adding them together counts the same trading activity twice.\n\n### Is Meteora DBC still active?\n\nCheck the latest source-dated DBC observations for recent activity. These observations do not verify the current availability of every frontend that has integrated DBC.","markdownUrl":"https://memefees.com/reviews/meteora-dbc.md"}]}