Private mempools are transaction submission systems that bypass the standard public Ethereum mempool — routing transactions directly to block builders or validators to be included in blocks without being visible to searcher bots in the public mempool. The standard Ethereum transaction flow (user → public mempool → all nodes see it → MEV bots can front-run it → block producer includes it) is replaced with a private channel: user submits transaction → directly visible only to selected block builders → included in block without public visibility. Flashbots Protect (RPC endpoint) and MEV Blocker (CoW Protocol) are the leading private mempool solutions — used by forwarding RPC settings in MetaMask or other wallets. Private mempools eliminate sandwich attacks and most frontrunning — bots cannot frontrun transactions they cannot see. Tradeoffs include slight inclusion latency (transaction must wait for a builder who processes private transactions) and trust in the private RPC provider.
How It Works
Standard public mempool (vulnerable):
“`
User → Submit Tx → Public Mempool → All Nodes See → MEV Bot Frontruns → Block Produced
“`
Private mempool (protected):
“`
User → Submit Tx → Private RPC → Block Builder (private) → Block Produced (no frontrun possible)
“`
Leading Private Mempool Solutions
| Service | Provider | Method | MEV redistribution |
|---|---|---|---|
| Flashbots Protect | Flashbots | Route to MEV-Boost builders | No — eliminates frontrunning |
| MEV Blocker | CoW Protocol | Route to searchers who backrun only | Yes — 90% of backrun MEV to user |
| Merkle.io | Merkle | Private builder routing | No |
| 1inch RPC | 1inch | Fusion + private routing | Yes — fills at better rate |
| Beaverbuild Private | Beaverbuild | Direct to builder | No |
MEV Blocker’s Unique Model
MEV Blocker (by CoW Protocol) goes further than preventing frontrunning — it actively redistributes backrunning MEV to users:
- User submits swap via MEV Blocker
- MEV Blocker broadcasts to a set of “backrunners” (searchers allowed to backrun but not frontrun)
- Backrunners compete to backrun the transaction (harmless arbitrage after user trade)
- 90% of backrunning MEV is sent back to the user as gas refund or extra output tokens
Common Misconceptions
“Private mempools guarantee frontrun protection.”
Private mempool solutions dramatically reduce frontrunning but are not absolute. Some block builders may not honor private transaction confidentiality; transactions can leak at various points; builders themselves could extract MEV. MEV Blocker’s model (allowing only backrunning) is more robust than simple private routing.
“Using a private mempool means giving up decentralization.”
Using a private RPC adds a trust dependency on the provider (Flashbots, CoW Protocol) for transaction routing — the user must trust the provider won’t extract MEV themselves. This is a meaningful tradeoff but not a fundamental decentralization compromise, since the on-chain settlement remains fully decentralized.
Criticisms
- Centralization risk: Most private mempool solutions route through Flashbots infrastructure, which controls significant block building market share — creating centralization in transaction ordering even if on-chain settlement is decentralized
- Censorship risk: Private RPCs that route only to compliant (OFAC-compliant) block builders may censor transactions from sanctioned addresses — users routing through private mempools may unknowingly accept censored transaction handling
- Provider trust: MEV Blocker and Flashbots Protect require trusting that the provider isn’t extracting MEV from captured transaction flow — auditing this behavior is limited
Social Media Sentiment
Private mempools receive strong support from DeFi users — anyone who has been sandwiched is immediately receptive. Flashbots Protect and MEV Blocker have high user satisfaction. Concerns about censorship risk are raised by decentralization maximalists. Overall: increasingly adopted as default RPC by sophisticated DeFi users; growing mainstream awareness.
Last updated: 2026-04
Related Terms
Sources
- “Flashbots Protect: How Private Transaction Routing Works” — Flashbots Documentation (2021-2024). Official documentation for Flashbots Protect — the RPC endpoint, how transactions are routed to block builders, confidentiality guarantees, and OFAC compliance status.
- “MEV Blocker: Backrunning-Only Privacy With MEV Redistribution” — CoW Protocol (2023-2024). Technical documentation for MEV Blocker — the protocol design, how it limits searchers to backrunning only, and how 90% of captured backrunning MEV is redistributed to users.
- “Block Builder Centralization and Private Order Flow” — EigenPhi / Blocknative Research (2023). Analysis of how private transaction flow (via private mempools, RPC providers) has concentrated block building power in a small number of builders.
- “SUAVE: Decentralizing MEV and Private Mempools” — Flashbots (2023-2024). Flashbots’ research into a decentralized alternative to centralized private order flow — Single Unifying Auction for Value Expression (SUAVE), a decentralized block builder coordination protocol.
- “Encryption at the Mempool Level: Shutter vs. Flashbots vs. Intent Systems” — Paradigm Research (2023). Comparative analysis of approaches to eliminating malicious MEV — protocol-level encryption (Shutter), private routing (Flashbots), and intent-based architectures (CoW/UniswapX).