Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.raydium.io/llms.txt

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

Raydium doesn’t stand alone. It consumes inputs from and produces outputs for a web of other Solana protocols. This page maps those relationships so you understand the boundaries of Raydium’s responsibility and where other protocols’ behavior affects you as a user or integrator.

​
Upstream dependencies

​
OpenBook (formerly Serum)

  • Role: central limit orderbook. AMM v4 pools were originally hybrid against OpenBook — swaps could fill against either the pool’s AMM curve or the matching OpenBook market — but the OpenBook integration has since been deactivated. AMM v4 pools no longer post or maintain orders on OpenBook.
  • Where it matters: historically only for AMM v4 pools; today, none of Raydium’s products has a live OpenBook dependency.
  • Risk surface: previously, OpenBook upgrades or outages could affect AMM v4 behavior (one such incident in January 2023). Now that the integration is off, that coupling is removed. CPMM and CLMM never had an OpenBook dependency.
  • Status: OpenBook continues running on Solana; Raydium does not depend on it for any current swap traffic. The OpenBook market accounts referenced by existing AMM v4 pools remain on-chain as inert state for backwards compatibility.

​
Solana runtime

  • Role: the execution substrate for all Raydium programs.
  • Where it matters: everywhere. Solana’s finality time (~1s), compute budget limits (1.4M CU per tx), and address lookup tables all directly affect Raydium UX.
  • Status: Solana upgrades periodically; Raydium tracks validator client releases (Agave, Firedancer) and adjusts if behavior changes.

​
Token programs (SPL Token and Token-2022)

  • Role: the token primitives all Raydium pools hold.
  • SPL Token: the legacy program; works on all products.
  • Token-2022: extensions-enabled program; works on CPMM, CLMM, Farm v6, not AMM v4.
  • Risk surface: extension behavior (transfer fees, hooks, etc.) can affect pool functionality. See security/oracle-and-token-risks.

​
Downstream integrations

​
Jupiter and other aggregators

  • Role: route trades across many Solana DEXes, including Raydium.
  • How it integrates: Jupiter reads pool state from Raydium’s REST API and via direct on-chain calls, then composes swap instructions via the Raydium SDK (or sometimes directly).
  • Volume share: roughly 60% of Jupiter’s volume touches Raydium pools at least once.
  • Integrator path: the general aggregator pattern is documented in integration-guides/aggregator.

​
Wallets

  • Role: let users swap, track LP positions, and participate in farms without leaving the wallet.
  • How they integrate:
    • Swap: route via Jupiter or directly through Raydium SDK.
    • Position display: enumerate user’s ATAs and NFT holdings, cross-reference with Raydium’s pool list (integration-guides/wallet-integration).
    • Farm display: call Raydium’s /positions/staking endpoint.
  • User impact: any wallet with in-app swap likely routes through Raydium without you noticing.

​
Lending protocols (Kamino, Marginfi, Drift)

  • Role: borrow/lend protocols that need oracle prices and liquidation execution venues.
  • How they integrate: CLMM ObservationState TWAPs as oracles; direct swaps through Raydium for liquidation collateral conversion.
  • Risk: if a lending protocol uses a spot Raydium price instead of TWAP, they can be exploited by flash-loan-style manipulation (see security/attack-vectors).

​
MEV searchers and arbitrageurs

  • Role: keep prices in line across Raydium, Orca, Phoenix, and centralized exchanges.
  • Effect on users: tight prices most of the time; sandwich attacks on less-protected swaps. See integration-guides/routing-and-mev.

​
Bots (market makers, DCA executors, liquidators)

  • Role: provide liquidity (LP on shallow pools), execute scheduled trades, close positions.
  • Integration path: typically Python or Rust bots using sdk-api/python-integration or Rust CPI wrappers.

​
Position in aggregated volume

As of April 2026:
  • Raydium handles ~35–45% of Solana-wide DEX volume on any given day.
  • Peak market share ~55% during periods when memecoin activity concentrates in LaunchLab + graduated pools.
  • Low end ~25% during periods of heavy orderbook-driven activity (large institutional flow goes to Phoenix when available).
These numbers fluctuate; the point is Raydium is reliably one of the top two venues by volume.

​
Token-2022 ecosystem

Raydium is one of the first major DEXes to natively support Token-2022. Implications:
  • New mints with transfer fees (e.g., royalties, fee-to-issuer tokens) can be LP’d.
  • Transfer-hook mints can exist (though with risk caveats).
  • Non-transferable and permanent-delegate mints are blocked.
As more projects launch under Token-2022 — particularly the “institutional” crowd using regulated mints — Raydium’s support positions it as a venue for that class of liquidity.

​
Future-looking dependencies

Watch-items that could change Raydium’s ecosystem position:
  • Solana validator diversification: if Firedancer achieves dominance, performance characteristics could shift.
  • Cross-chain bridging: Raydium has been studying extensions to other L1s/L2s. No deploys yet.
  • Jito’s evolution: ongoing integration between block engines and DeFi could change MEV dynamics.
  • On-chain orderbooks (Phoenix): continued maturity could shift some AMM-ish flow to orderbooks.

​
Pointers

Sources:
  • DefiLlama — market share stats.
  • Jupiter docs — aggregator routing.
  • Raydium API integration observations (2021–2026).