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). Exposure depends on
the chain and on the RPC endpoint your wallet sends through. A
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 swap and exit (Slippage & Price Impact §4),
and a private RPC removes most of the exposure.
Integrator note: always pass minOut / minLpAmountOut; near a leg’s coverage wall a larger liability-swap input returns less.
1. Endpoints by chain
Each endpoint is listed in its provider’s docs. 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.
1.1. Ethereum (chain ID 1)
| Provider | RPC URL | Notes |
|---|---|---|
| Flashbots Protect | https://rpc.flashbots.net/fast | Private submission, refunds, no fee on failed transactions; shares the transaction with all registered builders |
| MEV Blocker | https://rpc.mevblocker.io | Private submission with backrun rebates; /fullprivacy pays no rebates |
| BlockRazor | https://eth.blockrazor.xyz | Private routing with backrun rebates; /fullprivacy adds revert protection |
| Blink (formerly Merkle) | https://ethereum.blinklabs.xyz | Private mempool |
| bloXroute Protect | https://eth-protect.rpc.blxrbdn.com | Private relay to proposers |
1.2. Other chains
| Chain | MEV-protected RPC | Notes |
|---|---|---|
| Base and other L2s | None known | A centralized sequencer orders transactions, which limits third-party MEV |
| Chains without a global public mempool | None known | Each validator keeps a local mempool and RPC nodes forward to the next few leaders, so there is no public pool to sandwich from |
“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
- Open the wallet’s network settings (MetaMask: Settings, Networks, Add a network, Add a network manually).
- Enter a name, the RPC URL from the table, the chain ID, the chain’s native currency symbol and a block explorer URL.
- 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.