Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.burst.trade/llms.txt

Use this file to discover all available pages before exploring further.

Burst uses Meteora DAMM v2 pools as the spot liquidity layer for the platform. Burst does not run a custom AMM. It uses Meteora’s DAMM v2 pool model as the onchain execution primitive.

​
How tokens flow into Meteora

Tokens on Burst launch on a bonding curve. Once the curve fills, the token graduates into a Meteora DAMM v2 pool. This is the standard lifecycle for every Burst token:
  1. Launch - Token is created and trades on the bonding curve.
  2. Graduate - The bonding curve fills and the token moves into a Meteora DAMM v2 pool.
  3. Trade - The token now trades on the DAMM v2 pool with deeper, persistent liquidity.
Burst then layers market integrity controls, Fusion resolution, and fee routing on top.

​
Burst is powered by DAMM v2 pools

Every serious market on Burst needs a durable liquidity destination. That destination is a Meteora DAMM v2 pool. DAMM v2 pools are the settlement layer for post-graduation markets.

​
Liquidity architecture

Meteora handles the pool layer

Meteora provides:
  • onchain pool state,
  • swap execution,
  • liquidity accounting,
  • and the persistent market surface after graduation.

Burst handles the control layer

Burst adds:
  • bonding curve launches and graduation rules,
  • canonical market selection (Fusion),
  • fake-chart enforcement,
  • and fee flow back into active pools.

​
How Burst uses Meteora DAMM v2

Burst uses Meteora DAMM v2 pools in three core places:
  1. Graduation target. Graduated tokens move into a Meteora DAMM v2 market.
  2. Canonical market layer. Resolved winners concentrate liquidity in one DAMM v2 pool via Fusion merges.
  3. Reinforcement layer. Burst fee redistribution routes value back into active DAMM v2 pools.

​
Why the DAMM v2 layer matters

AMM infrastructure decides whether attention can turn into durable liquidity. Using Meteora DAMM v2 gives Burst:
  • a consistent graduation endpoint,
  • a stable post-launch execution venue,
  • and one pool model that can be reinforced by protocol logic.
This reduces fragmentation after graduation. It also gives Burst one clean place to route liquidity, merge value, and deepen the winning market.

​
Burst-specific pool behavior

Burst does not treat all pools as neutral. It applies policy and enforcement above the pool layer. That includes:
  • pulling liquidity from clearly non-legitimate charts,
  • merging later variants into a canonical market (Fusion),
  • and routing protocol fees into the highest-volume token’s DAMM v2 pool.
Meteora is the execution layer.Burst is the market-structure layer.

​
Post-graduation market design

Once a token graduates, Burst wants liquidity to compound instead of scatter. That is why the protocol converges markets into a canonical DAMM v2 pool when needed. In practice:
  • the first graduated token in an identity cluster becomes canonical,
  • later variants can be absorbed into that canonical market,
  • and post-graduation liquidity accumulates in the same Meteora DAMM v2 venue.
This gives traders a clearer destination, winners deeper liquidity, and Burst one enforceable market surface per resolved winner.

​
Strategic role

Meteora provides the pool infrastructure. Burst determines which markets deserve to keep and attract liquidity. Together, that creates a stack with both credible onchain execution and active market-quality enforcement.