MEV-Protected Execution: How FoxD Lands Your Trades Without Getting Sandwiched

You found the token early. You clicked buy before the crowd. And you still got a terrible fill — because a sandwich bot saw your transaction in the public mempool, bought in front of you, and sold into your slippage. MEV extraction quietly taxes retail traders billions per year. FoxD’s execution layer is engineered, chain by chain, to keep your orders out of that game.

The Threat Model

On most chains, a pending transaction is public before it confirms. Searcher bots scan this “mempool” for profitable victims: your buy of an illiquid token is an invitation to front-run (buy before you, raising your price) and back-run (sell after you, into the pump you paid for). The defense is architectural — never let your order be visible and orderable by adversaries.

Ethereum & BNB Chain: Private Builder Bundles

On Ethereum and BNB Chain, FoxD submits trades as private bundles directly to block builders, bypassing the public mempool entirely. A bundle either lands intact in a block or not at all — there is no window where a sandwich bot can see and reorder your swap. The landing incentive (bribe) goes to the builder as part of the bundle, tuned to your chosen priority level.

Base, Arbitrum & HyperEVM: Atomic Smart-Account Bundles

L2 sequencers process transactions first-come-first-served, which changes the threat model — but multi-step trades (approve, then swap) still leave gaps. FoxD uses EIP-7702 smart-account bundles: your trading wallet temporarily delegates to an audited on-chain executor so that approval and swap land atomically in a single transaction. One transaction means one fee, no approval race, and no half-completed state if anything reverts.

Solana: Priority Fees + Multi-Path Broadcast

Solana has no public mempool in the EVM sense — landing fast is about compute-unit pricing and propagation. FoxD attaches tuned priority fees and broadcasts each transaction simultaneously across multiple RPC paths, taking the fastest confirmation. During congestion this multi-path redundancy is the difference between landing in the next slot and watching your transaction expire.

Priority Tips: Speed You Control, Capped

Every trade carries a speed setting. The tip buys priority — builder bribes on L1s, sequencer priority on L2s, compute pricing on Solana. Two guarantees hold everywhere:

• Hard cap: tips never exceed 10% of trade value, on any chain, at any setting. A fast landing can’t silently eat your position.
• What you see is what you pay: the fee line on the trade panel is the actual charge — no hidden spread, no inflated “network fee.”

Slippage: Enforced On-Chain, Not Suggested

Your slippage tolerance is compiled into the transaction as a minimum-output amount. If the pool moves beyond it between quote and execution, the transaction reverts instead of filling badly. Combined with private submission, this closes the classic sandwich payoff: the attacker can’t see your order, and even a lucky collision can’t push your fill past the bound you set.

Failure Handling: Fast and Honest

Execution engineering includes the unhappy paths. FoxD fails fast: insufficient balance is rejected instantly (before anything is signed), quotes that can’t meet your slippage never leave the building, and the buy button reports the precise reason — no eternal “pending” spinner while your funds sit in limbo. On success, the receipt shows your measured end-to-end execution time.

Why This Matters More on Small Caps

MEV damage scales inversely with liquidity. On a deep ETH/USDC pool, a sandwich costs you basis points; on a $20k-liquidity fresh launch — exactly what snipers trade — an unprotected buy can be extracted for 10%+ instantly. Execution protection isn’t a premium feature for whales; it is the baseline requirement for the launch trading FoxD is built around.