MEV-Share Mechanics
How Flashbots' MEV-Share lets users share metadata about their transactions in exchange for a cut of the MEV searchers extract — a structural shift from 'searchers prey on users' to 'searchers and users share value.'
The basics
The MEV Problem
MEV (Maximal Extractable Value) is profit that block producers and searchers extract from transaction reordering: sandwiching swaps, frontrunning arbitrage, capturing liquidations. Historically, all this profit went to searchers and block producers. The user whose swap was sandwiched paid the cost; the searcher who sandwiched them kept the profit. MEV-Share, launched by Flashbots in 2023, changes this: users can opt in to share their transaction metadata with searchers in exchange for a kickback of any MEV the searcher captures.
How It Works in Practice
User submits a transaction through an RPC that routes to MEV-Share (Flashbots Protect is the main one; other order-flow-auction RPCs such as MEV Blocker run their own backrun auctions). The RPC reveals selected hints (e.g., 'someone wants to swap a million USDC for ETH') to searchers, without revealing the full transaction. Searchers bid to capture the resulting MEV; the winning bid commits to paying the user a share of the captured profit. The user's transaction settles; the searcher's bundle executes alongside it; the kickback is delivered.
Why Users Should Care
Two reasons. First, structural MEV protection: if your transaction is going through MEV-Share, it's not in the public mempool, so it can't be sandwiched by adversarial searchers. Second, kickback: you receive a portion of MEV that would otherwise go entirely to searchers. The kickback isn't huge for small trades, but it's structurally yours, where previously you paid for sandwich attacks and got nothing.
- Old model: user signs tx → mempool → searchers extract MEV → user pays the cost
- MEV-Share: user signs tx → private RPC → searchers bid for MEV → user shares the profit
- MEV-Share is reached via Flashbots Protect; order-flow-auction RPCs such as MEV Blocker use a similar backrun-rebate model
- Structural protection + small kickback for normal users
Key Takeaways
- MEV-Share aligns user and searcher incentives via metadata-sharing + kickbacks
- Submit via MEV-Share-enabled RPC instead of the public mempool
- Sandwich-attack protection is structural; kickbacks are small but real
- Flashbots Protect, the main MEV-Share route, supports Ethereum mainnet (and the Sepolia testnet)
Going deeper
Hints and Privacy Levels
When you submit a transaction via MEV-Share, you choose which hints to reveal. Possible hints include: which contract you're calling, the function selector, the logs the transaction will emit, the calldata itself (the transaction hash is the minimum that is shared). More-revealing hints attract more searchers (who can find better MEV opportunities) and produce larger kickbacks. Less-revealing hints maintain more privacy but capture less. The default Flashbots Protect setting shares the transaction hash and partial swap logs (the pool and the fact that a swap was made), enough to enable common backrunning patterns while keeping the rest of the transaction private.
Backrunning vs Sandwiching
MEV-Share's economic model assumes searchers will backrun users — execute their MEV strategy *after* the user's transaction confirms. This captures arbitrage opportunities that emerge from the user's trade (e.g., user buys 1M USDC of ETH, which moves the price; backrunner arbitrages the price difference between the venue the user traded on and other venues). Sandwiching (which executes *both before and after* the user) is structurally prevented because the MEV-Share Node only accepts backruns, and searchers see only the hints the user chose to share. This is the key insight: backrunning is value-neutral to the user (the user got their original execution); sandwiching is adversarial.
Order Flow Auctions
MEV-Share is one example of a broader pattern called Order Flow Auctions (OFAs). Another OFA is MEV Blocker, which runs its own searcher auction for backruns. The common pattern: aggregate user flow → auction it to searchers → distribute kickbacks. Wallets and apps can integrate these RPCs directly, which means even users who haven't explicitly opted into MEV-Share may be getting OFA-style treatment via their wallet's RPC.
MEV Blocker vs Flashbots Protect
Two user-facing options. Flashbots Protect is the main route into MEV-Share: by default it shares the transaction hash and partial swap logs and refunds 90% of MEV to the user, with detailed control over hints. MEV Blocker (formulated by CoW Protocol, Beaver Build and Agnostic Relay, and since acquired by Special Mechanisms Group) is a separate order flow auction that lets searchers bid to backrun and returns up to 90% of the value to users. Both deliver structural sandwich protection; the difference is in marginal rebate economics and configurability. For most users, either works fine; sophisticated users compare backtest results.
Key Takeaways
- Hint level controls privacy/yield tradeoff — more hints = larger kickback, less privacy
- MEV-Share enables backrunning (post-user MEV) but structurally prevents sandwiching
- Order Flow Auctions are the broader category; wallets may route via OFAs by default
- Flashbots Protect and MEV Blocker are two user-facing options
Under the hood
Builder-Side Economics
MEV-Share orders flow through block builders. Block building is concentrated: in a relayscan.io 24-hour snapshot (to 11 October 2026, 01:58 UTC), Titan built about half of MEV-Boost blocks (51%) and Quasar about a quarter (25%). The builder bundles the user's transaction with the winning searcher's backrun and submits the bundle to the proposer via MEV-Boost. Builders that include MEV-Share bundles compete on the same axis as builders that don't — total block value extracted.
Cross-Domain MEV-Share
MEV-Share launched on Ethereum L1, and Flashbots Protect's documented RPCs cover Ethereum mainnet and the Sepolia testnet. Cross-chain MEV — opportunities that span L1 and L2 or between L2s — is a frontier where solver / searcher architectures are evolving. Cross-domain order flow auctions are an active research area.
Encrypted Mempools as Endgame
MEV-Share is a transitional solution. The long-term endgame for MEV mitigation is some form of encrypted mempool where transactions are committed to before contents are revealed. SUAVE (Single Unifying Auction for Value Expression) from Flashbots was one proposed direction; its suave-geth repository was archived (read-only) on 12 May 2025. Ethereum's protocol-level discussion of inclusion lists, proposer-builder separation, and encrypted mempools are all parts of the same broad agenda. MEV-Share is the production-ready 'good enough for now' option while these deeper changes mature.
What MEV-Share Doesn't Protect Against
Not all MEV. Specifically: MEV that doesn't depend on knowing your transaction in advance — generalised arbitrage between venues, time-priority races for fixed opportunities (liquidations, NFT mints with price discovery). And not all attack surface: if your transaction involves multiple steps with intermediate state that's publicly observable (e.g., a long-running flash loan), there are still patterns adversaries can exploit. The protection is specifically against single-transaction sandwiching.
If You Trade Frequently, Set Default RPC to MEV-Share
MetaMask, Rabby, and most wallets support a custom RPC setting. Adding Flashbots Protect or MEV Blocker as your default RPC for Ethereum mainnet means every transaction you send gets that service's MEV protection and rebate treatment automatically. No per-transaction opt-in needed; structural protection on every trade. The kickback over a year of normal trading isn't life-changing but it's free money on transactions you'd send anyway.
Key Takeaways
- MEV-Share orders reach the proposer through block builders, which are themselves concentrated
- MEV-Share is documented for Ethereum mainnet; cross-chain ordering auctions are an active research frontier
- MEV-Share is a transitional solution; encrypted mempools are the long-term direction
- Protection is specifically against sandwiching; other MEV vectors persist
- Set MEV-Share-enabled RPC as default for structural protection on every transaction
Related Content
Related Coins
More Topics
Browse all 189 topicsStealth Addresses and Confidential Transactions
Privacy primitives that hide who's receiving what — from Monero's foundational stealth addresses to Ethereum's ERC-5564 and the legal context post-Tornado-Cash.
CDP Lifecycle
How collateralized debt positions work end-to-end — minting DAI against ETH, paying stability fees, surviving liquidations, and the structural lessons from MakerDAO's Black Thursday and Liquity's no-fee model.
Perpetual Swap Mechanics
How perp futures actually work — funding rates that keep them pegged to spot, mark vs index price, insurance funds that backstop losses, and the liquidation cascades that wreck overleveraged accounts in seconds.
Intent-Based Architectures
Why CoW Swap, UniswapX, Across, and 1inch Fusion moved from 'sign a transaction' to 'sign an intent' — and how solver competition delivers better prices and MEV protection.
Solver Networks
How solver markets shape DEX prices, the competitive structure across CoW Swap, 1inch Fusion, Hashflow, and other venues, and why solver consolidation is a central debate in DeFi market structure.
Liquidation Cascades
The mechanical structure of cascading liquidations — Black Thursday, May 19 2021, August 2024, October 2025 — what amplifies them, who profits, and why over-leverage creates correlated risk across the entire DeFi stack.
Flash Loan Economics
Why flash loans exist, the legitimate uses (arbitrage, collateral swaps, refinancing), and how the same primitive that enables capital-efficient DeFi also enables governance attacks and oracle manipulation.
zkSync Era Architecture
How zkSync Era's prover (Boojum), native account abstraction, and unique EVM-compatibility-via-zkEVM design differ from competing rollups — and what the architectural choices mean for users and developers.
References & further reading
- primary
- secondary
- secondaryrelayscan.io — MEV-Boost relay and builder stats
Top builders, 24h to 11 October 2026 01:58 UTC: Titan 51.03%, Quasar 25.11% of MEV-Boost blocks.
- primaryFlashbots Docs - MEV-Share Introduction
Backrun-only MEV-Share Node, 90% default refund, Flashbots Protect as the entry point.
- primaryMEV Blocker - Documentation
A separate order flow auction with searcher backrun rebates.