Flashbots

What Is Flashbots?

Flashbots is a cryptocurrency research and development organization that builds open-source infrastructure for managing Maximal Extractable Value, commonly known as MEV.

Its work initially focused on Ethereum, where transaction ordering can create additional profits for traders, block builders, validators, and other participants involved in producing blocks.

Flashbots aims to make the MEV market more transparent, competitive, accessible, and less harmful to blockchain users.

It develops tools that allow transactions and transaction bundles to reach block builders privately instead of being exposed immediately in the public transaction pool.

It also develops infrastructure that separates block construction from block proposal, allowing specialized builders to compete to create valuable blocks for validators.

Flashbots is not a cryptocurrency, token, blockchain, wallet, decentralized application, or crypto trading platform.

It is an organization and collection of protocols, software tools, application programming interfaces, research projects, and blockchain infrastructure.

The official Flashbots website describes the organization as working to reduce the negative externalities created by MEV on stateful blockchains.

Its major projects include MEV-Boost, Flashbots Protect, MEV-Share, BuilderNet, block-building software, relay infrastructure, and research connected with SUAVE.

What Is Maximal Extractable Value?

Maximal Extractable Value is the additional value that can be obtained by changing which transactions enter a block and the order in which those transactions execute.

This value is separate from ordinary block rewards and standard transaction fees.

A miner, validator, block builder, or specialized searcher may identify a profitable sequence of transactions and attempt to place that sequence into a block.

For example, two onchain markets may temporarily display different prices for the same crypto asset.

A trader can buy the asset from the cheaper market and sell it through the more expensive market, earning an arbitrage profit while helping the prices move closer together.

A lending protocol may also offer a reward to anyone who repays an unsafe loan and liquidates its collateral.

A searcher can detect the undercollateralized position and submit a transaction that performs the liquidation.

Other forms of MEV can harm ordinary users.

A sandwich attack occurs when an attacker places one transaction before a user’s swap and another transaction after it to profit from the price movement caused by the user.

Frontrunning occurs when someone observes a pending transaction and submits another transaction designed to execute first.

Backrunning occurs when a transaction is deliberately positioned immediately after another transaction to capture an opportunity created by the earlier action.

The official Ethereum explanation of MEV describes how transaction inclusion, exclusion, and ordering can create value beyond normal protocol rewards.

Why Was Flashbots Created?

Before private MEV infrastructure became widely available, sophisticated searchers competed by broadcasting transactions into Ethereum’s public transaction pool with increasingly high fees.

This competition could create failed transactions, wasted block space, unpredictable gas costs, and unstable network conditions.

Several bots might identify the same opportunity and repeatedly increase their transaction fees in an attempt to execute first.

Only one transaction could capture the opportunity, while the other transactions might fail and still consume gas if they were included.

This activity was sometimes described as a priority gas auction because participants competed through higher transaction fees.

Flashbots created a private communication channel that allowed searchers to submit ordered groups of transactions directly to block producers instead of exposing every strategy through the public mempool.

The infrastructure made it possible to bid for block inclusion more directly and to simulate bundles before placing them onchain.

Flashbots later expanded its work to address proposer-builder separation, user protection, MEV redistribution, private order flow, and decentralization of block building.

Does Flashbots Eliminate MEV?

Flashbots does not eliminate MEV because MEV is created by blockchain transaction ordering, market design, liquidation rules, price differences, and demand for limited block space.

Some MEV activities perform useful economic functions, including price arbitrage and the liquidation of unsafe loans.

Other activities transfer value away from users, create unnecessary congestion, or provide advantages to participants with better information and faster infrastructure.

Flashbots attempts to reduce the harmful effects of MEV while making extraction and redistribution more transparent.

Its tools can move transactions away from the public mempool, organize competitive auctions, return some MEV to users, and broaden participation in block construction.

No private transaction system can guarantee that every user will receive the best possible execution or avoid every form of MEV.

How Flashbots Fits Into Ethereum Block Production

Ethereum separates the work of validating the blockchain from the specialized work of constructing highly valuable blocks.

A user first creates and signs a transaction through a wallet or application.

The transaction may enter the public mempool or be sent privately through a service such as Flashbots Protect.

