What is Flashbots in Ethereum? MEV and block building explained
Flashbots in Ethereum is a research and development organization that builds tools to change how maximal extractable value (MEV) is extracted and shared. The Flashbots project illustrates this through Flashbots Auction, whose private bundle channel moved bidding for transaction order away from Ethereum’s public transaction pool. It emerged because public MEV competition created gas wars that congested Ethereum and raised costs for ordinary users.
Why did Flashbots arise?
Flashbots arose to address the damage caused when traders competed publicly for profitable places in a block. MEV is value gained by including, excluding, or ordering transactions. A searcher might profit by buying a token on one exchange and selling it on another at a higher price. Another might place trades around a user’s swap, worsening that user’s price. The opportunity comes from where transactions land, not merely from the transactions themselves.
Before private bundle auctions, searchers often raised their gas bids against one another in the public transaction pool. Those priority gas auctions filled network capacity with competing transactions and made ordinary transactions more expensive. Flashbots Auction gave searchers a way to send ordered groups of transactions, called bundles, privately for consideration by block producers. The competition for valuable order still exists, but its bids no longer have to play out as a public gas war.
That history explains the organization’s role. It studies MEV’s effects and builds infrastructure for the people who send transactions, find opportunities, build blocks, and propose them. It does not remove MEV from Ethereum: arbitrage and transaction ordering still create value. Its tools change who can see an opportunity, how participants compete for it, and who may receive the proceeds.
How do the main tools work?
The main Flashbots tools serve different participants in the same path from a pending transaction to a proposed block. A wallet user may care about keeping a swap out of public view. A searcher cares about placing a bundle. A validator cares about the payment offered for a complete block. These names mark distinct jobs:
- Flashbots Auction gives searchers a private channel for bundles and bids for transaction order.
- MEV-Boost lets validators consider blocks built by outside builders instead of relying only on a locally built block.
- Flashbots Relay checks builders’ blocks, holds their contents while bids are considered, and passes a selected block to a validator.
- Flashbots Protect is a wallet RPC route that keeps a submitted transaction out of the public transaction pool before inclusion.
- MEV-Share lets searchers bid to place a transaction after a user’s transaction and returns part of the resulting backrun value to the user when one occurs.
MEV-Boost, released for Ethereum’s 2022 Merge, separates building a block from proposing it. Builders assemble transactions and submit blocks with bids to relays. Relays check the blocks and offer their best valid bids to the validator chosen to propose the next block. MEV-Boost lets that validator compare bids across relays and select the highest one it receives. The validator earns the offered payment while the builder handles the specialized ordering work. The MEV-Boost overview describes this division of work.
Say you submit a token swap through Protect. Your wallet sends it through a private route rather than broadcasting it for every public searcher to inspect. MEV-Share can reveal limited information about the pending swap to searchers, who may bid for a profitable trade immediately after it. If a qualifying backrun lands, part of its value can return to you. The refund depends on the opportunity and the winning bid; a swap need not create one.
What changed when the builder moved to BuilderNet?
BuilderNet changed the organization’s own block building from a single operator’s builder to a shared network run with other operators. In December 2024, its centralized Ethereum builders and their order flow moved into BuilderNet. Multiple operators now participate in producing blocks from shared transaction flow, using open-source builder software. Their candidate blocks still reach validators through MEV-Boost relays. BuilderNet therefore changes who participates in making a block, while the validator’s job of choosing a bid remains familiar.
Shared order flow matters because a builder with exclusive access to valuable transactions can gain an enduring advantage. When operators can work from the same flow, more than one party can contribute to block production. BuilderNet also calculates refunds for participants whose transactions add value to a winning block. For a searcher, that creates a reason to send a useful bundle without giving one private builder exclusive control of it. For a wallet or app, it offers a route for private transactions and potential refunds through Protect.
BuilderNet’s design uses trusted execution environments, or TEEs, to restrict what operators can see and change while handling private order flow. Its current technical overview records a qualification: during a security-model transition, builder nodes are temporarily operating outside TEEs, while routing and backrunning services continue to use them. A TEE is a protection for sensitive computation, not a substitute for checking who operates the network and how its blocks reach validators.
Consider an illustrative searcher who spots an arbitrage opportunity. They want a builder to include their bundle in the intended order without exposing the strategy to every competing bot. A shared builder network can accept that bundle, combine it with other transactions, and bid for the block through relays. If its block wins, the searcher’s outcome depends on the bundle executing as intended and on the value available for a refund. The example shows why private handling, shared access, and bid competition matter together.
What should users and validators watch for?
Users and validators should watch how much transaction information they share and how much power builders and relays accumulate. With MEV-Share, revealing more about a transaction can help searchers find a backrun and raise a possible refund. It also gives them more information before inclusion. For a beginner making a swap, avoiding harmful reordering usually matters more than chasing an uncertain refund. Privacy settings and refund potential are connected through that choice.
Validators face a different trade-off. The highest builder bid can improve a validator’s return, but reliance on a small set of builders or relays concentrates decisions about which transactions reach blocks. Relays can also become points where transactions are delayed or censored. Comparing relay reliability and policies matters alongside bid value; the largest bid alone does not describe the network effect.
SUAVE is the longer-term plan for a shared, decentralized block-building layer. It aims to reduce exclusive control over order flow and let more participants coordinate on block construction. Treat it as a direction for the infrastructure, while judging today’s tools by their current privacy, operator diversity, and relay behavior.
Questions readers ask next
Do I need Flashbots to run an Ethereum validator?
No. An Ethereum validator can propose a locally built block. MEV-Boost is optional software for accessing bids from external builders. It can increase the value offered for a block, but using it adds reliance on relays and builders, so a validator should assess those dependencies.
Is Flashbots Protect free to use?
Yes. Protect does not add a service charge for using its private transaction route. An included Ethereum transaction still pays the gas required by the network. A MEV-Share refund is possible when a qualifying backrun creates value, but it should not be treated as a reduction in the gas you must be ready to pay.