Raydium is a Solana DEX that routes swaps across AMM liquidity pools

Price impact is the first constraint to inspect

Price impact, rather than the displayed pool fee, is the largest execution constraint when a Raydium order is large relative to the liquidity available along its selected route.

The quote separates the pool fee, price impact, and slippage tolerance. The pool fee follows the selected pool configuration. Price impact is the reserve-curve movement caused by the order itself, so it rises as an order consumes a larger share of active liquidity. Slippage tolerance sets the worst output that the signed transaction accepts while pool state changes between quotation and settlement. In a labeled hypothetical, a 1,000-unit input into a 0.25% pool pays 2.5 units in pool fees before price impact.

A smaller order receives a better curve price when every other input stays equal. If actual output falls below the minimum in the transaction, the swap reverses while the network fee remains charged. Splitting the order or checking broader venue coverage through Jupiter offers a more useful response than simply widening slippage.

Jupiter, Orca, Meteora, and Phoenix separate the venue choices

Jupiter, Orca, Meteora, and Phoenix address different Solana trading decisions, so Raydium fits users who want direct access to its AMM liquidity and pool-management tools.

Jupiter for cross-venue routing

Jupiter is a Solana aggregator that compares liquidity across Raydium, Orca, Meteora, and other integrated venues. It suits a swapper whose priority is venue breadth and a competitive final quote, especially when one protocol lacks sufficient depth. A Jupiter route still inherits the fee, curve, token-program rules, and liquidity of every underlying pool that it selects.

Orca and Meteora for alternative liquidity models

Orca centers its liquidity product on Whirlpools, a concentrated-liquidity AMM where positions occupy chosen price ranges. Meteora offers Dynamic Liquidity Market Maker pools that organize liquidity into discrete price bins. Raydium combines CPMM, CLMM, legacy AMM v4 pools, and LaunchLab migrations in one product family. The relevant comparison is the specific pair, active depth, fee configuration, and amount received, rather than the protocol name alone, which is covered in Using Raydium.

Phoenix for an order-book workflow

Phoenix provides an on-chain central limit order book, making it the clearer alternative for explicit limit prices and resting orders. Raydium executes current AMM v4 swaps only against the pool curve because the former OpenBook liquidity connection has been deactivated. That distinction separates immediate pool execution from an order-book strategy (more on this in Raydium app ).

Wallet, mint, and quote checks set up the first swap

A first Raydium swap requires a Solana wallet, enough SOL for network costs, the exact input and output mints, and a quote whose route matches the intended trade.

Wallet connection and fee balance

Phantom and Solflare both connect to Solana applications and present transactions for signature. Connecting shares the public wallet address; it does not move tokens or approve a swap. Keep SOL in the same fee-paying wallet because token balances such as USDC, USDT, or RAY cannot pay Solana transaction fees.

Mint identity before symbol recognition

Token symbols do not uniquely identify a Solana mint. Use the intended mint address when selecting an unfamiliar asset, then confirm that its token program is SPL Token or a supported Token-2022 configuration. Solscan and Solana Explorer show the mint owner, decimals, supply, and token-account activity without relying on the displayed symbol.

Quote review before signature

Raydium defaults to an exact-input quote: the user fixes the amount spent, while the interface computes expected output and a minimum output from slippage. Review the pool type, every route hop, price impact, pool fee, transfer fee, and priority fee. Priority fees influence transaction scheduling, not the pool price or output calculation. The signature authorizes that assembled transaction, so a fresh quote is necessary after changing the amount, mint, or tolerance.

Pool fees and Solana fees are separate costs

Even so, Raydium charges the fee that each selected pool defines, while Solana separately charges the transaction signer a network fee and any requested priority fee for execution.

CPMM commonly exposes 0.01%, 0.25%, and 1% pool-fee tiers, while the standard AMM v4 configuration charges 0.25%. A 0.25% fee removes 2.5 units from a 1,000-unit input before curve-driven impact. In CPMM and CLMM pools, 84% of the trading fee supports liquidity providers, 12% funds RAY buybacks, and 4% goes to the treasury. Standard AMM v4 assigns 88% to liquidity providers and 12% to buybacks.

Solana charges a base fee of 5,000 lamports per signature, and 1 SOL contains 1,000,000,000 lamports. An optional priority fee equals the requested compute-unit limit multiplied by its price in micro-lamports, divided by 1,000,000 and rounded up. These network fees pay for processing and remain separate from the amount that a Raydium pool collects.

Constant-product pools trade precision for full-range coverage

On those terms, Raydium CPMM and AMM v4 pools on Solana use the invariant x × y = k, creating continuous prices from paired reserves through all possible reserve ratios. A swap changes reserves; larger moves face steeper impact as their balance shifts. LP tokens record proportional ownership, while trading fees enlarge claimable reserves. CPMM supports suitable Token-2022 mints for new full-range pools. AMM v4 remains operational without Token-2022 support. Creating either pool carries a 0.15 SOL protocol fee before account rent.

Concentrated liquidity exchanges passive coverage for capital efficiency

