How ROCK works

ROCK is a Solana launchpad on Meteora's Dynamic Bonding Curve (DBC). It changes the incentives in the trenches: deeper launches, paid ticker copies, and trading fees routed back to holders and creators. It doesn't end manipulation, bundling or PvP. It makes them more expensive and rewards the people who actually hold.

Status: what's built and what isn't

How ROCK works

• Launch. A creator picks a name, ticker, image, pair (SOL or USDC) and fee tier. ROCK's server prices the ticker and builds one transaction that pays any duplicate-ticker fee and creates the coin and its Meteora DBC pool from ROCK's config. The creator signs it in their wallet.
• Curve. The coin trades on its bonding curve from about a $20K market cap. Buys add real SOL/USDC to the pool.
• Graduate. At about a $150K market cap the curve is complete and its liquidity moves to a Meteora DAMM v2 pool, where the LP is permanently locked.
• Fees. Every trade, before and after graduation, pays the creator-chosen fee. ROCK's share is split four ways: holders 40%, creator 20%, ROCK buyback 30%, treasury 10%.

Higher-liquidity launches

On a low-liquidity curve that starts near a $4K market cap, a small amount of money buys a large share of supply. ROCK starts every coin at about $20K, so the same share costs several times more:

Excluding fees. The reference curve is a constant-product curve with 1.073B virtual tokens against $4,292 of virtual quote.

Market cap, virtual liquidity, real reserves

These are four different numbers, and ROCK labels them separately everywhere:

• Market cap = price × 1B supply. $20K at launch. That isn't money anyone deposited.
• Virtual liquidity is the curve's shape (DBC concentrated-liquidity parameters). It sets how fast price moves, but nobody can withdraw it.
• Real reserve is the SOL/USDC actually held by the DBC pool. It's 0 at launch and reaches the migration threshold (~$40.1K) at graduation. Coin pages show this as "Curve reserve".
• Executable liquidity is what a trade can move through at an acceptable price impact. The trade panel shows impact for each quote.

Higher liquidity doesn't eliminate bundling and doesn't guarantee stable prices. It raises the cost of dominating early supply.

Meteora DBC config

ROCK defines six DBC configs (SOL and USDC × three fee tiers). They're built with buildCurveWithMarketCap from @meteora-ag/dynamic-bonding-curve-sdk@2.0.0 by scripts/build-curve.ts, and every number on this site is read from that output. Generated 2026-11-03.

SOL pairs: a DBC config is denominated in its quote token, so a SOL config hits exactly $20K/$150K only at the SOL price it was built for. If SOL moves, the USD starting market cap moves with it. ROCK creates a fresh set of SOL configs when SOL drifts more than about 15% from the reference. Existing coins keep their original config. USDC configs are exact.

Graduation

