---
title: "MEV Protection"
seo_title: "MEV-Protected RPCs for Swaps"
description: "When a swap is exposed to front-running and sandwiching, which MEV-protected RPC endpoints exist per chain, and how to add one to a wallet."
audience: user
type: guide
status: live
lang: en
updated: "2026-10-01"
publish: true
---
# MEV Protection

On a chain with a public mempool, a pending swap is visible before it lands, and searchers can
front-run or sandwich it ([MEV](/docs/glossary#mev-maximal-extractable-value)). Exposure depends on
the chain and on the RPC endpoint your wallet sends through. A
[MEV-protected RPC](/docs/glossary#mev-protected-rpc) hands the transaction to block builders
privately instead of gossiping it. BTR does not hide transactions itself: `minAmountOut` and
`deadline` bound the damage on every route ([Slippage & Price Impact §4](/docs/1-1-5-slippage-price-impact#4-protections)),
and a private RPC removes most of the exposure.

---

## 1. Endpoints by chain

Each endpoint is listed in its provider's docs and answered a live `eth_chainId` call on 2026-10-01.
Providers change terms and endpoints; confirm on the linked page before you route value through one. The list is not an endorsement. Which chains
BTR runs on: [deployed instances](/docs/2-1-contract-addresses).

### 1.1. Ethereum (chain ID 1)

| Provider | RPC URL | Notes |
|---|---|---|
| [Flashbots Protect](https://docs.flashbots.net/flashbots-protect/quick-start) | `https://rpc.flashbots.net/fast` | Private submission, refunds, no fee on failed transactions; shares the transaction with all registered builders |
| [MEV Blocker](https://docs.mevblocker.io/reference/api/transaction-endpoints) | `https://rpc.mevblocker.io` | Private submission with backrun rebates; `/fullprivacy` pays no rebates |
| [BlockRazor](https://docs.blockrazor.io/transaction-submission/rpc/ethereum) | `https://eth.blockrazor.xyz` | Private routing with backrun rebates; `/fullprivacy` adds revert protection |
| [Blink](https://docs.blinklabs.xyz/blink/get-started/integration/individual-users) (formerly Merkle) | `https://ethereum.blinklabs.xyz` | Private mempool |
| [bloXroute Protect](https://docs.bloxroute.com/core-solutions/rpc-service/protect-rpc) | `https://eth-protect.rpc.blxrbdn.com` | Private relay to proposers |

### 1.2. BNB Chain (chain ID 56)

| Provider | RPC URL | Notes |
|---|---|---|
| [48 Club Privacy RPC](https://docs.48.club/privacy-rpc) | `https://rpc.48.club` | Private mempool; 48 Club is a major builder on the chain, so inclusion is fast |
| [BlockRazor](https://docs.blockrazor.io/transaction-submission/rpc/bsc) | `https://bsc.blockrazor.xyz` | Private routing with backrun rebates; `/fullprivacy` adds revert protection |
| [bloXroute Protect](https://docs.bloxroute.com/core-solutions/rpc-service/protect-rpc) | `https://bsc.rpc.blxrbdn.com` | Private relay to proposers |
| [PancakeSwap MEV Guard](https://docs.pancakeswap.finance/trading-tools/pancakeswap-mev-guard) | `https://bscrpc.pancakeswap.finance` | Free; routes through bloXroute |

BNB Chain keeps its own list of free and premium privacy RPCs in the
[BNB Chain docs](https://docs.bnbchain.org/bnb-smart-chain/validator/mev/user-guide/).

### 1.3. Other chains

| Chain | MEV-protected RPC | Notes |
|---|---|---|
| Base and other L2s | None known | A sequencer orders transactions ([Slippage & Price Impact §5.2](/docs/1-1-5-slippage-price-impact#52-arbitrum-and-op-stack)) |
| Monad | None known | No global public mempool: each validator keeps a local one and RPC nodes forward to the next few leaders ([Monad docs](https://docs.monad.xyz/monad-arch/consensus/local-mempool)) |
| Arc | None known | |
| Avalanche C-Chain | None known | |
| X Layer | None known | |

"None known" means no wallet-addable private endpoint appears in the chain's or the providers'
official docs. It does not imply protection from reordering.

---

## 2. Add one to a wallet

1. Open the wallet's network settings (MetaMask: Settings, Networks, Add a network, Add a network manually).
2. Enter a name, the RPC URL from the table, the chain ID, the chain's native currency symbol and a block explorer URL.
3. Save, switch to the new network and swap as usual. Keep the original network entry as a fallback.

Some wallets cannot add a network with one click; enter the fields by hand. A private RPC can be
slower to include a transaction, and it can drop one that would fail. You are trusting the
provider's builders and relays, so prefer one from the table over an unknown URL.