Raydium
Raydium carries a reviewed Solana swap quote through signing, execution, and balance reconciliation
Raydium turns selected input and output tokens into a route-specific quote, then encodes the accepted limits in a Solana transaction awaiting wallet authorization. Review the expected output or required input, the applicable slippage limit, route, price impact, and fees before signing. After confirmation, reconcile the transaction status and token balance changes with the quote. A rejected limit, an expired submission, or a hidden token account requires a different check; none proves the exchange completed.
Updated on
Quote fields that govern execution
An exact-input quote fixes the amount offered to the pools, calculates an expected output, and sets a minimum output. An exact-output quote fixes the desired output, calculates the required input, and sets a maximum input. During reconciliation, the first mode anchors the amount spent, while the second anchors the amount received.
For an exact-input quote, the expected output is an estimate based on the pool state used for the quote. Its minimum output is the lower acceptance boundary derived from the slippage setting. An exact-output quote instead uses a maximum input as its upper boundary. If execution cannot satisfy the applicable boundary, the swap fails instead of accepting a worse result. Increasing the tolerance allows a lower output or a higher input, depending on the quote mode.
The route may use one pool, sequential pool hops, or a split across eligible liquidity. Review its quoted output or required input after pool fees and price impact rather than treating the displayed exchange rate as a separate promise. Fee configurations can vary by pool, and a token mint may impose its own transfer fee. The quote presented for the transaction is therefore more useful than a universal fee assumption.
How does a routed quote execute atomically?
A routed quote executes atomically when all its pool instructions are in the same Solana transaction. On a multi-hop path, each hop passes its output into the next. Exact-input execution checks the final output against the minimum, while exact-output execution checks the required input against the maximum. Each pool program applies its own pricing curve and configured fees. The router coordinates those instructions; it does not replace their pricing logic or obtain a new quote midway through execution.
A multi-hop path carries the first pool's net output into the second pool. Any reduction at an early hop therefore affects the amount available later. The final quote already reflects this relationship. Compare expected output across exact-input routes or required input across exact-output routes.
When every Raydium route hop is included in one Solana transaction, a failed hop prevents the route from settling partially. A route can still fail when a pool changes after quotation and the final amount falls outside the accepted bound. When a refreshed quote selects another path, review its output, limits, and costs as a new proposal.
The signing boundary
A displayed quote is a calculation, while a signature authorizes the transaction message. Confirm the input mint, output mint, fixed input or output amount, and applicable slippage limit before approving it. Mint addresses identify tokens on-chain; a familiar ticker or name alone cannot establish the selected asset.
The priority fee belongs to transaction scheduling rather than pool pricing. Paying a higher priority fee may improve the chance of timely processing during congestion, but it does not improve the quoted exchange rate. A delayed transaction can still encounter changed pool state before execution.
The wallet also needs enough SOL for network charges and any token account creation included in the transaction. Check the SOL balance before signing because insufficient funds for fees or account creation can stop execution before the swap reaches the pools.
A controlled retry after a stale quote
Consider an attempt with a fixed input amount and a chosen output mint. The initial quote meets the reader's acceptance threshold, but pool state changes before execution. If the final output would fall below the encoded minimum, the transaction fails at that limit instead of completing at the poorer amount.
Compare the first attempt and its retry using the same dimensions. The first action ends with the recorded limit failure. The second begins with a fresh quote, not a copied transaction or an unchanged assumption about the route.
Use this decision checklist before authorizing the replacement:
- Confirm the input and output mint addresses still match the intended exchange.
- Read the refreshed expected output and minimum received amount.
- Accept the retry only if its minimum output still meets the original threshold.
- Compare the new route, price impact, and fee disclosures with the failed attempt.
- Check the SOL balance, sign once, and retain the replacement signature.
A changed route is not automatically a problem. The retry is acceptable when its own limits and costs fit the intended exchange. If they do not, stopping preserves the input balance without broadening the slippage setting merely to force execution.
Why can a successful swap be missing from the wallet?
A successful on-chain swap may be absent from the wallet display because the interface has not refreshed or has hidden the output token account. Start with the transaction signature and its execution status rather than the activity label shown by a wallet.
Confirmed transaction metadata can expose pre-swap and post-swap token balances for the accounts involved. Match those entries by owner and mint address. Look for a decrease in the selected input token and an increase in the selected output token, while accounting for the transaction's recorded fees and account operations.
A hidden token account changes presentation, not settlement. Refreshing the wallet or enabling the verified output token may reveal the balance. Do not add an asset solely because its symbol resembles the expected token; reconcile the exact mint selected in the quote.
Separating rejection, expiration, and confirmation
A missing or pending transaction record is not proof of a completed swap.
If the chain reports an execution error, the swap state did not settle, although the network fee may still be charged. A slippage rejection means the transaction encountered a result outside its accepted output boundary.
An expired or dropped submission also produces no successful token exchange. Before approving a replacement, check the earlier signature again. A delayed status display should not prompt a second authorization while the first attempt remains unresolved.
A successful record moves the task to balance reconciliation. An execution error calls for a fresh quote, while an unresolved status calls for more confirmation evidence.
Reconciling the quote with on-chain balances
Begin with the input and output token accounts belonging to the signing wallet. Compare their balances before and after the transaction using the selected mint addresses. For an exact-input swap, the spent amount is the anchor. The received amount should meet the encoded minimum, although it may differ from the earlier expected output. For an exact-output swap, the received amount is the anchor, and the total input should not exceed the encoded maximum.
Token quantities are recorded in each mint's smallest units, while interfaces apply the mint's decimal precision for display. Rounding can create a small visual difference without changing the raw amount. Very small trades may also produce no usable output after integer calculations, causing the swap to reject.
Separate SOL network costs from the token exchange. The balance change may include the base transaction fee, an optional priority fee, and funding for a newly created token account. If SOL is also the selected input or wrapped during execution, inspect the transaction's account operations before assigning every SOL change to one cause.
Token-2022 mints may apply transfer fees on input, output, or both transfers. For supported pool types, Raydium accounts for input-side fees in the swap calculation and can show the expected net receipt after an output-side fee. For an exact-input swap, however, the on-chain minimum output is checked against the pool's gross output before that fee. If displayed totals still do not reconcile, compare raw balances across every account owned by the wallet for the relevant mint before attempting another swap.
When to abandon the current route
Do not sign when the minimum output already misses the intended threshold. A very small quoted output or severe price impact can indicate insufficient liquidity for the requested size. A smaller input, a different available route, or a later quote may produce a better boundary, but each choice needs its own review.
Repeated slippage failures do not justify an unlimited tolerance. A wider limit permits a worse execution and may leave more room for adverse price movement. Splitting a trade reduces each order's size, but it does not guarantee a better total output. Each transaction also has its own network fee, and pool conditions can change between submissions.
Proceed only when the current quote, encoded limit, route costs, wallet balances, and token identities satisfy the original acceptance condition. Choose another route or trade size only after reviewing a new quote.
Practical questions about Raydium
Does a higher priority fee improve the Raydium swap quote?
No. A priority fee affects how a Solana transaction competes for scheduling, not the pool price or expected token output. The quote may change while the transaction waits because pool state can move, but paying more for priority does not directly create a better exchange rate.
Can an exact-input swap return less than the expected output without failing?
Yes. The expected output reflects the state used for quotation, while the minimum output defines the accepted floor for an exact-input swap. Execution can return less than expected when pool conditions change. The swap still succeeds if the pool's output remains at or above the encoded minimum.
Why did my SOL balance fall by more than the network fee shown?
The transaction may have paid a priority fee or funded a new token account for the output mint. If SOL was also the swap input, its balance includes that spend as well. Inspect the transaction's account operations and fee record before treating the full difference as an exchange cost.
For an exact-input swap, is the minimum output checked before or after the output transfer fee?
For a supported exact-input swap, Raydium checks the on-chain minimum output against the gross amount the pool sends before the output transfer fee. The quote can still show the expected net receipt after that fee. Input-side and output-side transfer fees can both affect the route's economics.
Will a failed multi-hop swap leave an intermediate token in my wallet?
No, provided the hops are instructions within the same atomic Raydium transaction. If one hop fails or the final output misses its limit, the route does not settle partially. The network fee can still be charged even though the token exchanges revert.
Can a very small swap round down to no usable output?
Yes. Solana programs calculate token amounts in integer smallest units, and each mint defines its decimal precision. Under an extreme price ratio or tiny input, a pool calculation can produce zero usable output. The route may then reject the swap as insufficient rather than crediting a fractional unit.
Should I approve an older wallet prompt after the page displays a new quote?
No. The older prompt represents the earlier transaction message and its encoded limits. Reject it, request a transaction built from the refreshed quote, and inspect the token mints, fixed amount, and applicable slippage limit again. A changed page display does not rewrite a transaction already awaiting signature.