Raydium
Raydium Fees Across Quotes, Routes, and Settlement
The total cost of a Raydium swap combines pool charges with Solana transaction fees and, in some cases, Token-2022 transfer fees or token-account funding. The total depends on the selected route, current quote, fee payer, destination-account state, and token rules, so a useful comparison keeps those inputs aligned through authorization.
Like-for-Like Swap Cost Comparison
A like-for-like comparison starts with the same input mint, output mint, input amount, and slippage setting. It must also distinguish the quoted output from costs paid separately in SOL. Otherwise, account creation or a different priority fee can blur the distinction between the exchange result and the separate SOL outlay.
Route structure can change the exchange-side deduction. A direct route uses one pool, while a routed exchange can cross several pools. Each pool execution can apply its configured trading fee, so the total exchange-side deduction depends on the complete route rather than the first pool alone. Changing reserves can also make a quoted output stale before either route is signed.
Price impact is an exchange-rate effect, not a payment sent to a separate Raydium account. It describes how the requested exchange changes the obtainable rate relative to the pool state. Keep it separate from the pool fee, network fee, and any token transfer fee when reconciling total cost.
Swap Cost Components and Allocations
The table separates exchange, network, token, and account effects around an ordinary swap. Allocation rows describe parts of a pool fee, not extra charges. Live values come from different sources, so no single displayed percentage represents the entire transaction.
| Component Or Allocation | Value Or Rule | Required Context |
|---|---|---|
| Pool trading fee | The rate configured for each pool used by the route | The current quote route and active pool configuration |
| Liquidity-provider share | A portion of the pool trading fee under the pool’s rules | The applicable pool program and fee allocation |
| Protocol share | A portion of the same pool trading fee under current program rules | The applicable pool program and fee allocation |
| Solana base transaction fee | Calculated from the transaction message under current network rules | The required signatures and transaction message |
| Priority fee | Derived from the requested compute-unit limit and selected compute-unit price | The transaction’s compute-budget instructions |
| Token-account rent deposit | SOL funding supplied when a new token account is created | Whether the required account already exists and who pays |
| Token-2022 transfer fee | The active mint configuration applied to a qualifying transfer | The mint, transfer direction, and active epoch configuration |
Exchange-Side Amounts
Exchange-side accounting tracks how much input reaches each pool and how much output reaches the recipient. Pool trading fees and any applicable token-level transfer fee affect those amounts, while price impact changes the obtainable exchange rate. The expected output is an estimate, while the quote’s slippage threshold determines whether the transaction can proceed.
Wallet-Side Amounts
Wallet-side amounts are paid in SOL by the transaction fee payer. They include the network fee, any selected priority fee, and account-creation funding when needed. A rent deposit should remain separate in the comparison because it can be recoverable, unlike a processed transaction fee.
Which Costs Belong to the Quote?
A Raydium quote defines the exchange-side comparison through its route, expected output, pool-fee information, price impact, and slippage threshold. It is a state-dependent estimate rather than a reservation. Pool reserves, route availability, or token settings can change before authorization, making a refreshed quote materially different.
An unsigned quote cannot move tokens or charge the wallet. Letting it expire, rejecting the wallet request, or requesting another quote therefore preserves the pre-commitment boundary. Once a signed transaction is submitted and processed, network costs can apply even if an instruction later fails.
Pool Fee Allocation Versus Extra Charges
Pool-fee allocation describes where the pool’s trading fee goes; it doesn’t create another surcharge for each named share. Liquidity-provider, protocol, treasury, or fund portions are allocations within the configured trading fee. An enabled CPMM creator fee is different: it is an independent, optional pool charge. Compare the complete pool deduction once, then examine its allocation only when understanding pool economics matters. Adding those portions again would double-count the exchange charge.
Solana Fees and Fee-Payer Capacity
Solana charges the transaction fee payer in SOL. The required amount depends on the constructed transaction and current fee rules, not merely the number of input tokens being exchanged. Two equal-size swaps can therefore have different network costs when their routes, signature requirements, compute budgets, or account instructions differ.
The base fee shouldn’t be treated as an evergreen fixed lamport amount. Estimate it for the current transaction message or read it from the wallet preview. A priority fee, when present, is separate from the pool fee and doesn’t improve the quoted token amount; it changes the fee offered for transaction processing.
If the fee payer lacks enough SOL for the network charge or required account funding, the transaction can’t complete as built. A sufficient input-token balance doesn’t make up the difference. Add enough SOL or stop before signing, then compare a rebuilt transaction because its blockhash, quote, and fee estimate may differ.
Token Accounts and Recoverable Rent
A token-account rent deposit appears when the transaction must create a receiving or intermediate token account. It is SOL placed into the account to satisfy Solana’s account-funding requirement, not a Raydium trading fee. An existing compatible account can remove that creation step from an otherwise similar route.
Recovery generally requires closing an eligible token account after its token balance is zero and using the proper closing authority. The remaining lamports then return to the designated recipient. Account extensions or nonzero balances can prevent closure, so the original deposit shouldn’t be counted as immediately recoverable cash.
Token-2022 Transfer Fees at Epoch Boundaries
A Token-2022 mint can impose a transfer fee independently of Raydium’s pool fee. The extension can affect the amount entering a pool, leaving it, or reaching the destination, depending on the transfers the route performs. The mint’s configuration, rather than the token ticker, determines whether this charge applies.
A Token-2022 transfer-fee configuration can activate a newer fee schedule at a specified epoch. A quote prepared before that boundary may no longer describe the same token-level deduction afterward. Refresh the quote and transaction, then inspect the active mint settings instead of carrying an earlier percentage into the comparison.
Reversible Comparison Before Authorization
A route comparison remains reversible while the wallet request is unsigned. Keep the token identities and input amount constant, and reject any transaction whose total cost or minimum output is unacceptable.
Pre-Commitment Comparison
The pre-commitment record should retain the input and output mints, input amount, expected output, slippage threshold, route, pool fees, price impact, network estimate, and account-creation status. A comparison loses meaning if one candidate uses a different slippage tolerance or destination-account state.
Current Quote and Matching Transaction
A current quote should match the transaction’s mints, route, minimum output, and wallet instructions. Authorization is appropriate only after the fee payer can cover SOL costs and the receiving account state matches the preview. Signing authorizes the reviewed proposal for on-chain submission.
Quote Changes Before Signature
A change in pool state, route availability, or an epoch-dependent token setting can make a quote stale before signature. The old proposal remains uncommitted if it wasn’t signed. Discard it, request a fresh quote, and restart the comparison with the same input and output mints rather than assuming the earlier result still applies.
At the wallet prompt, either sign one currently acceptable transaction or leave without authorizing either route; the choice remains reversible while every wallet request is unsigned.
Pool Creation Costs Outside an Ordinary Swap
Pool-creation charges belong to creating and initializing a pool, not to an ordinary swap through an existing route. They shouldn’t be inserted into a swap-cost comparison unless the transaction actually contains pool-creation instructions. The same separation applies to liquidity-position deposits: their account and position costs don’t become swap fees merely because both actions use Raydium.
What Evidence Settles the Final Cost?
The confirmed transaction record settles the final cost by showing whether execution succeeded, what network fee was charged, and how the relevant balances changed. Reconcile the fee payer’s SOL balance separately from input and output token balances. This prevents a rent deposit or unrelated SOL movement from being mistaken for the pool fee.
The exchange result should be checked against the signed transaction’s minimum-output boundary, not an earlier quote left open on screen. Pool trading fees are normally reflected within the exchange amounts, while price impact has no separate recipient account. Token-2022 withheld amounts require token-account and mint context because a simple recipient-balance check may not explain the entire transfer.
A failed processed transaction can still consume a network fee without completing the swap. An expired unsigned quote cannot. If submission status is unclear, inspect the transaction signature before retrying; a newly built, signed, and successfully submitted replacement could execute a second exchange if the original also succeeded. The reconciled record, not the preview, is the final cost evidence.
Raydium fees: questions and answers
Are liquidity-provider and Protocol Shares Extra Charges on a Raydium Swap?
No. Liquidity-provider, protocol, treasury, or fund shares describe where a pool’s trading-fee bucket goes; they aren’t normally separate additions to that same bucket. A CPMM creator fee is different because it can be an independent, optional charge when enabled for the pool. The complete route quote should expose the pool-level amounts used.
Can a Token-2022 Transfer Fee Change at an Epoch Boundary?
Yes. A Token-2022 transfer-fee configuration authority can schedule a newer transfer-fee configuration for an epoch boundary, subject to the token program’s rules. A long-lived quote may therefore contain older assumptions. A maximum-fee cap limits the amount withheld per transfer, but it doesn’t permanently freeze the rate.
When Can a token-account Rent Deposit Be Recovered?
A rent deposit can generally be reclaimed when the token account is eligible to close, contains no tokens, and the close instruction returns its lamports to the designated destination. Until then, the deposit remains locked in the account. It isn’t a Raydium pool fee or payment for the swap.
Why Did an Unsigned Raydium Quote Expire Without Charging My Wallet?
An unsigned quote can expire because pool reserves, routing data, fee parameters, or transaction context changed. Without wallet authorization and submission, no transaction reached Solana, so no network or pool fee was charged. Request a fresh quote and compare its net output and SOL debit instead of treating the old terms as reserved.
Is Price Impact Paid to a Separate Raydium Account?
No. Price impact is the change in execution price caused by trade size relative to available liquidity along the route. It affects the output the pool curve can quote, but it isn’t a separate transfer to a fee recipient. Pool charges are distinct deductions, so the fee rate alone doesn’t describe the whole economic cost.
What Changes If the Transaction Fee Payer Runs Out of SOL?
The transaction can’t cover its required network charges and may fail before the swap executes. The quoted token output doesn’t automatically fund the fee payer. The fee payer needs enough SOL for the base fee, any selected priority fee, and conditional token-account creation when the transaction requires it.
Do equal-size Raydium Swaps Always Have the Same Solana Base Fee?
No. Solana’s base fee depends on the number of chargeable signatures rather than the swap’s token amount. Equal-size swaps can have different base fees when their transaction messages require different signature counts. Their optional priority fees can also differ because compute limits and compute-unit prices are separate inputs.
Are Raydium Pool Creation Fees Included in an Ordinary Swap?
No. A pool creation fee belongs to the action of creating a supported Raydium pool, not to an ordinary swap through an existing pool. Don’t add it to a swap-cost comparison unless the transaction actually contains pool-creation instructions, which have a different purpose and authorization scope.