Raydium is a Solana Decentralized Exchange Built for Practical Token Swaps

Pool Fees, Network Fees and Account Funding

On a first pass, Raydium's confirmation panel separates the pool fee, Solana network fee and any funding needed for a new token account. A pool fee reduces quoted output, while the network fee and account funding come from SOL.

Solana charges a base fee of 5,000 lamports per signature, and 1 SOL contains 1,000,000,000 lamports. The optional priority fee equals the requested compute-unit limit multiplied by its micro-lamport price, rounded up after division by 1,000,000. Solana sets a 200,000-compute-unit default for each non-builtin instruction and a 1,400,000-compute-unit maximum for one transaction. Raydium's automatic priority setting chooses a price from network conditions; paying more changes scheduling priority, not the swap price.

The route supplies the relevant pool rate. Standard AMM v4 parameters encode 25 fee units over 10,000, equal to 0.25%, while published CLMM configurations include 0.01%, 0.05%, 0.25% and 1% tiers. A Token-2022 transfer fee appears separately because the mint, rather than the pool, defines it. Creating a classic 165-byte SPL Token account also needs a rent-exempt SOL balance, which returns when an eligible empty account closes.

Wallet Readiness Before a Quote

Wallet readiness for Raydium starts with Solana Mainnet, V0 transaction support and enough SOL beyond the amount being swapped.

Network and Transaction Format

Phantom, Solflare and Backpack connect through Wallet Adapter and support the V0 messages used by Raydium routes. Address Lookup Tables replace a 32-byte public key with a 1-byte lookup index, saving 31 bytes for each resolved account. That compression matters because a Solana transaction fits within 1,232 bytes, while each Ed25519 signature occupies 64 bytes. Confirm that the wallet shows Solana Mainnet and the intended public address before requesting a quote.

SOL Headroom

The spendable SOL balance must cover the input amount, the 5,000-lamport signature fee, the selected priority fee and any account funding. Entering the wallet's full SOL balance as input leaves nothing for those deductions. When SOL is the input asset, the transaction also converts the swap amount into wrapped SOL for the token-program instruction path.

Token Account Readiness

Each fungible asset sits in a token account associated with a wallet owner, a mint and either the SPL Token Program or Token-2022. The Associated Token Program derives that address from those three inputs. If the output account is absent, Raydium normally adds its creation instruction to the swap transaction, with the wallet paying the rent-exempt balance in SOL.

Does the Token Selection Match the Intended Mints?

The token selection matches only when both mint addresses, token programs and displayed symbols correspond to the assets you intend.

A mint address is a 32-byte public key that identifies the asset independently of its symbol or logo. Check the From and To direction, then expand the token details and match each mint. USDC and RAY provide familiar symbols, yet the selected mint still controls the pool and destination account. The program owner matters too: an original SPL Token mint and a Token-2022 mint follow different account layouts and extension rules.

Read the amount in base units through the mint's declared decimals, rather than inferring precision from the input box. The wallet simulation should show the same input mint decreasing and output mint increasing. If either address or direction differs, close the prompt and rebuild the quote with the intended pair.

Route, Price Impact and Slippage Before Signing

The Raydium route panel shows how the quote reaches the output mint and where execution costs enter the amount received.

A single-pool route invokes one CPMM, CLMM or AMM v4 pool. A multi-hop route moves an intermediate token through two or more pools, and a split route allocates portions across several pools. All route shapes settle as one transaction. Each hop contributes its own configured fee and curve movement. The interface documents a 10-second re-quote cycle, defaults to exact-input mode and starts with 0.5% slippage. Those interface settings remain editable, so read the values attached to the transaction rather than relying on an earlier screen.

Price impact measures the quote's movement along pool liquidity; slippage tolerance defines the worst acceptable change between quote and execution. For an exact-input swap, the transaction sets minimum output as quoted output multiplied by one minus the slippage fraction. One percent equals 100 basis points, while 0.5% equals 50 basis points. Compare the expected output, minimum output and route fee before opening the wallet.

What Does the Wallet Signature Authorize?

A Raydium wallet signature authorizes the exact Solana message displayed, including its accounts, instructions, amount limits and recent blockhash. The supporting detail is gathered in Raydium alternatives.

The preview should identify the connected wallet as signer and fee payer, then show the intended input debit and output credit. It may include Compute Budget instructions, Associated Token Account creation, wrapped SOL handling and a CPMM or CLMM swap call. Each instruction shares one transaction outcome. A clear preview therefore connects the quoted amount, minimum output and network fee to the message that the private key signs.

A recent Solana blockhash remains processable for a maximum age of 150 slots, roughly 60 to 90 seconds at ordinary slot times. A long pause on a hardware wallet such as Ledger can consume that window. If the message expires, request a fresh quote and blockhash instead of repeatedly broadcasting the old signature. A higher priority fee affects scheduling, while a new quote refreshes the executable limits.

