
MEV (maximal extractable value) is the profit that can be made by including, excluding or reordering transactions in a block. On swaps, the main harm is the sandwich attack: a bot buys just before your trade and sells just after it, so your swap fills at a worse price. To reduce the risk, send swaps privately (Flashbots Protect, MEV Blocker), use an intent or auction design (CoW Protocol, 1inch Fusion, UniswapX), and keep your slippage tolerance tight.
SwapBee publishes this guide. 1inch, 0x, KyberSwap, LI.FI and Bungee are among SwapBee's providers. Sources were checked on 9 October 2026; the 0x post cited is from 2022.
Ethereum.org defines MEV as "the maximum value that can be extracted from block production in excess of the standard block reward and gas fees by including, excluding, and changing the order of transactions in a block". Much of it is taken by "searchers": independent parties whose bots watch pending transactions and submit profitable ones (ethereum.org).
Not all MEV hurts you. Ethereum.org says DEX arbitrage helps users get correct prices for their tokens. But "some forms of MEV, like sandwich trading, result in an unequivocally worse experience for users. Users who are sandwiched face increased slippage and worse execution on their trades."
The opening comes from the mempool, the public queue of pending transactions. KyberSwap's docs explain that a signed swap sits there, readable by anyone, until it is added to a block, and that Ethereum blocks come about every 12 seconds (KyberSwap docs).
That is how 1inch's Learn page lays it out (1inch Learn), and ethereum.org describes the same pattern: buy "immediately before the large trade", sell "immediately after". 1inch, citing EigenPhi data, counts more than 95,000 sandwich attacks on Ethereum from November 2024 to October 2025.
| Service | Method | What its docs say it does |
|---|---|---|
| Flashbots Protect | Private RPC: transactions go to a private Flashbots mempool | Hides them from frontrunning and sandwich bots |
| MEV Blocker | Private RPC endpoints on Ethereum, with an order flow auction | Endpoints "designed to protect" against frontrunning and sandwiching |
| CoW Protocol | Signed intents, settled in batches by competing solvers; trades of the same token pair in the same direction within a batch receive the same clearing price | MEV protection for every order, including against sandwich attacks |
| 1inch Fusion | Signed order filled by competing resolvers, bundled with other orders | Protects against front-running and sandwich attacks |
| UniswapX | Signed orders filled by competing fillers in an auction | "Protection against MEV" |
| KyberSwap | A maximum slippage you set for each trade | "minimizes any front-running opportunities" |
| 0x Swap API (2022) | "MEV-aware smart order routing" | Targets slippage, which is where MEV losses show up |
The designs fall into two groups.
Private sending. Flashbots Protect sends transactions to a private mempool "where they will be hidden from frontrunning and sandwich bots", and says users aren't charged for failed transactions; it gives its endpoint as rpc.flashbots.net/fast. MEV Blocker says its RPC endpoints are "designed to protect" user transactions from attacks "such as frontrunning and sandwiching", and pays users rebates from backrunning; it says all features are supported on Ethereum.
Intents and auctions. You sign an order stating what you give and the least you will accept, and others compete to fill it. On CoW Protocol, solvers settle batches, and its "uniform directed clearing price" means trades of the same token pair in the same direction within a batch receive the same clearing price; CoW says this stops bots profiting from reordering them. 1inch says Fusion orders are matched with resolvers and bundled with other orders before they reach the chain. UniswapX lists "Protection against MEV" among its features, with fillers competing to settle signed orders.
Some wallets build protection in. Uniswap Wallet lists "Built-in MEV protection", and 1inch Wallet says its swaps are "MEV protected" (Uniswap Wallet, 1inch Wallet).
Slippage tolerance is the most you accept between the quoted price and the execution price. A sandwich works by pushing your fill toward that limit, so a tight limit leaves less room. KyberSwap says a maximum slippage "minimizes any front-running opportunities" because the trade only executes if the final price is within the range you set. 1inch advises keeping slippage tight and notes that on stablecoin pairs, anything beyond a few hundredths of a percent is "free room for a bot".
Too tight has a cost too. SwapBee's slippage tip says low values "may cause transactions to fail if prices move quickly". And trade size matters: in 2022, 0x reported that AMM trades over $100,000 saw more than 20 basis points of slippage on average.
More on price, slippage and execution: best execution in crypto swaps and crypto swap fees explained.
On SwapBee there is no account and no wallet connection: you send your coins to a deposit address. You set a receiving address; most providers also ask for a refund address. After you confirm, you get a Swap ID to track the swap. There are no accounts, balances or pooled wallets: most swaps send your deposit straight to the provider, and on-chain DEX swaps use a one-time swap address SwapBee operates, which executes the swap and sends the output to your wallet automatically. Before you confirm, each quote's provider policy shows who holds your deposit. As of 26 October 2026, that is a one-time address SwapBee operates for LI.FI, 0x, KyberSwap, Bungee and 1inch, and the provider's deposit address for the other 17. The provider may ask for identity or other checks under its own rules. See our AML policy.
Slippage tolerance runs from 0.25% to 5%, with a default of 1%, and applies only to providers that support it. As of 26 October 2026, the providers that support it are LI.FI, 0x, KyberSwap, Bungee, 1inch and Near Intents. 1inch, 0x and KyberSwap publish their own MEV material, quoted above, but we have not documented how a swap routed through SwapBee is sent on-chain, so this post makes no claim either way about MEV protection on SwapBee swaps. If that protection matters for a same-chain Ethereum swap, use a tool whose own docs describe the protection you want.
To compare quotes, and the slippage setting where a provider supports it, open SwapBee.
A bot buys just before your swap and sells just after it, in the same block. Your swap fills at a worse price, and the bot keeps the difference.
It can limit the damage. KyberSwap's docs say a trade executes only within the slippage range you set. A tighter range leaves less room for price movement but can cause a trade to fail.
Both are private RPCs for sending transactions. Flashbots sends them to a private mempool and offers MEV and gas refunds. MEV Blocker says its endpoints are designed to protect against frontrunning and sandwiching, and offers rebates from backrunning through its order flow auction.
CoW Protocol's docs say it offers MEV protection for every order, through solver competition, batch settlement and a "uniform directed clearing price" (the same price for trades in the same direction on a pair within a batch).
No. Ethereum.org says "MEV is also not unique to Ethereum", and 1inch notes that other chains and layer-2 sequencers have their own variants.