Searchers monitor blockchain state and identify transaction combinations that may produce arbitrage, liquidation, or other MEV opportunities.

Searchers can submit private transactions or ordered transaction bundles to block builders.

Block builders combine public transactions, private transactions, bundles, and other order flow into complete block candidates.

Builders then submit bids for the right to have their block selected by the validator responsible for the current slot.

A relay can verify builder submissions and transfer the winning block between the builder and validator.

The validator signs and proposes the selected block to the Ethereum network.

Other Ethereum nodes independently verify the block according to the network’s consensus and execution rules.

Flashbots developed infrastructure used at several points in this supply chain, but it does not control Ethereum’s consensus rules or independently decide which blocks the network must accept.

What Is a Flashbots Bundle?

A Flashbots bundle is a group of one or more transactions submitted with a specified execution order and block-inclusion conditions.

A bundle may contain transactions created by the searcher, transactions copied from the public mempool, or private transactions provided through another order-flow system.

The transactions are presented to a builder in the sequence in which the sender wants them to execute.

A bundle can target a specific future block and may include minimum or maximum timestamp conditions.

Some bundle formats allow specified transactions to revert, while other failures cause the full bundle to be rejected.

The builder simulates the bundle against an expected blockchain state to determine whether it executes successfully and how much value it contributes.

The builder may include the bundle when it improves the total value of the proposed block.

A bundle is not guaranteed to enter the blockchain because another bundle may offer more value, the targeted state may change, the bundle may arrive too late, or the responsible validator may not use compatible infrastructure.

The official Flashbots bundle documentation explains how grouped transactions are ordered and submitted for potential block inclusion.

How Searchers Use Flashbots

A searcher is a person, team, or automated system that identifies profitable transaction-ordering opportunities.

Searchers may monitor pending transactions, onchain prices, lending positions, liquidity pools, contract events, and expected blockchain state.

When a searcher identifies an opportunity, it can construct a bundle containing the required transaction sequence.

The bundle may include a payment to the block proposer through transaction fees or a direct transfer defined by the transaction logic.

The searcher signs the required transactions and submits the bundle through the Flashbots application programming interface.

An authentication signature identifies the submitting searcher without necessarily using the same private key that holds trading funds.

The builder simulates the bundle and compares its value with other transactions and bundles competing for block space.

Only bundles selected by the winning builder and proposed by the validator become part of Ethereum’s permanent transaction history.

Searcher activity is highly technical and can create substantial losses when a bot contains pricing errors, unsafe approvals, incorrect contract calls, or poor risk controls.

What Is the Flashbots Auction?

The Flashbots Auction is an offchain system through which searchers submit transactions and bundles to block builders.

The auction allows searchers to express how much value their transaction sequence can pay for inclusion.

Builders compare competing bundles and ordinary transactions while constructing a block designed to maximize total value.

Bids are not normally published in real time before the winning block appears onchain.

This blind-auction structure reduces the ability of competing searchers to copy a bid immediately, but it also means a searcher cannot know the exact amount required to win.

Advanced users can interact with the auction through JSON-RPC methods such as

, , and .

The current Flashbots JSON-RPC documentation provides the supported methods, bundle size limits, parameters, and network endpoints.

Submitting a bundle does not transfer ownership of the searcher’s private key to Flashbots because the underlying transactions are signed before submission.

However, the infrastructure receiving the bundle may learn transaction information and proprietary strategy details according to the selected privacy settings.

What Is MEV-Boost?

MEV-Boost is open-source software created by Flashbots for proposer-builder separation on proof-of-stake Ethereum.

It runs alongside an Ethereum validator’s consensus client and allows the validator to request block bids from external relays.

Without MEV-Boost, a validator can construct a block locally using transactions available to its own execution client.

With MEV-Boost, the validator can compare locally built blocks with blocks produced by specialized external builders.

A builder may offer a larger payment because it has access to more order flow, faster infrastructure, and specialized block-optimization software.

The validator can select the most valuable valid block offered through its configured relays.

The official MEV-Boost overview describes the software as a free and open-source implementation of proposer-builder separation.

As of July 14, 2026, the latest stable release shown on the official MEV-Boost release page is version 1.11.

