Raydium

Raydium is a Solana DEX for Permissionless Pools and Token Launches

Raydium is a Solana trading venue where pools of deposited tokens let people trade through code rather than a central custodian. Its non-custodial programs support routed swaps, permissionless constant-product pools, concentrated-liquidity positions and LaunchLab token launches. Users connect a Solana wallet, retain control of its keys and sign each transaction that changes on-chain balances.

Last updated:

The main decision is not whether the interface looks simple. It is whether the selected route, pool design, token program and liquidity depth match the intended trade or liquidity position. Those details determine cost, execution and maintenance.

From a wallet quote to a settled swap

When a connected wallet supplies an input token, amount and destination token, Raydium searches its pool graph and returns the route with the strongest quoted output. The quote uses a direct pool or several hops, with each pool charging its configured fee. Every AMM pool contains 2 token vaults, so route quality depends on available reserves and the price movement created by the proposed size.

After review, the wallet signs a Solana transaction containing the chosen swap instructions and a minimum acceptable output. Execution is atomic: all instructions succeed together or the transaction leaves the balances unchanged. A single-signature transaction carries a 5 000-lamport base fee before any optional priority fee. Since 1 SOL equals 1 000 000 000 lamports, that base component is 0.000005 SOL. New token holdings also require an associated token account, whose rent-funded balance appears separately from the pool fee. Versioned transactions and Address Lookup Tables let a route reference more accounts within Solana’s 1 232-byte transaction limit.

The wallet controls approval, while the on-chain programs determine the final token movement within the signed limits.

Where Raydium fits beside Jupiter, Orca and Meteora

When the goal is best execution across Solana rather than direct pool access, Jupiter broadens the search while Raydium remains one of its liquidity sources. Jupiter is an aggregator that compares routes across venues. Raydium operates pools and exposes direct liquidity controls, so the two services answer different parts of the trading decision.

Orca’s Whirlpools concentrates liquidity within chosen price ranges. Meteora’s DLMM arranges liquidity in discrete price bins and supports a different management model. Phoenix uses an on-chain central limit order book, so makers place bids and asks instead of funding an AMM curve. Raydium groups swaps, CPMM, CLMM, farms and LaunchLab under one Solana-focused interface. It is the stronger fit when direct pool creation or LaunchLab matters; Jupiter is broader for route discovery and Phoenix suits traders who specifically want order-book control.

Permissionless pools and LaunchLab graduation

When a project needs on-chain liquidity or a no-code token launch, Raydium offers permissionless pool creation and a bonding-curve path into an AMM. CPMM gives both assets full-range exposure, while CLMM lets the provider choose a price interval.

Creating a CPMM pool carries a 0.15 SOL Raydium protocol fee, separate from Solana account rent and transaction fees. The same 0.15 SOL charge applies to Standard AMM v4 creation. A CLMM pool has a 0 SOL Raydium creation charge, although its pool and position accounts still need rent funding. In CPMM, depositors receive fungible LP tokens that represent their proportional claim on both reserves; CLMM stores each managed range as a position NFT. The other half of this is described in Raydium alternatives.

LaunchLab begins before an AMM pool exists. Its program supports 3 curve types: constant-product as type 0, fixed-price as type 1 and linear-price as type 2. JustSendit supplies a default no-code configuration, while LaunchLab mode exposes supply, curve and graduation parameters. Trades move along the selected curve until the launch-specific graduation target is met. Remaining base tokens and accumulated quote assets then seed a CPMM pool, subject to the configured migration path. A creator chooses the main settings upfront, so the graduation amount belongs to that launch rather than every token on the platform.

That sequence gives a creator 1 continuous path from issuance to a pool with tradable secondary liquidity.

Who benefits from concentrated and constant-product liquidity?

Liquidity providers who prefer passive full-range exposure fit Raydium CPMM, while active managers gain more control from CLMM positions with defined lower and upper bounds. CPMM positions keep earning while swaps use the pool. CLMM fees accrue only when the market price sits inside the chosen range.

A CPMM deposit pairs 2 assets and mints fungible LP tokens representing a share of the whole pool. The position follows the constant-product curve across every price, which limits upkeep but leaves the provider exposed to the pair’s relative price movement. A CLMM position instead uses 2 price boundaries and an NFT with a supply of 1. Narrower ranges place more liquidity near the current price and increase capital efficiency. When price exits the range, active liquidity falls to 0 for that position and its assets become concentrated on one side.

Fee income is not yield on a static balance. It compensates providers for holding changing token inventories and, in CLMM, maintaining a useful range.

Raydium banner with blue-purple waves and three promotional phrases

A wallet-ready decision checklist

Before a first Raydium action, the deciding condition is whether the wallet, token addresses, SOL balance and transaction limits are ready together. Preparation removes most avoidable transaction failures before any signature is requested.

