MEV Blocker is an Ethereum transaction-protection RPC service. A wallet can send a signed transaction through one of its endpoints instead of sending it directly to Ethereum’s public mempool. MEV Blocker uses private order flow and an auction between searchers and builders to reduce exposure to harmful frontrunning and sandwich attacks; some endpoints can also return a share of backrun bids to users.
Key Facts
- What it is: an RPC service for submitting Ethereum transactions—not a token, blockchain, or general category of relay tools.
- What it aims to reduce: public-mempool exposure to frontrunning and sandwiching. It does not promise to remove every form of MEV or every transaction risk.
- How rebates work: searchers can bid for eligible backruns. In the documented auction flow, a successful bid is split between a user rebate and builder/validator payments; a transaction may produce no bid and no rebate.
- Endpoint choice matters: the service offers different modes. For example, its “full privacy” endpoint does not offer rebates, while other endpoints trade off inclusion behavior, privacy, and rebate features.
- Supported network: MEV Blocker’s current documentation lists Ethereum for its features; it is not a universal protection setting for every EVM chain or Layer 2.
- Operator: CoW DAO’s January 2026 closing update says MEV Blocker was acquired by Special Mechanisms Group (SMG), a Consensys division.
How It Works
- Choose an RPC endpoint: the wallet sends transactions to the selected MEV Blocker URL. The transaction still needs to be signed by the wallet and ultimately included on Ethereum.
- Keep order flow out of the public mempool: rather than initially broadcasting the transaction to every public mempool observer, MEV Blocker handles it through its configured private transaction flow. What information is shared with searchers and builders depends on the endpoint.
- Run a backrun auction: eligible searchers may compete to submit a backrun bundle. MEV Blocker’s rules prohibit harmful frontrunning and sandwiching in this flow; a winning searcher may still trade after the user’s transaction.
- Send a bundle to builders: the selected transaction and any valid bundle are forwarded for block inclusion. The final transaction is public on-chain after it is included.
- Return eligible value: when a qualifying backrun bid is realized, the documented auction shares value with the user. The current documentation describes a 90% user share for that bid flow, but this is not a guaranteed rebate on every transaction and some endpoints do not provide rebates.
Backrunning is different from a sandwich: it occurs after the user’s trade rather than placing a trade both before and after it. A backrun may capture an arbitrage opportunity created by the user’s transaction. It is not automatically harmful in the same way as a sandwich, but the precise effect depends on the transaction and market.
Endpoint Privacy and Tradeoffs
“Private RPC” does not mean that no service can see transaction data. MEV Blocker’s documentation describes endpoint-specific sharing with permissioned or permissionless searchers and says builders must receive information needed to include transactions. Its full-privacy mode is designed to maximize privacy and does not provide rebates; other modes are designed for faster inclusion, revert handling, or more backrun opportunities. Review the endpoint’s current documentation before choosing it, especially for a sensitive transaction.
Using a private RPC also adds a service dependency: the RPC operator can affect availability, and a transaction that is not included may need to be resubmitted or handled through another route. Network fees still apply. MEV protection does not replace careful slippage settings, reviewing the token and destination contract, or checking what a wallet asks you to sign.
Limits and Risks
- No guaranteed rebate: a transaction may have no profitable backrun opportunity, may use an endpoint without rebates, or may not be included as expected.
- No absolute protection: private routing can reduce common frontrunning and sandwich exposure, but no RPC can promise that all harmful MEV is impossible. Reorganizations, failures, misconfiguration, and endpoint-specific rules matter.
- Privacy has trust boundaries: the RPC provider and the endpoint’s searcher or builder participants may handle transaction information before inclusion. Read how the selected endpoint shares data.
- Execution risk remains: a protected transaction can still have poor price impact, unfavorable slippage, contract risk, or a failed result. Keep normal transaction safeguards in place.
- Network scope: the documented service features are for Ethereum; other chains have different transaction ordering and RPC support.
Social Media Sentiment
A May 2026 r/ethereum discussion about losing value in a mid-cap DEX trade included comments suggesting MEV Blocker or Flashbots Protect as possible private-RPC options. The thread did not establish that the original loss was caused by a sandwich or that either service would have prevented it; commenters also raised slippage and token-specific fees. This is one troubleshooting discussion, not evidence of service-wide performance.
Last updated: 2026-10
Related Terms
- MEV (Maximal Extractable Value) — value that can be gained by influencing transaction inclusion or ordering.
- Sandwich Attack — a frontrun-and-backrun pattern that worsens a user’s trade execution.
- Flashbots — an organization and set of tools involved in Ethereum transaction ordering and MEV infrastructure.
See Also
- What Is MEV — And Why Every Ethereum Transaction Is a Game — a broader explanation of transaction-ordering incentives.
- Why Smart Contract Audits Fail — why security reviews cannot remove all contract and integration risks.
- How Do Crypto Bridges Work — And Why Are They Such a Hack Target? — additional context on the risks of relying on crypto infrastructure and transaction routes.
Use ChangeNOW to compare supported crypto exchange options.
Sources
- MEV Blocker Documentation — identifies the service’s purpose, supported chain, rebate design, and endpoint tradeoffs.
- MEV Blocker: Order Flow Auction — explains how searchers bid on backruns, how order data is shared, and how winning bids are distributed.
- MEV Blocker: Transaction Endpoints — lists current endpoint modes, including the distinction between rebate-enabled and full-privacy choices.
- CoW DAO: MEV Blocker Closing Update — records the January 2026 acquisition by Special Mechanisms Group and the transition away from CoW DAO operation.