Concentrated-liquidity positions on Raydium place liquidity between chosen price boundaries, producing deeper usable reserves inside that interval while requiring more maintenance than a full-range constant-product deposit.

Active ranges and idle capital

A CLMM position earns trading fees only while the market price crosses its active range. Narrow boundaries concentrate the same token value around the current market, which improves quotes without placing capital across unused distant prices. Once price leaves the interval, the position becomes one-sided and stops contributing active liquidity until price returns. The provider then chooses among waiting, withdrawing, or establishing new boundaries. This range decision drives capital efficiency, inventory composition, and maintenance frequency together.

Fee tiers and tick spacing

In the common configuration, Raydium CLMM configurations pair 0.01%, 0.05%, 0.25%, and 1% fees with tick spacing of 1, 10, 60, and 120, respectively. Smaller tick spacing permits finer range boundaries. A pool binds to its configuration when created, so liquidity providers must select the intended pool rather than changing the fee tier on an existing position.

Position maintenance

CLMM fees accrue to the individual position and remain claimable through the fee-collection flow. Moving a range means removing liquidity from the old boundaries and opening liquidity at new boundaries, each through wallet-signed instructions. Full-range CPMM liquidity demands less range management, while Raydium CLMM rewards closer attention with more targeted capital.

Token standards alter compatibility and received amounts

Pool compatibility on Raydium depends on the mint owner and enabled extensions, because classic SPL Token and Token-2022 pass different account data and transfer rules into swaps.

CPMM and CLMM allow five standard Token-2022 extensions at pool creation: TransferFeeConfig, MetadataPointer, TokenMetadata, InterestBearingConfig, and ScaledUiAmount. Other configurations require an explicit supported path. AMM v4 and Stable AMM accept classic SPL Token mints rather than Token-2022 mints.

TransferFeeConfig changes the amount that reaches a pool vault or wallet. Its charge belongs to the token mint configuration, not the Raydium pool fee, and a transfer-fee mint can apply a rate plus an absolute cap. A useful quote separates these amounts and shows received output after the expected transfer charge. This makes the exact mint and token program material parts of route selection.

Routing combines pool quotes without changing their curves

The Raydium router links eligible AMM v4, CPMM, CLMM, and Stable AMM pools into one atomic Solana transaction while leaving price calculation inside each underlying pool program.

The router supports exact-input and exact-output swaps. In the first mode, each hop consumes the previous hop's output; in the second, the route works backward from the requested final amount. Intermediate assets pass through user-owned associated token accounts, and every hop charges its own configured pool fee. If any instruction misses its minimum output, maximum input, account requirement, or CLMM price limit, the complete transaction reverses rather than settling a partial route.

The router itself adds no separate routing fee. Client software can also place multiple pool-swap instructions in one transaction, which offers more flexibility for external venues. Direct Raydium routing fits all-Raydium paths, while Jupiter provides broader cross-venue comparison.

Liquidity fees compensate for inventory and range exposure

Liquidity providers on Raydium receive a defined share of trading fees, but their position value changes as swaps rebalance reserves and the market moves between the two deposited assets.

In a constant-product pool, arbitrage keeps the curve near the wider market by exchanging one reserve for the other. The LP therefore owns a changing quantity of both tokens, creating impermanent loss relative to holding the same starting assets when their relative price diverges. CLMM adds boundary risk: an out-of-range position becomes concentrated in one asset and earns no trading fees until price re-enters. Fees offset exposure only when sufficient volume crosses active liquidity.

Farm rewards form a separate incentive layer and use their own reward token and schedule. They do not alter the pool invariant or remove inventory exposure. Compare fee income, reward emissions, range maintenance, and withdrawal flexibility with simply holding the two assets.

RAY links protocol revenue to the wider product suite

RAY is Raydium's six-decimal SPL token, used across the suite for staking and liquidity while protocol fee accounting directs part of trading fees toward transparent on-chain buybacks.

The fixed maximum supply is 555,000,000 RAY, and the mint authority is disabled. Buybacks receive 12% of the trading fee, not 12% of total trade volume. Holding RAY is unnecessary for swaps, pool deposits, pool creation, or Raydium Perps. Elsewhere in the suite, LaunchLab moves graduated bonding-curve liquidity into CPMM pools, while the Perps interface uses Orderly Network infrastructure. These products share an interface but retain distinct mechanics, fees, and positions.

A route-level checklist keeps the decision grounded

A Raydium decision is ready for signature when the chosen mint, pool configuration, route output, network cost, and liquidity commitment all match the user's intended action.

• Match each token symbol to its exact Solana mint and token program.
• Compare expected output after pool fees, transfer fees, and price impact.
• Confirm that the fee tier suits the pair and intended order size.
• Keep enough SOL for the 5,000-lamport base fee, priority fee, and any new account funding.
• Choose CPMM for full-range exposure or CLMM only with a range-maintenance plan.

For a simple swap, the signed transaction ends the decision. A liquidity position continues until the provider collects fees and withdraws or repositions the assets. If venue breadth matters more than direct pool management, compare the same amount through Jupiter before signing.