MEV-Boost version 1.11 introduced YAML-based configuration and a timing feature that can delay bid selection briefly in an attempt to receive a more valuable builder bid.

Waiting longer can improve the bid available to the validator, but excessive delay can increase the risk of missing the slot.

How MEV-Boost Works

A validator operator installs MEV-Boost and configures connections to one or more relays.

The validator registers information such as its public key and fee recipient with the connected relays.

When the validator is selected to propose a block, its consensus client requests block bids through the local MEV-Boost process.

MEV-Boost requests bids from the configured relays and compares the valid responses.

The relay initially provides a blinded block header rather than revealing the full transaction payload.

The validator signs the selected header and commits to proposing the associated block.

After receiving the signed commitment, the relay releases the full execution payload.

This design prevents the validator from viewing a builder’s valuable block and then copying its contents into a separate locally constructed block.

The relay must validate builder submissions and ensure that the promised payment and block contents satisfy the required rules.

If a relay fails to deliver the payload quickly enough, the validator may miss the proposal slot and lose potential rewards.

Is MEV-Boost Part of Ethereum’s Core Protocol?

MEV-Boost is an out-of-protocol system rather than a mandatory part of Ethereum consensus.

A validator can participate in Ethereum without installing MEV-Boost.

The software follows the Ethereum Builder API and communicates with consensus clients through standardized interfaces.

Because MEV-Boost is external infrastructure, it introduces trust, availability, and centralization considerations that are not enforced directly by Ethereum consensus.

Relays are expected to verify block validity, protect builder payloads before commitment, and deliver selected payloads on time.

Ethereum researchers continue to study protocol-level forms of proposer-builder separation that could reduce dependence on trusted external relays.

What Is a Flashbots Relay?

A relay is an intermediary connecting block builders with validators using MEV-Boost.

Builders submit complete block candidates and bids to relays.

The relay checks whether a submission is valid and whether the promised proposer payment is present.

It then provides eligible validators with blinded headers representing builder bids.

After a validator signs the selected header, the relay provides the full block payload.

The relay protects builders from having their block contents copied before the validator commits to the block.

It also protects validators by checking builder submissions before they are selected.

A relay can create liveness risk if it becomes unavailable or fails to return the promised payload.

A relay may also create censorship and privacy concerns because it can observe builder submissions and decide which submissions it accepts.

Validator operators commonly connect to more than one relay to reduce dependence on a single provider.

What Is a Block Builder?

A block builder is a specialized participant that constructs complete blocks from public transactions, private order flow, searcher bundles, and other transaction sources.

The builder attempts to arrange these transactions in a way that maximizes the value of the block while keeping the block valid.

Block builders compete by offering payments to the validator assigned to propose the block.

A builder with exclusive access to valuable transaction flow may be able to submit stronger bids than a builder using only the public mempool.

This advantage can create centralization pressure because users and applications may prefer builders that provide better execution or refunds.

The Flashbots documentation for block builders explains how builders construct blocks from several sources of transaction order flow.

What Is Proposer-Builder Separation?

Proposer-builder separation divides block creation into two roles.

The builder collects and orders transactions to create a block.

The proposer is the validator selected by Ethereum consensus to publish the block.

This separation allows specialized builders to compete without requiring every validator to operate advanced MEV-searching infrastructure.

A small independent validator can receive competitive block bids through the same MEV-Boost software used by a large staking operation.

Proposer-builder separation can therefore reduce one source of validator concentration.

However, it can concentrate power among builders and relays when only a small number of organizations have sufficient order flow, capital, data, and low-latency infrastructure.

Flashbots’ newer research focuses heavily on reducing this block-builder concentration.

What Is BuilderNet?

BuilderNet is a collaborative block-building network developed to decentralize Ethereum block construction and redistribute more MEV to users.

It allows several operators to participate in a shared block-building environment instead of operating isolated centralized builders.

The official BuilderNet documentation describes it as a secure and globally distributed Ethereum block-building network.

BuilderNet uses trusted execution environments to protect sensitive transaction data and block-building logic while allowing operators to verify which software is running.

Transactions submitted through BuilderNet can remain private from ordinary external observers before they are included in a block.

