MEV-Share is shaking up how we extract value from Ethereum transactions. With this protocol, you get access to transaction flows that were previously out of reach, and users finally have some real control over their transaction privacy.
Instead of just passively watching your transaction details leak out, you can decide exactly what to share with searchers, who then compete to get your transaction into a block.
The MEV-Share protocol flips the script on transaction orderflow compared to older MEV extraction models.
Now, you’re working with programmably private transactions, letting users dictate which info gets revealed and when.
This opens the door for new searching strategies and, crucially, ensures users can actually get paid for the MEV their transactions generate.
Key Takeaways
- MEV-Share unlocks new orderflow from users who want to share transaction data on their own terms.
- You can build advanced searching strategies using programmable privacy and selective sharing.
- To tap in, you need to connect to MEV-Share nodes and get comfortable working with limited transaction hints.
What is MEV-Share?
MEV-Share puts you in the driver’s seat, letting you control exactly what transaction details you reveal to searchers. You keep sensitive data private while still giving searchers enough to run strategies like arbitrage and backrunning.
Flashbots runs the MEV-Share Matchmaker, which processes transactions automatically if you’re using Flashbots Protect. Right now, about 3% of Ethereum transactions flow through this system, so there’s a decent pipeline of private orderflow for searchers to tap into.
Key Features:
- Selective privacy: You pick what to share.
- Default protection: Only hashes and pool addresses show by default.
- MEV redistribution: Users can get up to 90% of generated MEV back.
- Protocol compatibility: Works with Uniswap v2/v3, Balancer, and Curve.
How to Use MEV-Share
You get MEV-Share access by connecting to the Flashbots Matchmaker via Flashbots Protect. The process is pretty straightforward and keeps your transaction data safe while still letting you leverage MEV opportunities.
User Process:
- Connect through Flashbots Protect to reach the Matchmaker.
- Configure privacy settings to choose what you share.
- Submit transactions with your preferred privacy.
- Receive MEV redistribution if searchers extract value from your transactions.
By default, the system exposes only your transaction hash and supported pool addresses. The Matchmaker supports pool info for Uniswap v2/v3, Balancer, and Curve. If you want, you can reveal more, but all other data—calldata, logs, etc.—stay private unless you say otherwise.
Searcher Integration:
- Searchers listen for pending transactions via the Matchmaker’s SSE endpoint.
- They build partial bundles using what info they have.
- Bundles go to the relay system with the
mev_sendBundleAPI. - The Matchmaker swaps out transaction hashes for full signed transactions before sending to block builders.
This new paradigm unlocks different orderflow and searching strategies versus the old-school MEV extraction models.
How is MEV-Share Different from MEV-Boost or MEV-Geth?
The main difference? Transaction visibility and how much control users and searchers actually have.
MEV-Share builds on MEV-Boost, but it adds another layer—users and searchers interact directly, not just builders and validators.
Privacy Differences:
| Protocol | Transaction Visibility | User Control |
|---|---|---|
| MEV-Geth | Full transaction data visible | Minimal user protection |
| MEV-Boost | Builder-level privacy | No direct user involvement |
| MEV-Share | Selective data sharing | User-controlled privacy settings |
Here, searchers only see partial info. For example, a Uniswap trade might show just the token pair, but not the amount or direction.
Collaboration Structure:
- MEV-Boost: Connects block builders and validators.
- MEV-Share: Lets searchers and users work together.
You can check out the MEV-Share endpoint to see this limited transaction data in action. It’s a real shift toward user-centric MEV, where you control your privacy and still get a slice of the value.
Enhanced MEV-Share Capabilities#
Execution Requirements Before Block Placement#
You can set specific conditions that must be true before your bundle gets considered for block placement, using pre-inclusion parameters. The inclusion field in your mev_sendBundle request handles this, focusing on lightweight checks that block builders can process quickly.
The main controls are block and maxBlock. You specify these as hex numbers to target a block or a range. No need to spam the system with multiple requests for consecutive blocks.
Example targeting multiple blocks:
{
"inclusion": {
"block": "0x105f27a",
"maxBlock": "0x105f27e"
}
}
This tells builders your bundle is valid in any block from 0x105f27a to 0x105f27e. The system checks these before any heavy bundle simulation, so it’s efficient even with a high volume of submissions.
Validation Rules After Bundle Simulation#
After a block builder puts your bundle in a candidate block, post-simulation validation kicks in via the validity parameter. These checks only happen once the bundle’s position and state are known.
You control rebates and profit splits with two configs:
| Parameter | Purpose | Structure |
|---|---|---|
refund |
Minimum MEV percentages per transaction | bodyIdx + percent pairs |
refundConfig |
Recipient addresses for profits | address + percent allocations |
The refund array lets you set minimum MEV shares for specific transactions. Each entry points to a transaction and the minimum percent required.
Your refundConfig decides where profits go. You can split earnings across multiple addresses, giving you granular control over profit sharing.
These rules guarantee your bundle only lands on-chain if the economic terms are right. Builders have to respect these or skip your bundle entirely.
Composable Bundles and Profit Sharing#
Bundle composition is a big leap for collaborative MEV. When you share transaction data via hints, other searchers can fold your bundle into their own strategies, creating nested bundles.
You set the sharing rules with the privacy parameter and hint types:
calldata– Shows transaction input datacontract_address– Exposes contract addresseslogs– Shares event logsfunction_selector– Reveals function signatureshash– Shares transaction hashes
When you enable hints, you give others a chance to build on your strategy. Maybe someone backruns your arb to catch extra price action, or they combine your bundle with theirs for a bigger win.
Partial bundles shine here. You don’t need a full, standalone strategy—just contribute a piece that others can use. This kind of collaboration often produces more MEV than solo efforts.
Your bundle earns rebates if it gets included in someone else’s composition. The more your bundle helps boost profits, the bigger your rebate.
Targeted Builder Distribution#
You pick which builders get your orderflow using the builders parameter in your privacy settings. This choice affects both how fast your bundle gets executed and your shot at inclusion.
Choosing preferred builders ups your odds of getting into a block, since at least one of your picks might get the slot. If multiple parties make a bundle, only builders that everyone approves get the orderflow.
User preferences vs. searcher preferences:
- Wallet users set builders via Protect RPC URL parameters.
- Searchers use the
buildersfield inmev_sendBundle. - The final builder list is the intersection of everyone’s choices.
This setup lets you optimize for builders who handle your strategies well, avoid unreliable ones, or keep working with trusted operators.
The intersection rule means everyone keeps control over where their orderflow goes. Users decide their routing, and searchers can add their own restrictions.
Builder selection really matters for time-sensitive plays, where speed beats max profit. By narrowing to responsive builders, you boost your chances of hitting your target block.
Searching Strategies
Inside MEV-Share, you’ve got two main ways to find and execute opportunities. Each comes with its own trade-offs between computational efficiency and gas usage.
Direct Chain Analysis
This approach has you do the math inside your smart contracts—not off-chain. Your contracts read the data they need, crunch the numbers, and build transactions right during execution.
You’ll need contracts that:
- Calculate token amounts from reserve changes, not just transaction data.
- Process arbitrage parameters live during block execution.
- Run strategy logic based on the real-time blockchain state.
The simple-blind-arbitrage strategy shows this method in action. You get super accurate intra-block data, but your gas bill will be higher.
Benefits: Real-time accuracy, no stale info.
Drawbacks: More gas, higher execution costs.
Probability-Based Execution
If you’re working with limited info, you can try multiple parallel attempts with different parameters. This lets you cover your bases without burning gas on heavy on-chain computation.
Here’s how it looks:
| Scenario | Action | Result |
|---|---|---|
| Unknown trade direction | Submit two bundles | One reverts, one works |
| Uncertain swap amounts | Try multiple parameter sets | The optimal one goes through |
| Shifting markets | Run parallel strategies | You hedge your risk |
This is especially handy for backrunning on Uniswap or Uniswap V3, where you can ride price moves without needing to frontrun. You save gas and still stay competitive with other searchers watching the mempool.
Probabilistic strategies help block frontrunning by working off limited info, making on-chain exchange interactions smoother for everyday users.
If you want to take these strategies to the next level or integrate them into your DeFi product, Disrupt Digi can help you build, analyze, and optimize your on-chain searcher infrastructure.
Getting Started
Jump right in by connecting to the MEV-Share endpoint at https://mev-share.flashbots.net. Just plug that URL into your browser if you want to poke around before building anything serious.
Development Options:
- Arbitrage Bot Example – Check out the sample arbitrage bot if you want to get your hands dirty fast.
- Matchmaker-ts Library – Flashbots maintains a TypeScript reference implementation; it’s pretty solid.
- Simple-blind-arbitrage – Prefer JavaScript? There are examples for that too.
- Direct RPC Integration – If you don’t want any libraries in your stack, go straight to the endpoint.
MEV-Share runs permissionlessly, so you don’t need to jump through hoops or get anyone’s blessing to participate. This decentralized design opens the door for anyone in the ecosystem to get involved—no gatekeepers.
Privacy isn’t just a buzzword here. You can actually decide which parts of your transaction data to share with searchers, so you keep user privacy intact while still collaborating.
Depending on your stack and language of choice, you’ve got a few integration paths. Right now, most of the tooling is in TypeScript and JavaScript, but client libraries for other languages should roll out soon.
If you want to dig deeper, the detailed connection instructions walk you through the process step by step. And if you’re looking to maximize your edge, Disrupt Digi can help tailor your orderflow strategies for MEV-Share and beyond.
Additional Learning Materials & Tools
If you want to dig deeper into orderflow auctions, just check out the MEV-Share protocol repository. It’s packed with technical docs and specs.
The platform lays out hands-on guides for searchers getting started with MEV-Share nodes and bundle submission flows. Honestly, if you’re building, you’ll want to bookmark these.
Development Resources:
- Client libraries for spinning up custom bots
- Example arbitrage codebases that actually work
- Protocol specs and design docs for those who want to go deep
- Beta environments where you can test strategies against live orderflow
The searching strategies guide covers some pretty wild new approaches for extracting maximal extractable value on Ethereum. You’ll come across concepts like inclusion predicates and bundle composition—these let you fine-tune execution guarantees in ways that weren’t possible before.
Community Engagement:
Your feedback genuinely shapes how MEV redistribution mechanisms evolve. Developers jump into lively debates and troubleshooting sessions on forums and Discord; it’s where the real alpha leaks.
Privacy Considerations:
Take a look at differential privacy aggregate hints—this research zeroes in on balancing info sharing with the need to block frontrunning. These mechanisms offer a layer of protection for private transactions without sacrificing overall market efficiency.
The MEV redistribution solution analysis walks through real on-chain examples. You’ll see how Flashbots Protect and similar tools actually put value back in users’ pockets instead of letting extractors walk away with it all.
If you’re looking to build, optimize, or just stay ahead, Disrupt Digi’s services can help you navigate these protocols and strategies more efficiently. Don’t hesitate to reach out if you want to go from theory to practice.