Raydium Solana is a Decentralized Exchange Offering Concentrated Liquidity Market Maker Pools

A Manageable First Position for Hands-On Liquidity Providers

A first Raydium CLMM position gives hands-on liquidity providers a defined range, visible token inventory and a reversible exit path. It turns one allocation into an observable on-chain position.

The workflow starts with a pool that already contains the required two mints. You select a lower price and upper price around the current tick, then let Raydium calculate the compatible deposit ratio. After approval, the CLMM program records liquidity against those two boundaries and mints a position NFT to the signing wallet. Swaps move the pool tick and continuously change the position’s token composition while it remains inside the range. A decrease returns part of that inventory; a full decrease followed by collection and closure completes the exit.

That lifecycle suits a user who wants explicit control over where capital participates. It also creates a maintenance obligation: range placement stays fixed for the life of that NFT, even as the pool’s price moves. Changing the boundaries means reducing the old position and opening another.

Use the first position to learn the state changes, then size later deposits around the same evidence.

Wallet, Token and Balance Prerequisites

Raydium CLMM prerequisites are a compatible Solana wallet, both pool tokens and enough native SOL to finish account operations. The displayed public key identifies the position owner.

Phantom and Solflare both expose SPL Token balances and the position NFT created by the deposit. A Ledger device can back either wallet, although its screen may present several instructions for one CLMM action. Hold each mint required by the selected pool, because an in-range position normally draws from both. Keep native SOL separate from the amount destined for liquidity. Solana records 1 SOL as 1,000,000,000 lamports, and a zero native balance prevents the wallet from paying for transaction execution or new accounts. That reserve remains outside the two-token position.

Check whether each mint uses the original SPL Token program or Token-2022. Raydium supports both in CLMM flows, but mint extensions alter what the wallet preview shows. Token identities come from mint addresses, so symbols such as USDC and USDT should match the intended on-chain mints before range selection.

Pool Identity and Token Order Before Range Selection

A Raydium CLMM pool fixes the token pair, quote orientation and tick spacing that every later range decision must respect. Choose the existing CLMM market rather than a similarly named CPMM pool or another mint pair.

Read both mint addresses and decide which unit the displayed price uses. A SOL/USDC panel might show USDC per SOL; reversing the quote produces a reciprocal number and also reverses how lower and upper labels feel. The underlying range remains the same pair of ticks. PoolState supplies the current tick, while AmmConfig supplies the permitted spacing. Those values belong to the chosen pool, so switching to another pool for the same symbols creates a separate position with separate boundaries. The Raydium interface translates those pool fields into range controls, while Raydium SDK V2 exposes the same fields for programmatic users.

Use mint addresses, the CLMM badge and the current quote direction as the three identity checks. This keeps a correct range calculation attached to the intended market.

How Wide Should Your First Range Be?

Your first Raydium CLMM range should cover the price interval you are prepared to manage as one position. Narrow bounds concentrate liquidity into fewer ticks; wider bounds keep the position active across a larger move. The token ratio follows the current price’s location inside those bounds.

The current tick must lie between the selected boundaries for a two-sided active deposit. Moving either endpoint changes the square-root liquidity math, which changes the matching amount of the second token. Raydium snaps typed prices to valid ticks, so the executable lower and upper prices may differ slightly from the displayed targets.

Worked example: every changing input here is hypothetical: token0 is SOL, token1 is USDC, the current price is 100 USDC per SOL, the range runs from 81 to 121 and the wallet holds 10 SOL plus 1,000 USDC. The square roots are 10, 9 and 11. The CLMM formulas reduce to amount0 = L/110 and amount1 = L, producing a matching ratio of 110 USDC per SOL.

With 1,000 USDC as the limiting balance, the deposit pairs 9.09 SOL with 1,000 USDC and leaves 0.91 SOL in the wallet. Tick snapping and integer rounding adjust the final quote slightly. The calculation still reaches a concrete planning result: the range determines how much of the second token fits the first.

Tick Spacing Turns Prices Into Executable Boundaries

Tick spacing converts each Raydium CLMM price boundary into an integer endpoint that the on-chain program accepts. Raydium maps each tick to a 1.0001 price multiplier, equal to a 0.01% step or about 1 basis point. A target price therefore lands on the nearest usable tick rather than an arbitrary decimal.

Valid CLMM endpoints sit between tick -443636 and tick 443636. Common Raydium pool configurations use spacing values of 1, 10, 60 and 120. Those spacings permit every tick, every 10th tick, every 60th tick or every 120th tick respectively. Their approximate boundary resolutions are 0.01%, 0.10%, 0.60% and 1.21%. The pool configuration chooses one spacing, and both endpoints must be exact multiples of it. Off-spacing values never become a position.