BuilderNet can calculate MEV and gas-fee refunds for qualifying transactions submitted through Flashbots Protect.

The project is intended to weaken the advantage created by exclusive order-flow agreements and to allow broader participation in block construction.

BuilderNet remains on a progressive decentralization roadmap rather than being fully permissionless in every operational component.

The current documentation states that some identity management, provisioning, peer discovery, archiving, and development functions still depend on Flashbots-operated infrastructure during the bootstrapping period.

The long-term roadmap aims to decentralize these responsibilities and allow permissionless builder-node operation.

What Is the Latest BuilderNet Version?

As of July 14, 2026, the latest published release listed on the official BuilderNet blog is version 1.6, released on December 2, 2025.

BuilderNet version 1.6 included a rewritten order-flow ingestion layer, consolidation of operator software, performance improvements, and support for Ethereum protocol changes introduced around that release period.

The official BuilderNet development blog publishes release announcements, technical updates, and incident reports.

BuilderNet can evolve rapidly, so node operators and developers should verify current software versions before relying on archived configuration instructions.

What Is a Trusted Execution Environment?

A trusted execution environment, commonly abbreviated as TEE, is a protected computing area designed to isolate code and data from the surrounding operating system and infrastructure operator.

Remote attestation can provide cryptographic evidence that a particular software image is running on supported confidential-computing hardware.

BuilderNet uses TEEs to help protect private transactions, proprietary searcher strategies, and shared block-building data.

A participant can examine an attestation rather than relying only on an operator’s statement that the correct software is running.

TEEs reduce certain trust requirements but do not make the system completely trustless.

Hardware vulnerabilities, supply-chain problems, incorrect attestation verification, physical attacks, cloud-operator control, and bugs in the protected software remain possible.

Metadata such as timing, network connections, and message sizes may reveal information even when transaction contents are protected.

The Flashbots research on TEE attestation limitations discusses gaps that can remain between hardware claims and full application-level security.

What Is Flashbots Protect?

Flashbots Protect is a private transaction-routing service designed to reduce frontrunning, sandwich attacks, failed transaction fees, and excessive gas payments.

A user sends a signed Ethereum transaction to the Flashbots Protect remote procedure call endpoint instead of broadcasting it directly to the public mempool.

The transaction is then routed privately through Flashbots infrastructure and BuilderNet.

Because the transaction is not immediately visible in the public mempool, ordinary frontrunning bots have less opportunity to copy or surround it.

The official Flashbots Protect overview states that transactions are protected from public-mempool frontrunning and are not included by default when they would revert.

This failed-transaction protection can prevent users from paying gas for a transaction that the private simulation expects to fail.

Flashbots Protect can also provide MEV refunds and gas-fee refunds when the transaction qualifies.

Private routing does not guarantee immediate inclusion, a specific execution price, a refund, or complete protection from every form of MEV.

How Flashbots Protect Handles Transactions

Under the standard configuration documented in May 2026, Flashbots Protect attempts to include a transaction for up to 25 blocks before dropping it.

The default configuration does not include transactions paying a zero priority fee.

Reverted transactions are excluded by default unless the sender enables a setting that allows them to revert onchain.

The standard configuration shares limited transaction hints with MEV-Share searchers rather than disclosing the entire transaction publicly.

Users can change the block range, refund recipients, permitted builders, shared hints, and other settings through the Protect RPC configuration.

The current Flashbots Protect settings guide explains the default, fast, privacy, refund, and bundle options.

Users should understand each setting before changing it because more information sharing can improve searcher competition while reducing transaction privacy.

What Is Flashbots Protect Fast Mode?

Fast mode is a Flashbots Protect option designed to increase the probability that a transaction is included quickly.

It shares the transaction with all registered builders instead of keeping it limited to the default route.

It can also allocate a larger part of the MEV refund to the validator to make inclusion more attractive.

Full transaction information without the user’s signature may be shared with searchers operating inside approved trusted execution environments.

Searchers outside those protected environments receive only the hints selected by the user.

Fast mode increases distribution and inclusion opportunities, but broader sharing introduces additional trust relationships.

No fast-routing service can guarantee that the transaction will enter the next block.

