This guide explains Raydium's AMM v4 constant-product pool, its 0.25% LP fee, and when to add versus skip liquidity.
The decision changes when your projected 30-day fee share fails to exceed impermanent-loss exposure from a 10% relative price move.

How Raydium v4 constant product works
In Raydium's AMM v4 constant-product pool, the pool holds two on-chain reserves, x and y, and enforces x·y = k. A swap that adds Δx must remove Δy so that (x + Δx)(y − Δy) = xy; equivalently, Δy = y·Δx/(x + Δx). There are no resting limit orders inside the pool: the counterparty is the pool itself, and the post-trade price is set by the new reserve ratio. That is why depth is the practical cost control — as Δx grows relative to x, the effective execution price worsens, and a thin pool reprices faster than a deep one.
The same reserve math creates divergence exposure. When one token outperforms the other, arbitrage restores the invariant by adding the appreciating token and removing the underperforming one; an LP ends up with a different token mix than simply holding both assets. That is the mechanism behind impermanent loss: the pool preserves the product, not your original balance. A 10% relative move is a useful first stress case because it forces the curve to reprice, but the size of the resulting loss depends on the pair's behavior and on your share of the pool.
AMM v4 is not only a standalone curve. Each v4 AMM is paired with an OpenBook market — the on-chain order book descended from Serum — and Raydium can route trTrades between AMM liquidity and that book. Treat the OpenBook link as part of the pool's plumbing: before depositing, read the pool configuration and confirm that the linked market ID is the correct pair. A mismatch, deprecated market, or stale routing path can mean the volume you are underwriting does not reach the AMM leg at the rate you assume.
On the income side, the v4 AMM schedule charges a 0.25% fee on the input amount, and that fee accrues to LPs pro rata by LP-token share. In practice, your claim is a fraction of the pool, not a promised APR: hold s of S total LP tokens and your fee slice is s/S. Because the fee is charged on input, the amount actually swapped against the curve is smaller than the notional shown on a chart; because the fee accrues to LPs, it supports the claim behind each LP token. Verify the current fee tier in Raydium's AMM v4 documentation or the pool config before treating 0.25% as your net take.
The pre-deposit check follows directly: read x and y, confirm k and the OpenBook market ID, then compare your pro rata share of projected 30-day volume × 0.25% with the loss from a 10% relative price move in the pair. If the fee income does not clear that IL hurdle, adding liquidity is worse than skipping it; if it does, the remaining question is whether that cushion survives lower-than-expected volume and further price drift.

The evidence on v4 fee economics
Raydium’s AMM v4 fee economics are straightforward to audit, but only if you recompute them from primary data. According to Raydium’s offOfficial documentation (docs.raydium.io, AMM v4 instructions): swaps on v4 pools accrue a trading fee set at the program level. Before sizing a position in 2026, confirm the current fee parameter and instruction arguments in those docs, since protocol parameters can change. Treat any displayed annualized percentage rate as a convenience metric, not as evidence.
To verify live pool activity, pull a pool’s 24-hour or 7-day swap volume from Raydium’s interface or read it directly from the pool’s AMM account on Solana Explorer. Use the same source to confirm total pool liquidity and the value of the position you plan to add. Relying on a single dashboard view can hide stale data or aggregation differences, so the inputs you use for a deposit decision should be traceable to the pool’s on-chain state or to a figure you can cross-check against it.
The fee math is the core check: calculate your projected fee share as (your liquidity ÷ pool liquidity) × pool volume × pool fee rate. For example, if you supply a given fraction of a pool over a chosen window, you earn that same fraction of the fees generated by volume in that window. To estimate a 30-day figure, scale a verified 24-hour volume by the number of days in the period, or derive a daily average from a verified 7-day volume, then apply the same formula. Never trust a dashboard APR without recomputing it from these inputs.
Run a convergence check before depositing: compare the volume shown in Raydium’s UI with the volume or swap activity implied by the pool’s AMM account on Solana Explorer.
If the figures differ significantly, resolve the discrepancy or hold off on depositing until you can reconcile the data. This step ensures your fee projection reflects actual pool usage rather than a cached or mismatched statistic.
Once you have a projected 30-day fee share, compare that income against the impermanent loss exposure your pair could face over the same period. Adding liquidity is only justified when the fee share you calculated exceeds that exposure; if it doesn't, skipping the deposit preserves your capital. This evidence-based check keeps your decision grounded in verifiable pool volume, confirmed fee parameters, and your own math.

