MEV Blocker primary sources — 2026-05-08

Classification takeaway

MEV Blocker is best cataloged as wallet-facing order-flow-auction and private transaction-routing infrastructure, not just as a protective RPC endpoint. Its key mechanism is controlled order-flow exposure: users send transactions into a private routing layer, searchers compete for backrunning rights under explicit auction rules, builders pay for access to that flow, and a large share of resulting value is routed back to users and flow originators.

Primary sources reviewed

1. Official homepage — https://mevblocker.io/

   • Frames MEV Blocker as broad-spectrum protection from frontrunning and sandwich attacks for Ethereum users across DeFi, NFTs, and general dapp activity.
   • Emphasizes that users can add the system directly as a wallet RPC, which is important because it places MEV protection at the transaction-routing layer rather than inside one app.
   • Exposes the multi-endpoint surface (/fast, /noreverts, /fullprivacy, /maxbackruns, /nochecks), showing that the product is really a configurable routing policy layer with speed/privacy/rebate tradeoffs.
   • States that searchers can pay users for backrunning opportunities and names CoW Protocol, Agnostic Relay, and Beaver Build as original maintainers; the page also notes the 2026 acquisition by Special Mechanisms Group.

2. Docs introduction — https://docs.mevblocker.io/

   • Defines MEV Blocker as RPC endpoints that protect against frontrunning and sandwiching while offering rebates from backrunning through an order-flow auction.
   • Highlights the core claims the project wants to win on: speed, rebates, transparency, permissionlessness, and endpoint customization.
   • This is the clearest high-level source for understanding that MEV Blocker is trying to be both protective infrastructure and a user-aligned MEV redistribution layer.

3. How it works — https://docs.mevblocker.io/concepts/how-it-works

   • Contrasts the public mempool with MEV Blocker’s structured private routing path.
   • Says harmful MEV should be diminished while user-beneficial MEV should be maximized, which is a stronger and more precise claim than generic “MEV protection.”
   • Shows that builders and searchers remain in the loop; the project is not eliminating MEV intermediaries so much as constraining and repricing them.

4. Order flow auction docs — https://docs.mevblocker.io/concepts/order-flow-auction

   • Provides the most important mechanism details: builders post bonds and pay dues, searchers bid for backruns, fake transactions can be mixed into shared flow, signatures are removed and later re-attached, and the winning searcher is selected based on user rebate value.
   • This page is what makes MEV Blocker analytically useful: it reveals the system as a rules-based routing market with explicit control over who sees order flow and under what economic conditions.
   • It also clarifies that the project’s private mempool is not simply secrecy; it is selective disclosure plus auction-mediated execution.

5. Gas rebates docs — https://docs.mevblocker.io/concepts/gas-rebates

   • Positions MEV Blocker as a way to recapture value from Ethereum’s PBS-era fee path, especially priority-fee and builder-fee inefficiencies.
   • Useful because it broadens the classification beyond sandwich protection into fee-path intermediation and refund infrastructure.

6. Public web repository — https://github.com/mevblocker/web

   • Confirms that MEV Blocker is a live product surface with public wallet onboarding, endpoint configuration, docs content, and deployable web UX.
   • Supports the view that the RPC is meant for wide retail and integrator adoption, not only research audiences.

7. Acquisition memo — https://www.smg.org/memo/mevblocker

   • Notes that Special Mechanisms Group acquired the MEV Blocker RPC infrastructure in 2026.
   • Relevant as current operator context, though it does not materially change the mechanism classification.

Whitepaper / technical-doc status

• No canonical standalone whitepaper or litepaper surfaced in this pass.
• The strongest primary materials were the homepage, docs introduction, mechanism pages for the order-flow auction and gas rebates, the public web repo, and the acquisition memo.

Why it stays in the active corpus

• Strong comparison class for Shutter and Primev/mev-commit because it addresses pre-settlement power through a different control surface: private routing and auctioned backruns rather than threshold encryption or explicit preconfirmation commitments.
• Useful for reasoning about where authority centralizes when wallets and dapps outsource transaction routing to a user-protective intermediary that still depends on searcher access rules, builder connectivity, and rebate logic.
• Good long-tail addition because it turns “MEV protection RPC” into a more precise mechanism category: order-flow wholesaling with user-aligned refund rules.