What Are Flashbots MEV Refunds?

An MEV refund is a payment returned to a user when the user’s transaction creates an opportunity that a searcher captures through MEV-Share.

A large onchain trade may change a market price and create a profitable backrunning opportunity.

Searchers compete to place a transaction after the user’s trade and can offer part of the expected profit for the right to do so.

MEV-Share can require that part of the searcher’s value be returned to the user or another designated recipient.

Under the documented default Protect configuration, 90% of the MEV refund is directed to the transaction origin and the remaining 10% is directed to the validator.

These percentages can be changed through supported refund settings.

The official MEV refund documentation explains how privacy hints and searcher bids affect potential refunds.

A refund is not guaranteed because many transactions create no profitable MEV opportunity.

The amount also depends on searcher competition, market state, block-builder performance, transaction exclusivity, and whether BuilderNet wins the block.

What Are Flashbots Gas-Fee Refunds?

A gas-fee refund may be paid when a qualifying Flashbots Protect transaction could have been included with a lower priority payment than the user originally offered.

BuilderNet estimates the fee needed to include the transaction and may refund part of the overpayment.

Gas-fee refunds are calculated separately from MEV refunds.

The official gas-fee refund explanation states that eligibility depends on BuilderNet block production, congestion, builder profit, and the transaction’s contribution to the block.

Transactions already visible in the public mempool or sent through non-exclusive routes may be excluded from certain refund calculations.

Users should not assume that every transaction paying a high priority fee will receive money back.

What Is MEV-Share?

MEV-Share is an open-source protocol that allows users, wallets, and applications to capture some of the MEV created by their transactions.

Users send transactions to an MEV-Share node either directly or through Flashbots Protect.

The node reveals selected pieces of transaction information, called hints, to participating searchers.

A hint may reveal the transaction hash, destination contract, function selector, calldata, or selected execution logs.

Searchers use the available information to construct backrun bundles without necessarily seeing the complete private transaction.

The MEV-Share node simulates the bundles and forwards successful candidates to builders with refund requirements.

The official MEV-Share introduction describes the protocol as a permissionless order-flow auction designed to return MEV to the parties that create it.

The current documented implementation accepts backruns rather than allowing searchers to place transactions before the protected user transaction.

This restriction is intended to prevent harmful frontrunning while preserving potentially useful competition after the transaction.

What Are MEV-Share Hints?

A hint is a limited piece of information about a private transaction that the sender allows MEV-Share to disclose to searchers.

Sharing only the transaction hash provides greater confidentiality but may make it difficult for searchers to identify profitable backruns.

Sharing the destination contract or function selector can give searchers more useful information without necessarily revealing every transaction parameter.

Sharing calldata and logs provides more detail and may increase searcher competition and possible refunds.

Greater information sharing creates a tradeoff between privacy and execution value.

A user should not assume that partial disclosure is completely anonymous because contract addresses, timing, transaction size, and other metadata can reveal useful clues.

What Is a Private Transaction?

A private transaction is a signed blockchain transaction sent through a restricted route rather than broadcast immediately to the public peer-to-peer mempool.

The transaction still becomes public after it is included in a block because Ethereum blocks and transaction data are publicly verifiable.

Private routing provides pre-trade privacy rather than permanent transaction secrecy.

It can reduce the period during which an attacker can inspect and react to the pending transaction.

A private transaction may remain pending, expire, be canceled, or eventually be submitted through another route.

The parties receiving it before inclusion may still see some or all of its contents according to the service and privacy configuration.

The Flashbots private transaction API documentation explains how advanced users can submit and cancel individual private transactions.

What Is SUAVE?

SUAVE stands for Single Unifying Auction for Value Expression.

It is Flashbots’ long-term vision for decentralized, private, and programmable transaction-ordering infrastructure.

SUAVE was originally proposed as a way to separate specialized MEV functions from individual blockchains and allow applications to express preferences about execution.

Possible applications include private mempools, order-flow auctions, decentralized block builders, cross-chain coordination, and systems that select among competing execution outcomes.

SUAVE should not be understood as one finished consumer product with a fixed set of features.

Flashbots’ 2026 roadmap presents SUAVE as a phased and modular research direction built from components such as BuilderNet, privacy systems, collaborative block building, and anonymous communication.

