Solana Error 0x1771 (6001): Slippage Tolerance Exceeded Fix
Solana error 0x1771 (decimal 6001) is the standard AMM program error code for "Slippage tolerance exceeded". It is returned by Raydium, Orca, and Jupiter swap routing instructions when the minimum token output amount calculated during transaction creation cannot be satisfied by the current pool reserves at execution time. This occurs during high price volatility or MEV sandwich attacks. Increase slippage tolerance to 1.0%–1.5% and set dynamic priority fees.
# Root Cause & Technical Architecture
In Solana decentralized exchanges (such as Raydium CP-Swap, Concentrated Liquidity, or Orca Whirlpools), the swap instruction takes a parameter `minimum_amount_out`. When the program executes on a validator leader, it computes output tokens based on current pool liquidity. If `actual_amount_out < minimum_amount_out`, the program calls `return Err(SwapError::SlippageExceeded.into())`. In hex, program custom error 6001 serializes as `0x1771`.
# 4-Step Actionable Diagnostic Protocol
Step-by-Step ResolutionIncrease Slippage Tolerance in Swap Interface
In Jupiter or Raydium settings, increase slippage from default 0.3% to 1.0% or 2.0% during volatile market conditions or token launches.
Attach ComputeBudget Priority Fees to Prevent Delays
Add ComputeBudgetProgram.setComputeUnitPrice instructions to ensure transactions land within the next leader slot before price shifts.
Use Jito MEV Bundles to Avoid Sandwiching
Route transactions through Jito tip accounts to guarantee atomic inclusion and protect trades from adversarial arbitrage bots.
Check Token Transfer Fees and Taxes
If trading Solana Token-2022 assets with transfer fee extensions, ensure the slippage tolerance accounts for the mandatory token fee.
# Diagnostic Verification Code / Command
typescript// Jupiter Swap API: Adjusting Slippage Bps & Priority Fees
const quoteResponse = await fetch(
`https://quote-api.jup.ag/v6/quote?inputMint=${inputMint}&outputMint=${outputMint}&amount=${amount}&slippageBps=100` // 100 bps = 1.0%
).then(res => res.json());
// Add Priority Fees to Prevent 0x1771 (6001) Delays:
const { swapTransaction } = await fetch('https://quote-api.jup.ag/v6/swap', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({
quoteResponse,
userPublicKey: wallet.publicKey.toString(),
computeUnitPriceMicroLamports: 50000 // Priority fee to beat slot latency
})
}).then(res => res.json());Launch Derivation Path Inspector
Execute client-side cryptographic simulation and parameter checks safely in your browser via native WebCrypto without sending private keys or mnemonics over the wire.
Read Full Investigation & Recovery Workflow
Explore complete architectural diagrams, edge-case failure trees, and detailed post-mortem analysis in our verified deep guide.
# Related Diagnostic Codes in Solana & Bitcoin
Related Hex StatusesSolana Error 0x1: Insufficient Lamports for Rent Exemption Fix
Fix Solana Custom Program Error 0x1 Insufficient Funds. Troubleshoot missing lamports for account rent exemption, token transfers, and fee payer balances.
Solana Anchor Error 0xbc4 (3012): AccountNotInitialized Fix
Fix Anchor error 0xbc4 (decimal 3012) AccountNotInitialized. Resolve missing Associated Token Accounts (ATA), program state creation, and pre-instructions.
Solana Transaction Expired: Blockheight Exceeded & Priority Fees
Fix Solana Transaction Expired Blockheight Exceeded error. Resolve recentBlockhash expiration, optimize ComputeBudget priority fees, and prevent drops.
# Frequently Asked Questions
FAQ SchemaWhat is decimal 6001 in hex for Solana errors?
Decimal 6001 converts to 0x1771 in hexadecimal. It is the standardized error code for SlippageExceeded across Solana AMMs.
Why do my transactions fail with 0x1771 even with 1% slippage?
If your transaction sits in the validator queue without priority fees, other trades in preceding slots move the pool reserves past your threshold.
Does Solana charge gas fees when a swap fails with 0x1771?
Yes. Validators execute instructions up to the revert point and consume transaction signature and compute fees even on failure.