Not financial advice. This article is for informational purposes only. Leverage, automated orders, and custodial vaults all carry risk of loss.
Most DEX traders still hit “swap” at market and accept whatever slippage and sandwich bots leave them. On-chain order types and private transaction routing can do better, but each has tradeoffs. On Solana, Jupiter’s Trigger V2 supports USD-priced limit orders, take-profit/stop-loss (OCO), OTOCO, and trailing stops. Pending orders are stored off-chain and kept private until execution, and a keeper fills them through Jupiter’s routing. The catch: funds sit in a per-wallet vault (Jupiter’s developer docs call these vault accounts “custodial,” via Privy), and the output amount isn’t guaranteed. On Ethereum, private RPCs such as Flashbots Protect keep swaps out of the public mempool. Here’s how each of these works.
Why market swaps leak value
A pending transaction that bots can see can be front-run or sandwiched. Your slippage tolerance is the most a bot can take from you. On Solana, Jupiter’s older V1 limit orders were stored on-chain, so bots could see pending orders. Trigger V2 moves them off-chain.
Jupiter Trigger V2 (Solana)
- Order types: single trigger orders priced in USD (buy or sell above or below a price), OCO take-profit/stop-loss pairs, OTOCO (an entry order that, once filled, sets up a TP/SL pair), and trailing orders with a trail of 50 to 9,000 basis points.
- Mechanics: orders are private and off-chain until they trigger. A keeper then executes them, and orders can fill partially.
- Limits: $10 minimum order. The output amount isn’t guaranteed, so a fast market can fill you worse than your trigger price.
- Custody: Jupiter’s developer docs describe the deposit vaults as “Vault accounts (custodial) by Privy.” Its user docs describe a program-owned vault with no private key. The two descriptions don’t match, so read Jupiter’s current docs and decide for yourself before depositing size.
- Token-2022 caveat: the developer docs say deposits of tokens with transfer fees or transfer hooks are rejected unless whitelisted. The user docs, however, say Limit V2 supports transfer-fee tokens. Test with a small amount first.
Jupiter routing and transaction landing
Jupiter’s Ultra API is now listed in its docs as no longer actively maintained and superseded by Swap V2. Integrators should plan accordingly. Jupiter says its “Jupiter Beam” engine submits transactions privately and lands them quickly. Those latency and MEV-protection figures come from Jupiter itself, and it acknowledges MEV “cannot be fully eliminated.”
Separately, Jupiter’s Swap API now offers opt-in support for Solana’s new v1 transaction format (SIMD-0385). It allows transactions of up to 4,096 bytes (up from 1,232) with up to 64 accounts inline and no address lookup tables. That leaves more room for multi-hop routes and integrators’ own instructions. Not every wallet can sign v1 transactions yet.
Ethereum: private order flow
- Flashbots Protect RPC (
https://rpc.flashbots.net/fast): transactions are hidden from the public mempool, and reverted transactions aren’t included on-chain, so you don’t pay gas for failed swaps. Transactions with a zero priority fee are dropped. - MEV refunds: through MEV-Share, if a searcher backruns your transaction, you can get a refund. By default, 90% goes to the transaction’s sender (
tx.origin) and 10% to the validator. “Hints” settings let you trade privacy for larger refunds. Sharing fewer details means more privacy but less refund potential. - Uniswap Wallet swap protection routes swaps through Flashbots Protect and is on by default for Ethereum, according to Uniswap’s support article (last updated June 2025).
- Intent-based systems such as UniswapX and CoW Swap are another route. Solvers compete to fill your order instead of you broadcasting a swap.
What faster finality changes
Once Solana’s Alpenglow upgrade activates (scheduled for Oct. 21), Solana is targeting finality of roughly 150 ms, down from about 12.8 seconds. Bots, UIs, and retry logic tuned for the old timing will need adjusting. On Ethereum, the Glamsterdam upgrade’s enshrined proposer-builder separation changes how blocks are built, but it’s too early to say how that will affect MEV and private order flow.
Checklist
- Set slippage deliberately. Don’t leave a wide default.
- Use private submission for larger trades.
- Know who controls the vault holding your pending-order funds.
- Test new order types with small amounts.
- Avoid automated orders on tokens with transfer fees or transfer hooks.
Sources
- Jupiter Developers, Trigger Order API overview, Create Order, Vault & Deposit
- Jupiter user docs, Limit Orders
- Jupiter Developers, Ultra Swap API
- Jupiter Developers, Transaction Versions (v0 and v1)
- Flashbots Docs, Protect quick start, settings guide, MEV refunds
- Uniswap Support, “What is swap protection?”
- Solana Foundation, Alpenglow
Not financial advice. This article is for informational purposes only. Leverage, automated orders, and custodial vaults all carry risk of loss.