CPMM vs. CLMM vs. Concentrated: Who Wins?
Choosing between Raydium’s AMM v4 constant-product pool and a concentrated liquidity market maker (CLMM) position comes down to how your capital behaves relative to the pair you select. The right structure is the one that gives your projected fee share the best chance of clearing the price-movement exposure threshold described above, given how often you can manage the position and how closely the two assets track each other.
| Pool type | Capital deployment | Pair profile | Management cadence | Winner |
|---|---|---|---|---|
| AMM v4 (full-range CPMM) | Liquidity spread across the entire price curve; your full deposit remains active | Long-tail or volatile pairs with unpredictable price paths | Check less than once a week, or prefer a passive approach | AMM v4 |
| CLMM (concentrated) | Liquidity focused within a selected price range; capital outside the range stops earning | Correlated pairs (for example, SOL/USDC) with tighter relative movement | Reposition at least weekly to keep liquidity in range | CLMM |
AMM v4’s full-range design means every unit of your deposit is available to facilitate swaps at any price, so your capital is continuously earning its pro-rata share of pool activity. That constant participation comes with a trade-off: because the same liquidity is stretched across all possible prices, the fee density per dollar is far lower than what a well-managed concentrated position can capture when price stays within a narrow band.
CLMM positions invert that trade-off. By concentrating capital around the current market price, you compete for a larger share of fees generated within that range, which is why CLMM tends to win for correlated pairs where relative price movement is limited. The advantage depends on active upkeep: if the market moves outside your selected range, your liquidity stops earning until you reposition, making weekly monitoring a practical requirement rather than an optional refinement.
Use this as a pre-deposit check: if the pair is a new or volatile token, or if you cannot commit to reviewing and adjusting positions at least once a week, AMM v4 is the more resilient choice. If the pair is closely correlated and you can reposition on a weekly cadence, a concentrated position offers the stronger path to fee efficiency. In either case, confirm that your expected fee share still outweighs the pair’s likely price-move exposure before committing capital.

Costs and numbers that matter
Impermanent loss in a constant-product pool is the standard result for a relative price change r between the two tokens: loss versus simply holding is 2√r/(1+r) − 1. Treat these figures as method outputs, not forecasts, and apply them to your pair’s realistic move band rather than to an average market.
| Relative price move | IL vs. holding |
|---|---|
| 10% | ~0.11% |
| 25% | ~0.6% |
| 2x | ~5.7% |
| 4x | ~20% |
A 10% relative move costs roughly 0.11% by the same method, while the larger bands cost about 0.6%, 5.7%, and 20%. Compute your pair’s realistic move band before depositing; a stablecoin pair and a volatile pair should not use the same band.
Fee income is your share of volume times 0.25%. In the example, a $10,000 deposit in a $1,000,000 pool is a 1% share; at $500,000 weekly volume, that share earns (10,000/1,000,000) × 500,000 × 0.25% = $12.50/week, about $54 over a 30-day month. If your estimate is monthly volume, apply the same share to that monthly figure.
The deposit only beats skipping if projected 30-day fee share exceeds the IL you would absorb from the pair’s realistic relative move. For example, a 25% move costs about 0.6%, so a $10,000 position needs more than about $60 in 30-day fees; the example’s roughly $54/month is close to but below that line.
Also check costs that do not appear in the fee/IL comparison: Solana transaction and priority fees, plus any pool-specific claim, withdrawal, or account costs. Because these vary, verify current values in your wallet or on-chain before depositing and before exiting, and include round-trip costs in the same 30-day comparison.

