LiquidityPools.appOpen a calculator
Menu

Meteora DLMM · Discrete-bin model

Meteora DLMM calculator.

Inspect the actual geometric bin ladder, compare Spot, Curve, and Bid-Ask allocation shapes, and keep base fees separate from the volatility-driven variable fee.

Bin position

The active bin is zero. Enter an integer end-bin movement to model the final inventory state.

Fee scenario

Bin-level scenario input, not total pool volume.

Result

Modeled divergence vs. holding−0.10%End price remains inside the selected bins.
Price range$19.51 – $20.51
End-bin price$20.20
Base fee0.2500%
Variable fee0.4000%
Total fee rate0.6500%
Position / hold value$10,040.61 / $10,050.19
Estimated LP fee income$295.36
Net result vs. holding+$285.79
Each bar is a discrete fixed-price bin. Heights show the normalized analytical distribution.

This position is active in the modeled end bin.

Educational scenario only. Distribution weights follow the SDK shape and side-normalization rules before integer rounding; this is not a transaction quote. Excludes token transfer fees, composition fees, incentives, slippage, and rebalancing. Not financial advice.

The calculator uses the DLMM bin invariant

Each relative bin has one fixed price and one constant-sum liquidity value:

Pᵢ = P₀(1 + s/10,000)ⁱ; Lᵢ = Pᵢxᵢ + yᵢ

Where:

  • i — relative bin ID.
  • s — bin step in basis points.
  • Pᵢ — fixed price of bin i.
  • Lᵢ — constant-sum liquidity value in that bin.
  • xᵢ and yᵢ — token reserves in that bin.

A bin trades without price impact until one side is consumed; then execution advances to another bin.

How the three shapes are represented

Spot assigns the same raw weight to every selected bin. Curve uses the SDK helper’s Gaussian family centered on the active bin. Bid-Ask uses its inverse-Gaussian family to raise weights toward the edges. Token X and token Y weights are normalized separately on their respective sides, including half of the active-bin density on each side. The model omits only integer rounding and transaction construction.

How fees are separated

The program fee relationship is:

total fee = min(base fee + variable fee, 10%)

Where:

  • base fee — the base-factor, bin-step, and power-factor term.
  • variable fee — the volatility accumulator and variable-control term.
  • 10% — the program’s maximum total fee rate.

Estimated income uses volume and competing liquidity for the modeled active bin, then applies time in range and the standard-pool LP share.

What this cannot predict

Future volume, bin crossings, volatility decay, competing liquidity, token value, and rebalancing are unknown. A large modeled fee rate can coincide with rapid inventory conversion and loss against holding. No displayed figure is an expected return or a pool recommendation.

Official Meteora sources

  1. DLMM formulas: prices, constant-sum bins, and fees
  2. DLMM Spot, Curve, and Bid-Ask strategies
  3. Meteora DLMM TypeScript SDK reference

Frequently asked questions

How is a DLMM bin different from a concentrated-liquidity tick?

Each DLMM bin trades at one fixed price with constant-sum liquidity. Price changes when a swap consumes a bin and advances to another bin. A tick range instead represents a segment of a continuous concentrated-liquidity curve.

How does bin step change price?

A bin step is measured in basis points. Price at relative bin i is anchor price multiplied by (1 + bin step / 10,000) raised to i.

Are Spot, Curve, and Bid-Ask weights exact deposit quotes?

No. This calculator uses explicit normalized analytical shapes: uniform, center-heavy, and edge-heavy. Meteora SDK deposit amounts also depend on token balances, active-bin state, integer rounding, and strategy helpers.

Does this connect to Meteora?

No. This phase is pure client-side scenario maths. It does not call an API, read a wallet, quote a transaction, or recommend a pool.