Raydium (RAY)

Raydium Explained: Solana Liquidity Infrastructure, RAY Utility, and Control Risks

Raydium is a Solana-based suite of automated market makers, liquidity tools, token-launch infrastructure, and a separate perpetuals interface. Its RAY token connects to protocol buybacks, staking, and liquidity, but the core exchange functions do not require users to hold RAY.

What Raydium does

Raydium is not a single pool design. Its current product suite includes AMM v4 for legacy liquidity, CPMM for new constant-product pools, CLMM for concentrated liquidity, Farm and Staking programs, LaunchLab for bonding-curve token launches, and a separate perpetuals product. The public developer organization also publishes selected Rust programs, TypeScript SDKs, interface definitions, and integration examples for builders using Raydium liquidity on Solana.

For spot trading, Raydium uses on-chain pool programs rather than a conventional centralized matching engine. CPMM follows the constant-product model, while CLMM lets liquidity providers select price ranges. A CLMM position earns fees only while the market price remains within its chosen range, which can improve capital efficiency but requires more active management than a full-range pool.

The architecture is moving from legacy pools to newer programs

AMM v4 was originally designed as a hybrid constant-product pool that shared liquidity with OpenBook. Raydium’s documentation says a July 2026 program upgrade removed the OpenBook dependency from the deployed program, leaving existing AMM v4 pools operating as pure constant-product pools. AMM v4 remains relevant for legacy pairs, but Raydium recommends CPMM for new constant-product pools.

CPMM is the newer standard AMM. It does not require an OpenBook market and supports Token-2022 features, including certain transfer-fee configurations. CLMM uses ticks, position accounts, and observation data to track concentrated positions and fee growth. Integrators therefore need to identify the pool program before calculating fees, reading accounts, or constructing transactions; the programs have different account layouts, fee conventions, and upgrade authorities.

LaunchLab and Perps serve different users

LaunchLab is aimed at token creators and early buyers. A token begins trading against a bonding curve, and once its funding threshold is reached, remaining inventory and collected quote assets can migrate into a Raydium CPMM or CLMM pool. This creates a bridge between token issuance and secondary-market liquidity, but it also means launch participants face curve pricing, slippage, creator-fee settings, and the risks of newly issued tokens.

Raydium Perps should not be treated as another AMM pool. The documentation describes it as a separate perpetual-futures interface using an off-chain central-limit order book operated by Orderly Network. Deposits and withdrawals settle on Solana, while matching and order management use Orderly infrastructure. The product supports leverage and cross-margin, and the documentation states that it is unavailable to residents of the United States and several other jurisdictions.

What RAY actually does

RAY is Raydium’s native SPL token on Solana. The documented mint address is 4k3Dyjzvzp8eMZWUXbBCjEvwSkkk59S5iCNLY3QrkX6R. Raydium lists a maximum supply of 555 million RAY, a disabled mint authority, and current emissions of approximately 1.9 million RAY per year from the mining reserve. The project’s published allocation assigns tokens to mining reserves, partnerships and ecosystem programs, the team, liquidity, community and seed allocations, and advisers; team and seed vesting concluded on February 21, 2024.

RAY is connected to the protocol through buybacks, staking, and use as a pool asset. Raydium says users can stake RAY to earn additional RAY rewards, while 12% of trading fees are allocated to RAY buybacks. For CLMM and CPMM pools, the documented split is 84% to liquidity providers, 12% to buybacks, and 4% to the treasury. AMM v4 assigns 88% to liquidity providers and 12% to buybacks. These percentages apply to the swap fee, not to the full trade amount, so a 12% buyback share on a 0.25% fee equals 0.03% of the trade value.

Governance and upgrade control

RAY ownership should not be assumed to provide direct control over every protocol decision. Raydium’s current security documentation describes privileged program roles, including authorities that can upgrade programs, create or modify pool configurations, and collect protocol fees. Program upgrades for AMM v4, CPMM, CLMM, Farm v6, and LaunchLab are described as controlled by a 3-of-4 Squads multisig, while operational configuration and treasury functions are associated with a separate 3-of-5 treasury multisig.

The upgrade multisig is described as having a 24-hour timelock, while the treasury multisig has a narrower operational scope and no timelock. These controls reduce some single-key risks but do not make the programs immutable. The practical governance question for users and integrators is therefore not only how RAY holders may participate in signaling or staking, but also which multisig controls the relevant program, configuration account, fee destination, or upgrade authority at the time of use.

Dependencies and practical limitations

Raydium’s spot AMMs generally derive swap prices from pool state rather than an external oracle. The project says its frontend and API may use Pyth, Jupiter, or pool-derived prices for dollar displays, but those external prices are not used by the core AMM swap calculations. This distinction matters for integrators: a displayed dollar value is an interface estimate, while an executable swap depends on pool reserves, liquidity distribution, fees, slippage settings, and the Solana transaction environment.

Token-2022 extensions add another dependency surface. Freeze authority, transfer fees, transfer hooks, and other mint controls can change the economic and operational assumptions of a pool. Raydium documents protections against some extensions, but users still need to inspect the token mint and pool configuration rather than treating every listed asset as equivalent. The project’s own license and security material also state that audits, bug bounties, and administrative controls are mitigations rather than guarantees.

Key takeaways

• Raydium is a collection of Solana programs covering swaps, concentrated liquidity, farms, token launches, and a separate perpetuals venue.
• CPMM is the recommended newer constant-product program, while AMM v4 remains important for legacy pools; CLMM uses concentrated liquidity ranges and tick-based positions.
• RAY is not required to trade, provide liquidity, create pools, or use Raydium Perps. Its documented roles include staking, buyback exposure, and use as a liquidity asset.
• Twelve percent of documented spot trading fees is allocated to RAY buybacks, with the remaining fee split differing by pool program.
• Program upgrades and key operational permissions remain controlled by multisigs and privileged authorities rather than being fully determined by ordinary RAY ownership.
• Users and integrators must distinguish Raydium pool mechanics from Orderly-powered Perps infrastructure and inspect Token-2022 permissions before interacting with a pool.

Risks and open questions

• Raydium programs remain upgradeable, and operational authorities can change pool configurations, collect fees, or deploy new program code within their documented permissions.
• CLMM liquidity can move out of range, reducing fee generation and exposing liquidity providers to inventory and impermanent-loss risks.
• Token-2022 extensions, freeze authorities, transfer fees, and transfer hooks can materially change the risk and payout profile of a pool.
• LaunchLab participants face bonding-curve pricing, slippage, creator-fee settings, migration conditions, and the failure risk of newly launched tokens.
• Raydium Perps depends on Orderly Network’s matching and infrastructure layer and is subject to leverage, liquidation, counterparty, jurisdiction, and cross-margin risks.
• The economic effect of RAY buybacks depends on actual protocol fee generation, routing, execution, treasury decisions, and the treatment of bought-back tokens; a buyback allocation is not a guaranteed distribution to holders.