sam-robeson

Which Flashbots Tool Fits Transactions, Bundles, or Blocks?

Flashbots has a different entry point for each sender: Protect for normal signed transactions, MEV-Share for orderflow refunds and backruns, the Auction for searcher bundles, and MEV-Boost for validators receiving builder blocks. If you sign wallet transactions, start with Protect; if you operate a validator, start with MEV-Boost. What you send decides which component fits.

Flashbots Is the Project; MEV-Boost Is Validator Software

The name covers a research and infrastructure organization, while MEV-Boost is one open-source program it built for Ethereum validators. They are not two services competing for the same task. Protect accepts a transaction, the Auction accepts a searcher’s bundle, and MEV-Boost helps a validator choose a block assembled by an external builder.

The ethereum.org entry “Maximal extractable value (MEV)” defines MEV as value extracted from block production beyond ordinary rewards and gas fees by including, excluding, or reordering transactions. That definition explains why these roles differ: a transaction sender wants a route into a block, a searcher wants a particular ordering, and a validator chooses which completed block to propose. Flashbots Docs describes separate tools at those points in the process.

Protect Sends a Wallet Transaction Privately

Flashbots Protect RPC fits a person or application sending an ordinary signed Ethereum transaction. The sender uses a private submission route instead of broadcasting the transaction to the public mempool, where other actors could see it before inclusion. If your step is choosing private submission for a wallet transaction, make that RPC selection at flashbots.app and use the selected route when you send it. The transaction still needs a builder that wins the relevant slot to include it.

Protect is the practical starting point for a swap sender who does not construct bundles. Its private route can reduce exposure to public mempool frontrunning, and eligible transactions may receive gas or MEV refunds. Neither a refund nor prompt inclusion is guaranteed: the transaction must create a suitable opportunity, and the route must reach a builder whose block is selected.

Protect also uses MEV-Share underneath when refund hints are enabled. A hint reveals selected information about a private transaction to searchers without handing them the whole signed transaction. The privacy setting therefore affects a real tradeoff: more useful hints can help searchers identify a backrun and fund a refund, while fewer hints reveal less and may produce fewer opportunities.

MEV-Share Connects Orderflow to Backrunners and Refunds

MEV-Share fits senders who want control over what their orderflow reveals and searchers who build backruns from that information. A wallet or application can submit a private transaction through Protect or directly to a MEV-Share Node. The node releases the permitted hints, such as a transaction hash or selected log data, according to the sender’s privacy settings.

A backrunner reacts to that hinted transaction by submitting a partial bundle: a reference to the user transaction plus the searcher’s own transaction intended to follow it. The node simulates the combination and forwards a valid match toward builders with refund conditions attached. That is why the user’s possible refund comes from a searcher’s bid on the opportunity, rather than from merely switching RPCs.

This is also the case where one role may need two components. A searcher already submitting ordinary bundles through the Auction needs the MEV-Share flow as well if the strategy depends on hinted private orderflow. Conversely, a wallet user seeking a possible refund can usually start with Protect and adjust its hint settings; running searcher software would solve a different problem.

The Auction Takes Bundles From Searchers

The Auction fits a searcher who specifies transactions and their order for a block builder. A bundle groups signed transactions for a target block; the builder simulates it and considers whether its payment and execution make it worth including. The searcher sends the bundle through a builder submission API such as eth_sendBundle, rather than sending a normal wallet transaction through Protect.

Consider two operators reacting to the same Ethereum market state and facing the same potential arbitrage. One signs a single transaction to execute their trade; Protect matches that payload. The other prepares multiple signed transactions whose order must be preserved and whose inclusion only makes sense together; the Auction matches that bundle. The opportunity is the same. What each operator sends changes the route and the outcome they can request.

A bundle submission is a bid for inclusion, not a reservation. The builder must accept it, construct a competitive block, and have that block selected. Searchers should therefore distinguish a successful API response from on-chain inclusion, and use simulation and the resulting block to establish whether the intended ordering actually happened.

MEV-Boost Lets Validators Receive Builder Blocks

MEV-Boost fits a validator that wants to compare blocks offered by external builders. It runs alongside the validator’s consensus client and queries configured relays for bids. Builders assemble full blocks from transactions and bundles, then send those blocks to relays. The validator receives a bid and block header, selects an offer, and obtains the full payload through the relay for its proposal.

The Flashbots Relay is one relay a validator can configure. A relay connects builders and validators, checks builder blocks, and carries bids and payloads between them. It is not a destination for a wallet user’s ordinary transaction. This is the key distinction behind the common question “Flashbots or MEV-Boost?”: the organization built tools for several roles, while MEV-Boost serves the validator side of block selection.

A validator should confirm that its consensus client can use MEV-Boost, that its intended relays are configured, and that local block production remains available if external bids or payloads do not arrive. Separate services such as bloXroute and Blocknative occupy related infrastructure roles; their names do not change the test for choosing a component: identify the sender, the payload, and what the sender needs back.

Your Sender Role Determines the First Setup Step

Choose the component by writing down the object your software sends. A signed wallet transaction points to Protect. Hinted orderflow or a backrun built around it points to MEV-Share. An ordered bundle offered to a builder points to the Auction. A validator requesting external block bids points to MEV-Boost and its configured relays.

Then make one test submission appropriate to that role and inspect the result it is meant to produce: a privately included transaction, a matched backrun and possible refund, a bundle included in its intended order, or a validator proposal using a builder block. That check establishes whether the component you selected handles the payload you actually send.