You already know what MEV is. Bots, sandwiches, an invisible tax on every swap — you've made the diagnosis. But a diagnosis is made once, and protection requires a specific setting you've either configured or haven't. Open your wallet right now and check which RPC it points to by default. If it's a standard public endpoint, you're still broadcasting every intention into a room full of bots, and everything you know about MEV in theory hasn't saved you a single cent. Let's get into what Flashbots actually is — not as a cautionary tale, but as a lever you can flip in two minutes.

The gas war that wore everyone out

Before 2020, there was no MEV protection at all — there was only the race. Bots would spot someone's profitable pending transaction sitting in the public mempool and launch a priority gas auction: each bot bidding a slightly higher fee than the last to land first in the block. During moments of market panic — a sharp price drop, a cascade of liquidations — this race drove gas prices up for the entire network, because bots were spamming dozens of competing versions of the same transaction, each trying to be first. An ordinary user just wanted to pull their collateral before getting liquidated, and paid absurd fees for it — not because the network was overloaded with real demand, but because it was overloaded with someone else's private war over ordering.

That was the war Flashbots showed up to solve in 2020 — not as a product, but as a research group with a pragmatic idea: if the race is unavoidable, let it happen through a private channel instead of as spam on the public network. That's how the first private relay came to be — a path where a bot could send its bid directly to a miner, bypassing the mempool and bypassing the gas war everyone else was watching.

PBS: who builds the block and who confirms it

After Ethereum's move to Proof-of-Stake, that idea grew into an architecture that, by most estimates, now handles the large majority of the network's blocks — Proposer-Builder Separation (PBS), implemented through the MEV-Boost infrastructure. Here's how the roles break down:

The point of the split is that no single node can both see the contents of other people's trades and decide whether to include them. The validator can't steal the builder's strategy, because it never sees it before signing. The builder can't cheat the validator, because the relay verifies the bid. None of this makes MEV disappear — it's still there — but it moves the war over ordering out of the public space where everyone used to bleed for it.

Flashbots Protect — the lever you already have

Here's the practical part. Flashbots Protect is an RPC endpoint you can point your wallet at instead of the default one. Setting it up takes about two minutes: in MetaMask (or any wallet with configurable networks), you add Flashbots Protect's custom RPC URL in place of the public node — and from that moment your transactions go straight to builders, entirely bypassing the public mempool. A bot that used to sit and watch the queue of pending transactions simply stops seeing you. You're not there anymore.

The service typically offers two modes. Fast prioritizes speed, with a small amount of exposure at the last hop of the route. Protect prioritizes maximum privacy, and comes with a refund mechanism: if your transaction doesn't land in a block — say the market moved and your trade's conditions no longer hold — you're generally not charged gas for the attempt, unlike the public mempool, where a failed transaction still burns your gas regardless. That changes the actual economics of trying: before, "it might not work" cost you money either way; now it only costs you money if it actually works.

MEV-Share — if you won't hide, sell what shows

There's a second, more interesting philosophy of protection. MEV-Share doesn't hide your transaction entirely — it lets you decide how much of it to reveal to a curated set of vetted searchers, and takes a cut of whatever profit they extract from it and routes it back to you. Instead of "nobody sees anything," it's "someone sees a little, and shares the take."

It sounds like a compromise, but it's really a reversal of the usual logic: if extraction is unavoidable at any level of visibility, let it at least partially flow back to you instead of entirely to the predator. Several protocols and aggregators already bake refund mechanisms like this in by default — you can end up with a rebated swap without ever knowing what happened under the hood.

An ecosystem, not one brand

Flashbots isn't the only player, and it's worth not anchoring to a single name. MEV Blocker, built with contributions from CoW Protocol and other teams, works on a similar model: a private RPC plus a searcher auction plus a refund to the user. bloXroute offers its own protected RPC with comparable mechanics. Some wallets — Rabby, for instance — already route a chunk of transactions through protected channels by default, without asking you to pick an RPC at all.

The model has spread beyond Ethereum, too. On Solana, Jito's infrastructure plays a similar role — a block builder and relay with private bundle submission, solving the same problem in the same spirit. It's worth seeing this as an emerging industry pattern rather than one company's product: private submission, builder auction, partial refund back to the user. That's what the industry converged on once it looked honestly at the problem.

Where protection doesn't save you

Be clear-eyed about the boundaries. A private RPC protects you against front-running at the entry point — against your transaction ever being spotted in a queue. It doesn't protect you from MEV extracted after your transaction lands, based on network state your own trade just changed — a liquidation that happens the following block because your trade moved an oracle price, for instance. It doesn't remove trust from the equation either: you're trusting the relay not to peek at contents on someone else's behalf, and that trust is reputational rather than cryptographically guaranteed, even if the protocol's design makes abuse costly and visible. And Protect mode can sometimes mean slower or less certain inclusion during a sharp market move — privacy and speed don't always pull in the same direction.

None of that erases the benefit. It means a private RPC is one lever, not the only one. Tight slippage, trading in deep liquidity, splitting large trades — all of that still matters alongside private routing, not instead of it.

Our record: PBS is a rare case in crypto infrastructure where the answer to "who watches the watchers" isn't "trust us" — it's "we built the system so no single node sees everything and decides everything at once." The builder sees the contents but doesn't decide inclusion. The validator decides inclusion but doesn't see the contents. The relay stands between them as a witness with nothing to gain from the outcome. That's engineering aimed at separating power — the same instinct behind why MAAT is built around a set of Keepers rather than a single keyholder. Not mysticism, not a forced parallel — just the same engineering intuition twice: concentrating visibility and decision-making in one place always breeds Isfet, a parasite sitting in the gap between what's known and what's decided.

The protection already exists, it works, and it costs you two minutes of setup. The difference between someone who pays an invisible tax to bots every single day and someone who's stopped isn't knowledge about MEV. You already have that — you read this far. The difference is whether you actually changed the RPC in your wallet tonight, or filed it under "later," which, as usual, never quite arrives on its own.