What the evidence does not establish
Live 2026 pool volumes, current fee splits, and wash-trading-adjusted APRs cannot be confirmed from this article's sources. No market figure here is certified; each input below must be verified on-chain before the add/skip rule can be applied.
No grounding source in this packet provides verified 2026 Raydium v4 pool volume or TVL figures. Treat any displayed APR as a hypothesis: recompute it from on-chain pool state, swap volume, fee accrual, and your pro-rata share rather than accepting a marketing page. If the underlying volume cannot be traced to chain data, the threshold comparison is not established.
Edge case: stablecoin-stablecoin v4 pools have near-zero impermanent loss, so the skip-threshold rule can break in favor of fee income. That does not make the pool automatically profitable, because volume per pool may be much lower; check realized volume before equating low IL with profit.
Edge case: for new token launches, the rule can break the other way. Early volume may be one-time rather than repeatable, so a projection based on launch activity can overstate fee income. Check whether volume persists after the initial distribution before treating it as a run rate.
| Unverifiable claim | Why it can mislead | Check before depositing |
|---|---|---|
| Live 2026 pool volumes or TVL | No verified source is provided here; dashboards may lag or aggregate differently. | Read pool reserves and recent swap volume directly from chain data. |
| Current fee splits | Program parameters and routing can change; a stale fee assumption changes the threshold. | Confirm the fee actually applied to the pool you are using. |
| Wash-trading-adjusted APRs | Inflated volume can make fee income look larger than organic demand supports. | Compare volume patterns, unique flow, and fee accrual over time. |
| Stablecoin-stablecoin "safe" pools | Low IL does not guarantee enough volume to beat skipping. | Verify sustained volume, not just pair stability. |
| New-token launch pools | Early volume may not repeat, so projections can be overstated. | Wait for post-launch volume to stabilize before sizing a position. |
The practical rule is conservative: if a figure is not verifiable on-chain, do not let it decide the deposit. Recompute the fee side from primary data, treat launch and stablecoin edge cases as separate checks, and skip or reduce size when the evidence is incomplete.

