Execution Engines

Pick how each trade lands — by speed, MEV protection, or landing rate. Untaxed adds 0% on every one.

Overview

Every trade routes through Jupiter, and you choose how it's submitted. There are three top-level modes — Jup, Jito, and Helius — and the Jup mode itself offers three routing paths (Beam, Ultra, and Metis), for five execution paths in total. Select the mode from the toggle row above the buy/sell buttons; the Beam / Ultra / Metis sub-tabs appear under Jup. The choice persists across sidebar refreshes.

Jup (Default)

Jupiter routing across every Solana DEX (Raydium, Orca, Meteora, and more) for best price, with three landing paths to choose from:

Beam — default

Jupiter's sub-second landing pipeline with built-in MEV protection. Untaxed assembles the transaction itself for tight control and appends a private address-lookup table so it fits the packet limit on complex routes.

Ultra — fully managed

Jupiter builds, prices, and lands the whole transaction server-side with real-time slippage estimation — you only sign. A priority-fee ceiling protects you from congestion spikes. The lowest-effort option.

Metis — Jupiter V1

Routes via Jupiter's V1 quote and lands through Helius Sender (with an automatic Jito fallback). A reliable alternate path when you want V1 routing.

When to use Jup: Default choice for everyday trading — reliable, sub-second, MEV-safe, and free. Stay on Beam unless you specifically want Jupiter to manage everything (Ultra) or prefer V1 routing (Metis). Switch to Jito for bundled atomic execution, or Helius Sender for the highest landing rate on contested tokens.

Jito Bundles

Your transaction is bundled and sent directly to Jito's block engine, which forwards it to validators. This provides MEV protection — your trade can't be sandwiched by bots.

Jito Settings

Open the gear icon to configure:

When to use Jito: When buying a token that's being actively sniped or when making large trades where a 1-2% sandwich would cost more than the Jito tip.

Helius Sender

The most aggressive execution strategy. Your transaction is sent through two paths simultaneously:

  1. Staked connections (SWQOS) — Direct validator connections via Helius' staked infrastructure.
  2. Jito bundle — Simultaneously submitted to Jito's block engine.

Whichever path lands first wins. This dual-routing gives the highest probability of transaction inclusion.

Helius Sender Settings

Uses the same settings as Jito (slippage, priority fee, tip). The tip is used as the Jito bribe when the Jito path is taken.

When to use Helius Sender: When every millisecond matters — new token launches, time-limited opportunities, or when Solana is congested and you need the highest landing rate.

Engine Comparison

JupJitoHelius
Extra costNoneFee + TipFee + Tip
MEV protectionNoYesPartial
Landing rateGoodGoodBest
USDC supportYesNoNo
Holder requiredNoNoYes