The updated 2026 SUAVE roadmap connects the project with broader goals for decentralized block building, scaling, privacy, and censorship resistance.

What Is Flashnet?

Flashnet is a research protocol introduced by Flashbots in February 2026 for anonymous low-latency message broadcasting.

It is intended to hide the network identity of transaction senders while maintaining performance suitable for blockchain block-building systems.

Flashbots expects the protocol to support private transaction submission, censorship resistance, account-abstraction mempools, and communication between participants in distributed block-building networks.

Flashnet addresses a different privacy problem from transaction encryption because an operator may infer information from the network source even when message contents are protected.

The official Flashnet research article describes it as a planned coordination component for moving BuilderNet toward more permissionless operation and the broader SUAVE vision.

Flashnet is an evolving research and development effort rather than a guarantee that all Flashbots traffic is currently anonymous.

Benefits of Flashbots

Flashbots can reduce failed gas auctions by allowing searchers to submit conditional bundles outside the public mempool.

Private routing can protect ordinary users from common public-mempool frontrunning and sandwich strategies.

MEV-Share can return part of the value created by a user transaction to that user.

Gas-fee refunds can reduce unnecessary priority-fee overpayments in qualifying BuilderNet blocks.

MEV-Boost gives validators access to a competitive block market without requiring each validator to develop its own searcher and builder infrastructure.

Open-source software allows independent developers to inspect, test, modify, and operate compatible infrastructure.

Public research and data can improve understanding of block construction, censorship, transaction ordering, and market concentration.

BuilderNet attempts to reduce dependence on isolated centralized builders and exclusive order flow.

Risks and Limitations of Flashbots

Flashbots infrastructure does not remove smart contract risk, market risk, private-key risk, or the possibility of an unfavorable trade.

A private transaction can remain pending longer than expected or fail to reach the validator responsible for the winning block.

Users depend on transaction routers, builders, relays, and validators to handle private order flow according to their documented rules.

Relays and builders can experience outages, software errors, network delays, or security incidents.

A validator relying on an unavailable relay may miss a proposal slot.

Private order flow can create centralization advantages for builders that receive the most valuable transactions.

MEV-Boost makes builder competition accessible to validators but does not make the relay and builder markets fully decentralized.

Trusted execution environments reduce some privacy risks but remain dependent on hardware, attestation systems, and correct software.

Searchers can lose money through incorrect simulations, changed blockchain state, poor bidding, competition, or programming mistakes.

Refund calculations are not guaranteed and may be difficult for an ordinary user to predict before a transaction executes.

Changes to Flashbots software, policies, supported networks, and endpoints can affect existing integrations.

Flashbots and Blockchain Centralization

MEV can encourage centralization because the most successful builders may gain access to better private order flow and use their profits to improve infrastructure.

Low latency, advanced simulation, large amounts of capital, and direct relationships with applications can create advantages that smaller participants cannot easily match.

Validators may prefer the builders that consistently submit the highest bids, increasing the market share of already successful builders.

Relays can also become centralized when validators rely heavily on a small number of operators.

Flashbots’ early infrastructure helped isolate MEV competition into specialized roles, but this separation also made builder concentration a major concern.

BuilderNet, MEV-Share, SUAVE, and Flashnet are intended to reduce exclusive control over order flow and block building.

These projects should be evaluated by their actual operator diversity, permission requirements, software transparency, hardware dependencies, and resilience rather than by decentralization claims alone.

Does Flashbots Censor Transactions?

Flashbots software does not change Ethereum’s consensus rules or prevent users from submitting valid transactions through the public network.

However, any private builder or relay can decide which transactions and bundles it accepts or includes.

A private transaction submitted through only one route may be delayed when that route does not build the winning block.

Rules imposed by infrastructure operators, legal obligations, service policies, technical filters, or outages can affect transaction handling.

Users seeking greater inclusion probability can select routing options that share transactions with more builders, although broader distribution can change privacy and refund conditions.

Long-term censorship resistance requires diversity among builders, relays, validators, transaction routes, and software implementations.

Is Flashbots Safe for Ordinary Crypto Users?