• When the pool's quote reserve reaches the threshold, DBC swaps stop and the pool is ready to migrate.
• Migration is permissionless. Meteora runs migration keepers on mainnet for eligible quote thresholds, and ROCK runs its own crank as a fallback.
• Meteora creates a DAMM v2 pool seeded with the quote reserve and 267.48M tokens at the graduation price. Meteora's SDK applies a 0.2% protocol liquidity-migration fee (about 0.84 SOL on a SOL pool).
• Locked: 100% of the migrated LP goes to the partner position (owned by ROCK's fee wallet) as permanently locked liquidity. Neither ROCK nor anyone else can withdraw it. That comes from the DAMM v2 permanent lock set in the DBC config.
• Who claims fees: the locked position still earns LP fees (80% of the DAMM v2 trading fee after Meteora's 20%). ROCK's keeper claims them and splits them four ways, exactly as before graduation.
• Surplus: if the final buy overshoots the threshold, DBC splits the surplus 20% to Meteora and 80% to partner/creator. ROCK treats its part as revenue and splits it the same way.

Fees

Creators choose a tier at launch. It applies to every buy and sell, on the curve and after graduation.

Fee layers

• Total fee: the tier, charged on the trade. Collected in the quote token (SOL/USDC).
• Meteora protocol fee: 20% of the trading fee on DBC and on DAMM v2 (Meteora docs).
• Referral / host fee: when a terminal passes a referral account, 20% of Meteora's protocol fee goes to it. It comes out of Meteora's share and doesn't change ROCK's revenue or what the trader pays.
• ROCK revenue: the remaining 80%. On the curve this is DBC's partner trading-fee share (the config gives the creator field 0%). After graduation it's the LP fee of ROCK's locked position.
• The split applies only to ROCK revenue, never to the full fee.

How fees move

ROCK uses no custom on-chain program. Fees build up in Meteora's pool accounts until ROCK's keeper (a server process) claims them with Meteora's own claim instruction into ROCK's fee wallet. Each claim is booked to the coin's ledger and split four ways using integer maths, with the rounding dust (at most 3 base units) going to the treasury. Every claim and payout is a public transaction.

Holder rewards

40% of ROCK's revenue from each coin goes to that coin's holders, paid in the coin's pair (SOL or USDC).

• Time-weighted, not snapshots. Rewards are computed per 10-minute epoch from each wallet's time-weighted average balance. Buying a large bag a second before the epoch ends earns one second's worth.
• Earned is kept. Selling stops future accrual and never claws back credit already earned.
• Pools aren't holders. DBC and DAMM v2 vaults and ROCK's own wallets are excluded, so their share goes to real holders.
• How it's measured. The keeper reads every holder's balance about once a minute and credits each interval at the lower of the balances at its start and end. A bag bought just before a reading, or sold just after one, earns nothing for that interval.
• Payouts. At the end of each epoch the holder share is split pro rata and paid straight to wallets once a wallet's balance passes the minimum (about $0.01). Smaller balances roll over. Total credits can never exceed what the coin's holder bucket has received.
• Verifiable. The inputs are public token balances and every payout is a public transaction.

Creator rewards

20% of ROCK's revenue from a coin goes to the payout wallet the creator chose at launch. It's paid in the coin's pair, before and after graduation, and shown on the coin page. Creators can also make a first buy inside the launch transaction, so nobody can buy before them.

Ticker protection

• Tickers are 1–10 ASCII letters or digits and case-insensitive. A leading $ is ignored. Look-alike Unicode characters are rejected.
• The first coin with a ticker launches free. Each later one pays 1 SOL to the treasury. The fee is a server setting.
• The fee is part of the launch transaction itself. ROCK's server generates each coin's mint key and only signs a transaction that includes the fee. A Solana signature covers the whole transaction, so the fee can't be removed without breaking it. Different capitalisation doesn't avoid it.
• The original coin is never affected.

Limitation: DBC pool creation is permissionless, so someone could create a pool on ROCK's config without going through ROCK's site, using their own mint. Those pools aren't registered, so ROCK doesn't list them and they get no rewards. ROCK still collects their partner fees, which go to the treasury.

ROCK buybacks

30% of ROCK's revenue buys the ROCK ecosystem token. The keeper buys at most once every 6 hours, in capped slices, through Jupiter. Before each buy it compares the route's effective price with the market price and skips the slice if it's more than 3% worse. Bought ROCK goes to the treasury and is held there. The Buybacks page lists every transaction. The ROCK token is separate from coins launched on ROCK and hasn't launched.

Treasury

10% of ROCK's revenue, plus duplicate-ticker fees, goes to the treasury, which funds development, infrastructure, operations, marketing and incentives. Its address and transactions will be public.

Authorities & security

• ROCK has no custom on-chain program. Coins, pools, curves, graduation and LP locks are Meteora's audited programs.
• ROCK's server holds one key: the fee wallet, which is Meteora's fee claimer for every ROCK config. On mainnet it lives in the host's secret store, never in code or on disk.
• The treasury is a Squads multisig. ROCK's server only sends to it and holds none of its keys.
• Every transaction the keeper signs is recorded before it's sent, so a crash can't pay anyone twice or lose a fee claim.
• The fee wallet only ever holds fees waiting to be paid out. Users never send it funds, apart from a duplicate-ticker fee they approve in their own wallet.
• Coin mints have no mint or freeze authority, and metadata is immutable.

Risks

• Memecoins are highly speculative. Most go to zero and you can lose everything you put in.
• Fee claims and payouts are run by ROCK's server. If it stops, fees keep accumulating safely in Meteora's pools but payouts pause until it's back.
• Reward calculations run off chain on ROCK's server. Inputs and payouts are public, but you rely on the server computing them correctly.
• Buyback swaps can lose value to slippage within the price guard.
• SOL-paired coins' USD market caps move with SOL.
• Meteora's programs are external dependencies. Changes or incidents there affect ROCK coins.
• Prices and stats come from on-chain data and third-party feeds, and can be delayed or wrong.

Contracts

Meteora addresses come from Meteora's SDK constants and developer docs, and are the same on mainnet and devnet. ROCK's mainnet addresses will be listed here at launch.