Connecting a wallet grants no blanket custody of its balances. Each swap, deposit, withdrawal or launch action requires a separate signed transaction. Start with the product that matches the task, then treat the displayed minimum output or liquidity range as the controlling boundary. A browser session is only the interface; Solana records the actual state.

How do Raydium pools set price and fees?

Raydium prices a swap from the selected pool’s curve, current reserves and active liquidity, while the pool configuration supplies the fee rate. A larger swap relative to usable liquidity moves farther along the curve, increasing price impact even when the stated fee stays unchanged. A multi-hop route applies each pool’s curve and fee in sequence.

CPMM uses the invariant x × y = k: adding input to one reserve removes output from the other while their adjusted product remains constant. CLMM applies similar swap steps only across active tick ranges. Raydium’s published CLMM configurations pair 4 base fee tiers - 0.01%, 0.05%, 0.25% and 1% - with tick spacings 1, 10, 60 and 120. The tick spacing is fixed when a pool is created. CPMM configurations use a 1 000 000-unit denominator for rates, where 2 500 represents 0.25%; the running pool configuration supplies the executable value.

For CPMM and CLMM trade fees, 84% goes to liquidity providers, 12% funds RAY buybacks and 4% goes to the treasury under the published split. Standard AMM v4 charges a 0.25% swap fee; its published division sends 88% to LPs and 12% to RAY buybacks. The router adds no independent percentage fee, so a route’s cost comes from its constituent pools, token-program transfer fees and Solana network charges.

Liquidity, token and transaction trade-offs

When token controls, shallow reserves or a narrow liquidity range dominate the position, Raydium users face losses that the interface cannot remove. Liquidity providers bear inventory exposure as the 2 assets change relative value. CLMM adds range risk because fee accrual stops once price leaves the configured interval. A CPMM position remains active, but its token mix shifts along the curve, which is detailed in Raydium walkthrough.

Token controls matter separately from pool math. Standard AMM v4 accepts classic SPL Token mints, while CPMM and CLMM support approved Token-2022 configurations. Their default extension allow-list contains 5 entries: TransferFeeConfig, MetadataPointer, TokenMetadata, InterestBearingConfig and ScaledUiAmount. A transfer-fee mint deducts its configured token charge in addition to the pool’s swap fee. Mint and freeze authorities also define issuer control over supply or token accounts. Before signing, the useful boundary is the wallet’s minimum received value, the mint’s program rules and the liquidity position’s chosen price range.

Raydium - your questions answered

Is RAY required to pay for a Raydium swap?

RAY is not required to execute a standard Raydium swap. Solana network fees are paid in SOL, while the selected pool deducts its configured trading fee from the swap amount. RAY is the protocol token connected to buybacks and staking, but a wallet swapping USDC for another Solana token does not need to hold it. The wallet still needs enough SOL for signatures, optional priority fees and any new associated token account.

Can a Raydium CLMM position NFT be transferred to another wallet?

A Raydium CLMM position can move to another wallet by transferring the NFT that represents its ownership. The PersonalPositionState is associated with that NFT, so fee-collection and liquidity-management authority follows the token’s owner. The receiving wallet needs Solana support for the position NFT and enough SOL for later transactions. CPMM positions work differently: ownership is represented by fungible LP tokens, so transferring those tokens transfers the corresponding redeemable pool share.

How long does a Raydium swap take to confirm?

Raydium swap confirmation follows Solana transaction processing rather than a protocol-defined waiting period. A recent blockhash is valid for 150 slots, which bounds how long an ordinary signed transaction remains eligible for inclusion. Congestion, priority fees, route complexity and RPC performance determine where confirmation lands within that window. If the blockhash expires first, the swap does not execute and the wallet must build a fresh transaction from a new quote.

Does Raydium require an identity-verified account?

Raydium’s on-chain programs do not require a username or identity-verified trading account. Access begins with a compatible Solana wallet, and the wallet address identifies positions and transaction history. A third-party wallet, fiat service, aggregator or regional interface can apply its own eligibility and account rules. Those service-level requirements sit outside the AMM programs. A user still needs SOL for network costs and supported tokens in wallet accounts before signing a swap or liquidity action.

When can a signed Raydium swap be cancelled?

A Raydium swap cannot be cancelled after Solana has confirmed the transaction. Before broadcast, a wallet can discard the unsigned or signed message without changing on-chain balances. After broadcast, validators either execute the atomic instruction set or leave it unexecuted if it fails or expires. There is no order sitting open for a normal AMM swap. Limit orders or perpetual positions use separate mechanisms and should not be treated as ordinary token swaps.

How are Raydium liquidity-provider fees claimed?

Raydium fee claiming depends on whether the position uses CPMM, Standard AMM v4 or CLMM. In CPMM and AMM v4 pools, the LP share stays within the pool’s accounting and is realized when LP tokens are redeemed for reserves. CLMM tracks fee growth for each position, so the position owner collects accrued fees directly without closing the range. Farm rewards use separate reward schedules and claim instructions. A displayed APR combines changing inputs and is not a fixed protocol return.