Flashbots Protect can reduce several common transaction risks, but it should not be treated as a complete security system.

It cannot determine whether the smart contract a user is calling is legitimate or malicious.

It cannot recover cryptocurrency sent to the wrong address or reverse an included blockchain transaction.

It cannot guarantee that a swap’s price remains favorable while the transaction is pending.

Users must still review the destination address, token approvals, slippage settings, transaction value, network, and wallet request.

Flashbots does not require a user to reveal a wallet seed phrase or private key to route a signed transaction.

A website or support account requesting these secrets in the name of Flashbots should be treated as fraudulent.

Is Flashbots a Token?

Flashbots is not a native cryptocurrency or required utility token.

Users do not need to purchase a Flashbots-branded token to use MEV-Boost, Flashbots Protect, or the public documentation.

A crypto asset using a similar name should not automatically be assumed to have an official relationship with the organization.

Users should verify announcements through the official Flashbots documentation and the verified Flashbots GitHub organization.

How Developers Can Use Flashbots

Application developers can integrate Flashbots Protect to offer private transaction submission and potential refunds.

Wallet developers can configure transaction privacy, shared MEV-Share hints, builder distribution, and refund recipients.

Searcher developers can submit private transactions and bundles through supported JSON-RPC methods.

Validator operators can install MEV-Boost and connect it to compatible consensus clients and relays.

Block-builder developers can use Flashbots specifications, open-source relay software, testing frameworks, and builder implementations.

Researchers can analyze published block data, auction behavior, builder concentration, censorship, latency, and MEV distribution.

Developers should first test transaction and bundle logic on a supported test network before risking mainnet cryptocurrency.

Production integrations should monitor API changes, release notes, rate limits, incident reports, and software signatures.

How to Evaluate Flashbots Data

Flashbots data can help users examine block bids, builder activity, relay performance, refunds, and MEV behavior.

Public blockchain data shows which transactions were ultimately included but may not reveal every unsuccessful private bid or bundle.

A profitable transaction identified onchain does not always reveal which participant designed the strategy or how offchain payments were divided.

Builder and relay labels may depend on public keys, fee recipients, self-identification, or third-party classification.

Market-share figures can change depending on the time period, data source, missed slots, and classification method.

Users should distinguish measured onchain outcomes from estimates of private order flow and unrealized MEV.

Common Misconceptions About Flashbots

Flashbots does not control Ethereum.

Ethereum nodes independently validate every proposed block according to consensus rules.

Flashbots does not eliminate all frontrunning or guarantee the best execution for every transaction.

Private transactions become public after block inclusion.

MEV-Boost is not mandatory for Ethereum validators.

Running MEV-Boost does not automatically make a validator malicious or dishonest.

MEV is not always harmful because arbitrage and liquidations can support market and lending-protocol operation.

Flashbots Protect is not a wallet and does not hold the user’s seed phrase.

BuilderNet is not yet fully permissionless in every operational component.

A trusted execution environment is not the same as a completely trustless system.

An MEV refund is not guaranteed profit.

Flashbots does not have a required native token.

Frequently Asked Questions

What does Flashbots mean in crypto?

Flashbots is a research and infrastructure organization that develops tools for managing MEV, private transactions, block building, and proposer-builder separation.

What problem does Flashbots solve?

Flashbots reduces harmful competition, failed transactions, public-mempool frontrunning, and opaque MEV extraction while supporting more competitive block production.

What is MEV?

MEV is the additional value obtained by including, excluding, or changing the order of blockchain transactions beyond ordinary block rewards and transaction fees.

Is Flashbots a cryptocurrency?

No, Flashbots is an organization and software ecosystem rather than a coin or token.

Does Flashbots have a native token?

No official native token is required to use Flashbots’ core public tools.

Is Flashbots part of Ethereum?

Flashbots builds infrastructure for Ethereum, but its main tools operate outside the core Ethereum consensus protocol.

What is MEV-Boost?

MEV-Boost is open-source software that lets Ethereum validators receive block bids from external builders through relays.

What is the latest MEV-Boost version?

As of July 14, 2026, the latest stable release shown by the official repository is MEV-Boost version 1.11.

Does an Ethereum validator need MEV-Boost?

