LIVE
Solana // Meteora DBC > DAMM v2

VolatilitySurge_

The pool taxes snipers 10% in the first blocks, charges more when price surges, and every partner fee is spent on buyback & burn. No router. No hooks. Just the curve.

3.00%
Fee now
0.00
Bot tax SOL
0
Burned

Telemetry

Live fee engine

What the pool charges right now, what bots paid at launch, and how the fee moved over the last two minutes.

Live Volatility Gauge LIVE
+0.0+0.5+1.0+1.5+2.0
+0.00%
volatility fee
Base
3.00%
Total fee
3.00%
Accum. move
0.0%

Fee charged by the pool on every swap: base 3% plus a volatility component that grows with price movement (DLMM-style accumulator) up to about +2% at a 15% move, then decays when the market calms.

Real-Time Bot Tax LIVE
SOL paid by snipers in blocks 1-4
SOL
Block 1
10%
0.000 SOL
Block 2
10%
0.000 SOL
Block 3
5.48%
0.000 SOL
Block 4
5.48%
0.000 SOL
STATUS AWAITING LAUNCHSNIPE TXS 0VOLUME 0.00 SOL

The anti-snipe fee is part of the pool itself, so it applies on every frontend, terminal and bot.

Dynamic Fee Chart LIVE
Base fee 3%Volatility feeCap ~5%
NOW 3.00%PEAK +0.00%AVG +0.00%
0%1%2%3%4%5%6%
NO SIGNAL / AWAITING LAUNCH

Anti-snipe schedule

Fee by block

Enforced by the Meteora Dynamic Bonding Curve pool, not by a router or a transfer hook. There is no way to trade around it.

Block 1-2 // slot +0 / +1
10%
SNIPE WINDOW

Snipers racing the launch pay a 10% fee to the pool on every buy. Same price for every bot, every router, every terminal.

Block 3-4 // slot +2 / +3
5.48%
COOLDOWN

Exponential step-down: 10% x (1 - 45.23%) = 5.48%. Late snipers still pay almost double the floor.

Block 5+ // slot +4 onward
3%
BASE FLOOR

Base floor for everyone, forever. The volatility fee is added on top only while price is moving hard.

DEV BUY @ 3%. The dev buy happens inside the launch transaction itself and pays the 3% floor (DBC first-swap-with-min-fee). It cannot be front-run: the pool does not exist before that transaction.
+ VOLATILITY FEE. From block 5 the total is 3% + a dynamic component: 0% in a calm market, up to about +2% at a 15% price move, decaying back as volatility fades.

BuybackAndBurnVault

Buyback & burn

Fees do not go to a team wallet. They are claimed by a program-owned vault and turned into burned supply.

SOL claimed
0.0000
partner fees into the vault
SOL spent on buybacks
0.0000
bought back on the curve
Tokens burned
0
0 tokens
Crank count
0
keeper runs
Fee flowloading
1Every swap pays the pool fee (anti-snipe / base + volatility)
2Partner share accrues to the BuybackAndBurnVault PDA (Meteora keeps its protocol share)
3Keeper crank claims the fees and buys the token back on the curve
4Every token the vault holds is burned in the same instruction
Vault balance awaiting buyback: 0.0000 SOL
Crank log LIVE
No cranks yet.

Protocol

How it works

Four rules, all enforced on-chain. No router, no hook, no off-chain promise.

01

Atomic launch

One transaction creates the token and the Meteora Dynamic Bonding Curve pool, makes the dev buy at the 3% floor and registers the launch on-chain. If any part fails, all of it reverts.

02

Snipers get taxed

Blocks 1-2 pay 10%, blocks 3-4 pay 5.48%, block 5 onward pays 3%. The fee lives inside the pool, so any aggregator, trading terminal or raw bot pays the same.

03

Volatility pays more

A volatility accumulator (bin step, DLMM-style) adds up to about +2% when price moves 15%. Calm market, fee returns to the base.

04

Buyback & burn

All partner fees go to the BuybackAndBurnVault PDA. A keeper claims them, buys the token back on the curve and burns it. After graduation the pool migrates to Meteora DAMM v2 with LP locked forever.

Disclosure

FAQ

Straight answers, including the parts that matter for trust.

Where is the anti-snipe fee charged?

By the Meteora Dynamic Bonding Curve pool itself. The fee schedule (10% in blocks 1-2, 5.48% in blocks 3-4, 3% from block 5) is part of the pool config and is verified by our program on-chain. It applies on every frontend, terminal, aggregator and bot. There is no router to bypass.

Does the dev pay the snipe fee?

No. The dev buy happens inside the launch transaction (the same transaction that creates the pool) and pays the 3% floor via DBC first-swap-with-min-fee, the same floor every trader pays from block 5. Nobody can trade before it because the pool does not exist until that transaction lands.

What is the volatility fee?

A dynamic fee added on top of the base fee. A volatility accumulator (the same model as Meteora DLMM, based on bin step) grows when price moves fast and decays when it calms down. At a 15% move it adds about +2%. In a quiet market it is close to zero.

Where do the trading fees go?

Meteora keeps its protocol share. All remaining (partner) fees go to the BuybackAndBurnVault, a PDA of the program. The creator share is configured to 0% and the program rejects any config where it is not.

A keeper periodically calls the crank: it claims the fees, buys the token back on the curve (capped per crank to limit price impact) and burns every token the vault holds. Totals for SOL claimed, SOL spent, tokens burned and crank count are stored on-chain.

[!] Can the admin take the fees?

Partly, and we want this to be clear. The program has a disclosed wind_down instruction. When the admin calls it, buybacks stop permanently and any SOL in the vault that has not yet been spent on buybacks is returned to the admin.

Tokens that were already burned stay burned. That is final and cannot be reversed by anyone. There is no other instruction that moves vault funds anywhere except into a buyback.

Transfer hooks, mint authority, LP?

No transfer hooks. The mint is immutable (no mint authority, supply can only go down through burns). When the curve completes, liquidity migrates to Meteora DAMM v2 and the LP is permanently locked.

SPL or Token-2022?

Either is supported by the launch flow. The final choice is announced together with the contract address.

Where is the program?

Program ID DXpoj4ao32Zn2WdmsmDAR1eS5vfKMX1cj31JTPiipiW3. The contract address of the token will be posted here and on X at launch. Until then, any address claiming to be VOLATILITY SURGE is not ours.