During normal operation, Raydium packs 60 adjacent usable ticks into each TickArrayState. At spacing 60, one array covers 3,600 integer-tick units. The inline PoolState bitmap tracks 1,024 arrays on each side of tick zero, while an extension covers farther ranges. Range width affects which endpoint arrays the opening transaction must supply.

On-chain prices use Q64.64 square-root fixed point, which reserves 64 fractional bits. The interface translates that representation into human prices after applying both token decimal scales. This mechanism explains why a neat decimal target turns into a slightly different executable boundary.

Balancing the Two Token Inputs

A Raydium CLMM deposit funds the maximum usable liquidity with the token that reaches its quoted limit first. Enter one amount, then treat the second amount as a calculated consequence of the range.

An in-range position holds 2 token types, and the mix changes as the current tick approaches either endpoint. Exactly at or beyond one side, the position resolves to 100% of one pool token; the quote orientation determines which token that is. Raydium performs the arithmetic in integer base units. Wrapped SOL uses 9 decimal places, while Circle-issued USDC on Solana uses 6. Token-2022 mints carry their own decimal setting, so the mint data controls display conversion.

Review the maximum for both tokens in the wallet approval. The first amount represents the chosen budget; the second reflects range geometry, current tick and rounding. A moved quote requires recalculation before signing.

What Does the Wallet Approval Create?

Wallet approval opens one Raydium CLMM position, transfers its token amounts and creates the ownership records required for later management. The wallet may display several program instructions for that single action.

The position NFT mint has supply 1, and its associated token account holds that single unit. PersonalPositionState records 2 tick indexes, the pool identifier, liquidity and growth snapshots. Ownership follows the wallet that holds the NFT account. Depending on the pool mints, Raydium creates the position through SPL Token or Token-2022 instructions, while the CLMM program remains the authority over position state.

The same approval may create missing associated token accounts or initialize an endpoint TickArrayState. Solana executes the instruction set atomically: every required state change succeeds together or the deposit state rolls back. A successful signature therefore leaves a usable position record and its matching NFT.

Confirmation Checks That Prove the Position Exists

Position verification requires the Raydium portfolio record, the position NFT and a successful Solana transaction signature to agree. The portfolio should show the intended pool, 2 boundaries, deposited token amounts and current range state. Phantom or Solflare should display the NFT, while Solana Explorer or Solscan can show the successful instructions and account changes. Matching the NFT mint to PersonalPositionState ties the visible card to the on-chain position.

Reading In-Range and Out-of-Range States

Range monitoring follows the Raydium CLMM current tick because that value determines inventory composition and whether liquidity is active. The interface reduces that relationship to three visible states.

On chain, the in-range test is lower tick ≤ current tick < upper tick. The lower endpoint is inclusive and the upper endpoint is exclusive, an asymmetry that matters exactly at a boundary. While the tick stays inside, swaps move the position gradually between its 2 tokens. Below the lower endpoint or at and above the upper endpoint, the position holds 100% of one token. Returning through the boundary reactivates the stored liquidity without minting a new NFT or changing its endpoints. The interface translates those comparisons into in-range and out-of-range labels, but the tick inequality is the controlling state.

Watch the current price relative to both boundaries rather than only watching the token balances. Inventory changes are part of the range mechanism, not a separate trade placed by the wallet. If the original interval still fits the plan, an out-of-range position can remain open and reactivate when price returns.

When the interval no longer fits, decrease the old position and select new endpoints for a separate NFT.

How Do You Withdraw and Close the Position?

A clean Raydium CLMM exit reduces liquidity, settles the two token balances and closes the position account after it reaches zero. Partial and full withdrawals begin from the same position card.

Choose Decrease, set the removal amount and review both returned mints before signing. A partial DecreaseLiquidity call leaves the NFT, tick boundaries and remaining liquidity intact. A 100% decrease sets position liquidity to 0, after which pending token amounts and any displayed rewards must be collected. ClosePosition then burns the position NFT and releases rent from closable position accounts. These are distinct state changes even when the interface batches them into a short sequence.

Verify the exit at both levels. The wallet should show the returned SOL, WSOL, USDC or other pool tokens, and the Raydium card should show zero liquidity before closure. The final signature should include the close instruction; after it confirms, account closure marks the lifecycle complete.

From Selected Pool to Closed Position

The Raydium solana workflow has 6 observable states from wallet readiness through an empty, closed position. Each state leaves a record that supports the next decision.

At the readiness state, the wallet holds the required pool tokens and native SOL. Pool selection then fixes mint order and tick spacing. The range quote establishes 2 executable endpoints and a compatible token ratio. Approval transfers tokens, creates one position NFT and records liquidity. Confirmation ties that NFT to its on-chain state. Monitoring continues until a decrease returns inventory, and closure finishes the position after liquidity reaches 0.

A second page describes it in detail. Following the interface, wallet and transaction evidence keeps the first deposit and exit bounded to one position lifecycle.