$10,000 add or skip
Consider a $10,000 deposit into a Raydium AMM v4 SOL/mid-cap token pool with $1,000,000 in total liquidity, giving you a 1% share. Over the prior 7 days the pool processed $2,000,000 in swap volume. For this pair, assume a realistic 30-day relative price move of ±30%, which corresponds to roughly 0.9% impermanent loss on the position, or about $90 on $10,000. These inputs frame a single decision: add liquidity only if your projected 30-day fee share clears that $90 exposure.
Checkpoint 1 — fee income: At the 0.25% swap fee documented in Raydium’s official AMM v4 materials (docs.raydium.io), $2,000,000 in weekly volume generates $5,000 in total pool fees ($2,000,000 × 0.0025). Your 1% share is $50 per week, or about $200 over 30 days if volume holds. Against the $90 impermanent-loss estimate, the position starts with a positive fee cushion.
Checkpoint 2 — volume decay: Recheck pool volume 7 days after depositing using the same on-chain or dashboard sources you used initially. Fees scale linearly with volume, so your 30-day fee share falls to $90 when weekly volume averages roughly $900,000 ($900,000 × 0.0025 × 0.01 × 4.3 weeks ≈ $97). If observed volume trends below that level, the projected fee income no longer covers the assumed ±30% move, and exiting or reducing the position limits further erosion of the cushion.
Checkpoint 3 — IL realization: At day 30, mark the value of your LP position against the value of simply holding the same SOL and mid-cap token amounts you deposited. Impermanent loss is realized on withdrawal; if the relative price moved and fees did not keep pace, the mark-to-hold comparison makes the shortfall explicit and informs whether to remain in the pool.
The cost of being wrong cuts both ways. If you add liquidity and volume collapses while the pair diverges by 30%, you absorb the ~$90 impermanent loss with insufficient fee offset, underperforming a hold strategy. If you skip the deposit and volume sustains near $2,000,000 per week with a smaller relative price move, you forgo roughly $200 in 30-day fee income on $10,000. Running all three checkpoints before and during the position turns that trade-off into a measured decision rather than a guess.
Decision rules: add or skip
Apply these rules in order before depositing into a Raydium AMM v4 pool. Each rule is a gate, not a suggestion: if any rule fails, skip the deposit and keep capital idle.
Apply the canonical rule used throughout this guide: compute your projected 30-day fee share (your pool share × pool volume × 0.25% × 4.3) and add liquidity only if it exceeds your estimated impermanent loss at the pair's realistic move band; if it falls below that IL, skip. Use the same volume window you can verify on-chain, and do not annualize a thin sample.
If you cannot verify the pool's linked OpenBook market ID and its fee parameter in Raydium's official documentation, skip. Match the market ID shown on Raydium's pool page to the ID in the docs before comparing fees. Unverified pools carry contract-level risk that the fee arithmetic cannot price.
If the pair is stablecoin-stablecoin, impermanent loss is near zero, so the decision rests almost entirely on fee income: verify sustained 7-day and 30-day volume from on-chain data before adding, and skip if volume has collapsed sharply versus its prior window, even if the pair looks stable. Do not assume a fixed volume threshold — check the pool's actual, persistent activity.
For non-stablecoin pairs, use the 10% relative-move rule as a floor: if your projected fee share would not cover the impermanent loss from that move, skip. Record the inputs you used—pool share, volume window, and IL estimate—so you can re-run the check after a volume shock.
| Pre-deposit check | Pass condition | Action |
|---|---|---|
| OpenBook market ID and fee parameter | Verified in Raydium docs | Skip if unverified |
| Projected 30-day fee share | Greater than 2× estimated IL | Add; skip below 1× |
| Stablecoin-stablecoin pair | 7-day volume above ~$100,000 and no volume drop above 80% | Add only if fee check also passes |
Copy the checklist into your deposit notes and require every row to pass; a single failed row is enough to skip.
Frequently Asked Questions
How is the output amount of a swap calculated in a Raydium AMM v4 constant-product pool?
A swap that adds Δx must remove Δy so that (x + Δx)(y − Δy) = xy, or equivalently Δy = y·Δx/(x + Δx).
Who acts as the counterparty for trades in a Raydium v4 pool?
There are no resting limit orders inside the pool, so the counterparty is the pool itself and the post-trade price is set by the new reserve ratio.
Why do thin Raydium v4 pools lead to worse execution prices for larger swaps?
As the swap amount Δx grows relative to the reserve x, the effective execution price worsens and a thin pool reprices faster than a deep one.
How does arbitrage change a liquidity provider's token mix when one asset outperforms the other?
Arbitrage restores the invariant by adding the appreciating token and removing the underperforming one, leaving the liquidity provider with a different token mix than simply holding both assets.
What does the constant-product invariant preserve for liquidity providers?
The pool preserves the product (x·y = k), not the liquidity provider's original token balance.
What factors determine the size of impermanent loss from a relative price move in a Raydium v4 pool?
The size of the resulting impermanent loss depends on the pair's behavior and on the liquidity provider's share of the pool.
Quick answers
| What invariant does Raydium's AMM v4 constant-product pool enforce? | The pool holds two on-chain reserves, x and y, and enforces x·y = k. |
| How is Δy determined when a swap adds Δx? | Δy = y·Δx/(x + Δx). |
| Why is depth the practical cost control? | As Δx grows relative to x, the effective execution price worsens, and a thin pool reprices faster than a deep one. |
| What is the mechanism behind impermanent loss? | When one token outperforms the other, arbitrage restores the invariant by adding the appreciating token and removing the underperforming one, so an LP ends up with a different token mix than simply holding both assets. |
| When does the add-versus-skip decision change? | The decision changes when your projected 30-day fee share fails to exceed impermanent-loss exposure from a 10% relative price move. |
Also worth reading: Raydium CLMM vs AMM: 2026 Fee Data and Decision Framework: Raydium CLMM vs AMM: 2026 · How To Fix Raydium Firmware Password Issues On Dell Laptops: How To Fix Raydium Firmware · SHIB/WETH v2: Constant-Product Cliff and Slippage Depth: SHIB/WETH v2: Constant-Product Cliff and