dex-execution

DEX Execution — Solana Swap Execution via Jupiter

Execute token swaps on Solana through Jupiter, the dominant DEX aggregator routing across Raydium, Orca, Meteora, Phoenix, Lifinity, and 20+ other venues.

Overview

Jupiter aggregates liquidity across all major Solana DEXes to find optimal swap routes. A single swap may split across multiple pools and hop through intermediate tokens to minimize price impact. The Jupiter v6 API handles route discovery, transaction building, and fee optimization — your code handles quoting, user confirmation, signing, and submission.

Base URL: https://quote-api.jup.ag/v6

Execution Pipeline

Every swap follows this seven-step pipeline. Never skip steps 2-3 (display and confirm).

Step 1 — Get Quote

import httpx
 
params = {
    "inputMint": "So11111111111111111111111111111111111111112",   # SOL
    "outputMint": 

Step 2 — Display Quote to User

Always show these fields before proceeding:

Step 3 — Require User Confirmation

NEVER proceed without explicit "yes" from the user.

Step 4 — Build Transaction

Step 5 — Sign Transaction

Step 6 — Submit Transaction

Step 7 — Confirm Transaction

Jupiter API v6 Endpoints

See references/jupiter_api.md for full parameter and response documentation.

Key Parameters

Slippage (slippageBps)

Dynamic Slippage

Set dynamicSlippage: true in the swap request to let Jupiter auto-adjust slippage based on current market conditions. Preferred for most use cases.

Priority Fees (prioritizationFeeLamports)

Priority fees determine transaction ordering within a block.

Use "auto" for most cases. For fine-grained control, query Helius getPriorityFeeEstimate.

Other Parameters

• onlyDirectRoutes: Skip multi-hop routing. Faster but may get worse price.
• asLegacyTransaction: Use legacy format instead of versioned transactions. Required for some older wallets.
• maxAccounts: Limit accounts in transaction (default 64). Lower values reduce route options but improve confirmation reliability.
• platformFeeBps: Integrator fee in basis points. Taken from output amount.
• wrapAndUnwrapSol: Auto wrap/unwrap SOL ↔ wSOL (default true).
• dynamicComputeUnitLimit: Auto-set compute budget based on simulation.

Priority Fee Estimation

Transaction Confirmation Strategy

See references/transaction_lifecycle.md for the full Solana transaction lifecycle.

1. Submit with skipPreflight: False to catch obvious errors
2. Poll getSignatureStatuses every 2 seconds for up to 60 seconds
3. If not confirmed: rebuild transaction with fresh blockhash and retry (max 3 attempts)
4. Blockhash expiry: transactions expire ~60 seconds after blockhash was fetched
5. Final check: verify token balance changed as expected

Error Handling

Safety Requirements

These are non-negotiable requirements for any execution code.

1. ALWAYS show quote details (amounts, price impact, route) before execution
2. ALWAYS require explicit user confirmation — never auto-execute
3. Default to simulation mode — do not sign or submit unless explicitly enabled
4. Never store or log private keys — load from env vars, use immediately, discard
5. Never use 100% slippage — this is a common scam/exploit vector
6. Verify token addresses — confirm mints match expected tokens before swapping
7. Check price impact — warn if >2%, block if >10% unless user overrides
8. Maintain SOL reserve — keep 0.05 SOL minimum for rent and future fees

See references/safety_checklist.md for the complete pre/during/post execution checklist.

Integration with Other Skills

Files

References

• references/jupiter_api.md — Complete Jupiter v6 API parameter and response reference
• references/transaction_lifecycle.md — Solana transaction lifecycle, priority fees, retry strategies
• references/safety_checklist.md — Pre/during/post execution verification checklist

Scripts

• scripts/get_quote.py — Fetch and display Jupiter swap quotes with route analysis
• scripts/simulate_swap.py — Build and simulate swap transactions without submitting