The Atomic State Change After Execution

A successful Raydium swap changes the input account, pool accounts and output account together inside one atomic Solana transaction.

Input Account Debit

The SPL Token Program debits the exact input token account named in the message. With native SOL, the System Program first funds a wrapped SOL token account and Sync Native updates its token amount. The wallet's SOL change therefore combines the swap input, network fee and any rent-exempt account funding rather than representing only the pool trade.

Pool Route Execution

The Raydium program reads the selected pool state, moves input into its vault and calculates output from that pool's curve and fee configuration. A CLMM route also reads the active tick arrays, while CPMM follows its constant-product state. Multi-hop execution feeds one hop's output into the next within the same transaction. Solana processes the instructions in order and commits every state change together; a failed instruction rolls back the token movements while the network still charges the transaction fee.

Output Account Credit

The token program credits the destination account for the output mint with the executed receipt amount. If the transaction creates that Associated Token Account, creation and credit settle together. Raydium then reports the signature and actual received quantity, giving the wallet a direct link between one signed message and one output-token balance increase.

How Do You Verify the Output Token Receipt?

The output token receipt is verified by matching one successful signature to the wallet signer and both token balance changes.

Open the signature from Raydium's completion message or the wallet history in Solscan or Solana Explorer. Confirm that Status reads Success and the signer equals the wallet that approved the swap. Next, inspect pre-token and post-token balances for the exact mint addresses. The input account should decrease by the executed amount, while the output account should increase by the actual receipt. Review the separate SOL fee and any new account funding so neither gets mistaken for pool price impact.

A wallet interface may hide an unfamiliar output account even after the network records it. The explorer's token-balance delta remains the decisive receipt record.

Match the account owner, mint and token program before importing that asset into the wallet view. For a multi-hop route, intermediate transfers explain extra pool activity, but the user-facing receipt remains the final destination-account increase tied to the same signature.

Recovery From a Missing Output Token Account

A missing output token account usually means the Associated Token Account was absent, unsupported by the wallet or not created.

Rebuild the Destination Account Instruction

First refresh Raydium, reconnect the same wallet and select the output mint again. A modern V0-compatible wallet lets the transaction include an Associated Token Program instruction before the swap call. That instruction derives the account from the wallet owner, output mint and token program, allocates the required account size and funds its rent-exempt balance. Re-quote after the account plan changes because the SOL requirement and transaction message have changed.

If the wallet cannot display or sign that account-creation instruction, update it or switch to another maintained Solana wallet that supports V0 and Token-2022.

Separate Account Absence From a Display Delay

A failed transaction with an account-related error produced no output credit, so rebuild and sign a fresh message. A successful explorer record tells a different story: find the destination token account in the post-token balances and match its owner and mint. When that delta exists, refresh the wallet's asset list or add the mint through its supported import flow. Do not repeat the swap merely because the wallet dashboard has not rendered the account.

This recovery path resolves the setup error at its source: one deterministic destination account for the selected wallet, mint and token program.

Token-2022 Transfer Fees and Wrapped SOL Edge Cases

Token-2022 transfer fees and wrapped SOL change receipt accounting, so their preflight fields deserve a separate final review.

A Token-2022 mint can enable TransferFeeConfig, which expresses its rate in basis points and sets a maximum fee in the token's smallest units. The rate denominator is 10,000 basis points, making 100 basis points equal to 1%. Raydium separates the pool fee from the mint transfer fee and quotes net output after the applicable transfer charge. A newly scheduled transfer-fee configuration activates two epochs later, so the transaction must use the active configuration at execution. Extension-bearing token accounts can also exceed the classic 165-byte layout.

Wrapped SOL gives native SOL the token-account form required by the SPL Token Program. One wrapped SOL represents one SOL, and both use nine decimal places, so 1 lamport remains the smallest unit. Raydium's transaction can create, synchronize and close a temporary wrapped SOL account around the swap. If wrapped SOL remains after an interrupted flow, the wallet's unwrap action closes the account and returns its SOL balance.

A Go-or-Wait Decision Checklist

The Raydium go-or-wait checklist turns the preview into five concrete conditions that must all hold before signing. Use the displayed transaction, not memory from the prior quote.

• Wallet: Solana Mainnet, the intended address and V0 support are all present.
• Funding: SOL remains for the 5,000-lamport base fee, priority fee and any destination-account funding.
• Assets: Input and output mints, token programs and direction match the intended exchange.
• Quote: Expected output, minimum output, route, price impact and each displayed fee fit the decision.
• Receipt Plan: The resulting signature will be checked for Success, signer and exact token-balance deltas.

Wait and regenerate the transaction whenever one condition changes, including a refreshed quote, switched wallet or newly created token account. Signing after all five checks produces an auditable path from selected mints to confirmed output token units.