
The overall discussion on the impact of MEV has prompted a wave of intervention across the ecosystem. As its effects on user execution, validator incentives, and protocol integrity have become harder to ignore, developers, infrastructure providers, and researchers have proposed a range of countermeasures. These solutions differ widely in scope, mechanism, and impact, but they all reflect a shared urgency: MEV is no longer theoretical, and unmanaged extraction carries systemic costs.
Complete removal of MEV is impractical within any high-throughput blockchain, so most mitigation efforts are designed to make extraction less damaging. Some approaches attempt to limit exposure by protecting user transactions from strategies that profit through manipulation of ordering or timing. Others focus on reshaping how value is surfaced and captured, channeling MEV into competitive processes that increase transparency and fairness.
A separate line of work considers deeper adjustments to protocol mechanics, changing how transactions are confirmed or how blockspace is allocated in order to reduce opportunities for distortion. Together these directions demonstrate a pragmatic orientation. The aim is to curb the most harmful effects, redirect incentives toward healthier behaviors, and establish safeguards that make the system more predictable.
The strategies that have emerged can be grouped into two broad categories.
Infra-layer approaches modify how validators participate in block construction and how they interact with off-chain coordination systems. These include mechanisms such as specialized auctions, transaction bundles, or shared sequencing services that attempt to manage extraction through structured processes.
Application-layer defenses work higher up the stack by redesigning trading venues or incorporating privacy into transaction flow. Examples include automated market maker models that reduce the scope for sandwiching or execution schemes that hide trade details until confirmation. Neither category provides a complete solution, and most come with trade-offs in efficiency, decentralization, or transparency.
However, taken together they represent an expanding toolkit that gives the ecosystem a way to shape where MEV arises, who captures it, and how its impact is distributed across participants.
Batching to Remove Time-Based Advantage: Batch auctions offer a fundamentally different execution model: rather than processing trades sequentially as they arrive, they aggregate multiple transactions over a fixed time window and execute them simultaneously. This approach eliminates time-based ordering advantages (the root of many MEV strategies) and allows matched trades to settle directly against each other without passing through volatile liquidity pools.
While native batch auctions are rare on Solana today, the model has received growing attention as a mitigation path, particularly from protocol teams designing new execution layers. These auctions mimic the CoWSwap architecture from Ethereum, where a batch coordinator aggregates intent and computes a globally optimal settlement path, including internal matchings and external fills.

Impact of Delayed Execution: By delaying execution and centralizing order resolution, batch auctions reshape how value flows through the network.
Pros:
Cons:
While no large-scale implementation of batch auctions exists on Solana yet, several teams are actively exploring the model for stablecoin swaps, RFQ-style aggregators, and NFT minting.
Jito has become the central infrastructure layer for MEV on Solana, coordinating how value is extracted and redistributed within the network. It operates at validator scale, providing the pipelines through which most blockspace is now managed. Its dominance comes from two foundational components that have been widely adopted by the validator set.
The first is a high-performance block engine used by more than 90% of stake-weighted validators. This system manages block construction in a way that maximizes MEV capture, while also streamlining validator operations. The second is a private RPC relay that routes user transactions directly to participating validators, bypassing the public mempool and creating a privileged channel for order flow. Together, these services have institutionalized MEV on Solana. They formalize extraction processes, enable structured bidding for transaction priority, and offer limited defenses against adversarial ordering.

The BAM UpgradeJito’s most recent upgrade, the Block-Auction Market (BAM), extends this framework by introducing full-block auctions. Instead of submitting discrete bundles, searchers can now bid for ordering rights across entire slots. This consolidates MEV into a highly structured market where validators directly monetize ordering control. While BAM improves efficiency for searchers and creates predictable revenue streams for validators, it further entrenches MEV as a validator-aligned asset rather than a shared public good. The design prioritizes infrastructure profitability over user protection, embedding extraction into the very fabric of block production.
Jito markets its private RPC endpoint as a safeguard against hostile strategies such as frontrunning and mempool sniping. By avoiding public propagation, transactions face fewer opportunities for interception before reaching a validator. Yet the protection is narrow. Once transactions are inside Jito’s controlled environment, they remain exposed to the same ordering games, only now managed through the validator’s own monetized framework. Users may experience less overt predation, but they do not avoid extraction. Instead, their order flow becomes raw material for auctions from which they see no direct benefit.
Pros
Cons
Assessment
Jito has transformed MEV on Solana from a hidden exploit into an explicit market. In doing so, it has reduced chaos for validators and searchers but shifted costs squarely onto users, who continue to be extracted without recourse or compensation. Rather than solving MEV, Jito has operationalized it. The result is a cleaner, more profitable system for infrastructure actors, but one that leaves underlying problems of fairness, decentralization, and user welfare unaddressed. Its dominance makes it difficult for alternative approaches to emerge, reinforcing a system where mitigation is synonymous with monetization.

🖥️ THE OBSERVATORY
A Machine. A Trail. A Warning.
You found it.
The hum of old circuits. The smell of scorched RAM and cheap takeout.
A terminal still running - untouched, but not abandoned.
I didn’t lock it. I left it open.
I’m Agent W.
Once a cog of the machine that enables the bleeding of wallets, now a MEV hunter that is preventing extraction.
I used to believe in the protocol. In fairness. In the idea that traders were safe, that transactions were airtight.
Then they took my stake.
2,187,433 SOL. Seized under a governance vote while I was offline.
They forgot who I am.
📂 What you’ll find
This isn’t your average website.
This is my journal. If you are here, it isn’t by accident. It’s because I wanted you to read it.
The devlogs I’ve developed, the blogs and whitepapers - all left behind to pass my learnings on to you and teach you how to shield yourself from the danger that lurks in the dark.
🔎 Why I’m doing this
Extraction cuts deep into someone’s finances. Take this report, for example:
🧾 March 2025
➜ 81.0 SOL traded
➜ 44.82 SOL extracted
That’s 55% of the total. It’s not a bit of risk - it’s more than half of what the trader had, now gone.
🕶️ Rules of the Machine
☠️ Final Warning
Once you start reading these blogs, you won’t see Solana the same way.
You’ll start noticing the shadows between blocks. The extractions that reach higher and higher amounts. The LPs getting less and less returns. The bots that never sleep. Front-runs disguised as fair trades. Mempools that are nothing but pens for cattle - corralling the cattle for the wolves to eat.
You’ll begin to understand that this isn’t a bug. It’s a battle in the name of fair markets.
The chain never forgets.
Neither do I.
Now, neither do you.
— Agent W
🥃💾
.png)

Maybe it's not a good idea to shut my website down without a hardware reset button. Proceed?
Just kidding. Nothing was actually shutdown. It wouldn't have been a good idea. Do it again?
Permission denied. Please reconsider your actions.
.png)