No, a validator can build blocks locally, but MEV-Boost provides access to competitive external builder bids.

What is a Flashbots bundle?

A Flashbots bundle is an ordered group of transactions submitted with conditions for possible inclusion in a particular block.

Are Flashbots bundles guaranteed to execute?

No, a bundle may lose to a stronger bid, fail simulation, arrive late, target the wrong state, or be submitted for a slot whose validator does not use compatible infrastructure.

What is Flashbots Protect?

Flashbots Protect is a private transaction-routing service designed to reduce public-mempool frontrunning, sandwich attacks, failed transaction fees, and certain gas overpayments.

Are Flashbots Protect transactions private forever?

No, they receive pre-trade privacy but become publicly visible after they are included in an Ethereum block.

Does Flashbots Protect guarantee transaction inclusion?

No, inclusion depends on builder access, validator selection, transaction validity, fees, timing, and network conditions.

What is an MEV refund?

An MEV refund is a payment returned to a user when searchers capture value created by that user’s transaction through MEV-Share.

Does every Flashbots transaction receive a refund?

No, refunds depend on whether the transaction creates value, attracts competitive searcher bids, and enters a qualifying block.

What is MEV-Share?

MEV-Share is an order-flow auction protocol that selectively shares transaction hints with searchers and redistributes part of resulting MEV.

Can MEV-Share searchers frontrun protected transactions?

The current documented system accepts backruns rather than transactions placed before the protected user transaction.

What is BuilderNet?

BuilderNet is a collaborative Ethereum block-building network using trusted execution environments and a roadmap toward more decentralized operation.

Is BuilderNet fully decentralized?

No, its roadmap targets permissionless operation, but current bootstrapping infrastructure still relies on selected operators and Flashbots-managed components.

What is the latest BuilderNet version?

As of July 14, 2026, the latest published release on the official BuilderNet blog is version 1.6.

What is SUAVE?

SUAVE is Flashbots’ broader architecture and research vision for private, programmable, and decentralized transaction-ordering systems.

What is Flashnet?

Flashnet is a low-latency anonymous broadcast protocol proposed for private transaction submission and distributed block-building communication.

What is a Flashbots searcher?

A searcher is a participant operating software that identifies MEV opportunities and submits private transactions or bundles to builders.

What is a Flashbots relay?

A relay verifies builder blocks, presents blinded bids to validators, and reveals the selected payload after the validator commits to it.

Can Flashbots reverse an Ethereum transaction?

No, Flashbots cannot reverse a valid transaction after it has been included and finalized on Ethereum.

Can Flashbots prevent every sandwich attack?

No, private routing can reduce exposure to common public-mempool attacks, but protection depends on routing, trust assumptions, transaction leakage, and execution conditions.

Does Flashbots store private keys?

Normal use involves sending signed transactions, so users should never provide their wallet private key or seed phrase to Flashbots or anyone claiming to represent it.

Is using Flashbots risk free?

No, users still face smart contract, market, privacy, infrastructure, delay, and transaction-configuration risks.

How can developers test Flashbots tools?

Developers can use supported test-network endpoints and local simulation before submitting bundles or transactions involving valuable mainnet assets.

Conclusion

Flashbots is a cryptocurrency research and infrastructure organization focused on Maximal Extractable Value, private transaction routing, block construction, and Ethereum proposer-builder separation.

Its tools changed how searchers communicate with block producers by allowing private bundles and direct bids instead of relying entirely on public-mempool gas competition.

MEV-Boost gives validators access to blocks created by specialized builders, while Flashbots Protect offers users private transaction submission and potential protection from common frontrunning strategies.

MEV-Share allows users and applications to receive part of the value generated by their order flow.

BuilderNet uses collaborative block construction and trusted execution environments to reduce builder centralization and redistribute block value.

SUAVE and Flashnet extend the longer-term roadmap toward private, programmable, anonymous, and permissionless transaction-ordering infrastructure.

Flashbots does not eliminate MEV, control Ethereum, guarantee refunds, or remove every transaction risk.

Its importance comes from making the MEV supply chain more visible and providing open tools for users, validators, builders, searchers, developers, and researchers to participate under clearer rules.