Flashbots Protect is a public service that provides a secure gateway for submitting Ethereum transactions, designed to protect users from harmful Maximal Extractable Value (MEV) strategies like frontrunning and sandwich attacks. By routing transactions through the Flashbots private mempool (also known as the SUAVE-aligned relay network), it prevents opportunistic bots on the public mempool from seeing and exploiting pending transactions for profit. This service is offered as a free RPC endpoint that any wallet or dApp can integrate, effectively creating a private channel to block builders.
Flashbots Protect
What is Flashbots Protect?
Flashbots Protect is a free RPC endpoint that shields users from frontrunning and sandwich attacks by submitting transactions directly to the Flashbots private mempool.
The core mechanism relies on the sealed-bid auction model pioneered by Flashbots. Transactions sent via Protect are bundled and submitted directly to professional block builders, who compete to include them in the next block without revealing their contents to the general network. This process eliminates the public visibility that predatory bots rely on. Crucially, users maintain transaction privacy only until the block is proposed, at which point the transaction is executed on-chain with the same finality as a standard transaction, but with a significantly reduced risk of being exploited.
For the end-user, using Flashbots Protect is often as simple as selecting it as a network option in a supporting wallet like MetaMask. The service handles the complexities of bundle submission and auction mechanics in the background. Its primary benefits are protection from value extraction, potentially better gas estimation leading to lower overall costs (by avoiding failed frontrun attempts), and the ethical stance of not rewarding harmful MEV. It represents a practical application of MEV-aware infrastructure that shifts advantage back to regular users.
It is important to distinguish Flashbots Protect from simple transaction acceleration services. While both aim to improve transaction outcomes, Protect's fundamental goal is censorship resistance against malicious bots, not just speed. Transactions sent via Protect are also not subject to the same gas price auctions that occur in the public mempool, which can lead to more predictable fees. However, as a trade-off for privacy, transactions are only included if a builder selects the bundle, though in practice reliability is very high for standard transactions.
The development of Flashbots Protect is part of a broader ecosystem initiative to democratize access to MEV protection. It complements other Flashbots products like the Flashbots Auction for searchers and the SUAVE platform. By providing this public good, Flashbots aims to mitigate the negative externalities of MEV, making DeFi and other on-chain activities safer and more equitable for all participants without requiring them to understand the underlying complexities of blockchain mempool dynamics.
How Flashbots Protect Works
Flashbots Protect is a public RPC endpoint that shields users from harmful Maximal Extractable Value (MEV) by routing their transactions through a private, permissionless mempool.
Flashbots Protect is a free, public service that functions as an alternative to the standard Ethereum public mempool. When a user submits a transaction via its RPC endpoint, it is sent directly to a network of searchers and builders within the Flashbots ecosystem, bypassing the open network where it could be frontrun or sandwiched. This private transaction flow prevents opportunistic bots from seeing the transaction details until it is included in a block, thereby neutralizing common forms of harmful MEV extraction.
The core mechanism relies on the Flashbots Auction, a two-stage process. First, specialized searchers analyze the private transaction and may bundle it with others to create profitable MEV opportunities, such as arbitrage or liquidations. These bundles are then sent to block builders, who compete to construct the most valuable block by including the most profitable bundles. Crucially, builders submit their complete block proposals directly to validators via mev-boost, ensuring the transaction is only revealed upon successful block inclusion.
For the end-user, using Flashbots Protect is as simple as selecting Flashbots Protect RPC in their wallet interface (like MetaMask) or connecting to the public endpoint https://rpc.flashbots.net. The service is non-custodial and does not require an API key. Its primary benefit is transaction privacy during the pre-confirmation phase, which protects against predatory trading strategies that exploit visible pending transactions in the public mempool.
A key feature is its commitment to failed transaction protection. When a transaction submitted via Protect fails (e.g., due to a revert or insufficient gas), it is not broadcast to the public chain, and the user is not charged any gas fees. This gasless failure model contrasts with the public mempool, where failed transactions still incur costs, providing significant economic safety for users interacting with complex DeFi protocols.
Flashbots Protect is part of a broader suite of infrastructure aimed at democratizing MEV. By providing a public good that routes transactions through a private channel, it mitigates the negative externalities of MEV for ordinary users while allowing the value extraction to be competed over in a transparent, efficient marketplace via the builder ecosystem. It represents a critical piece of infrastructure for fairer transaction ordering on Ethereum.
Key Features of Flashbots Protect
Flashbots Protect is a public RPC endpoint that shields users from harmful MEV by routing transactions through the Flashbots private relay, preventing frontrunning and sandwich attacks.
Private Transaction Routing
The core mechanism that prevents frontrunning. Instead of broadcasting a transaction to the public mempool, Protect sends it directly to the Flashbots Relay. This keeps the transaction's details hidden from searchers who scan the public mempool for profitable opportunities, effectively eliminating the chance of being frontrun or sandwiched.
MEV-Share Integration
Enables users to potentially capture value from their transactions. When a transaction creates a profitable MEV opportunity (like a large DEX swap), MEV-Share allows searchers to bid for the right to include it in a bundle. A portion of this bid is returned to the user as a rebate, turning a potential loss into a gain. This creates a more equitable distribution of MEV value.
No Failed Transaction Fees
Protect uses a simulate-bundle model. Before a bundle containing your transaction is submitted to the network, it is simulated to ensure it will succeed. If the simulation fails (e.g., due to slippage or a revert), the bundle is not submitted. This means users do not pay gas fees for failed transactions, a significant improvement over the standard public mempool experience.
RPC Endpoint Simplicity
Requires no changes to user wallets or dApp code. Users simply change their wallet's RPC endpoint to https://rpc.flashbots.net. This makes adoption seamless for end-users and developers alike, as it integrates with existing Ethereum tooling like MetaMask without requiring smart contract modifications or complex SDKs.
Censorship Resistance via Permissionless Builders
While the Flashbots Relay is a centralized component, it is designed to be credibly neutral. It forwards transaction bundles to a competitive, permissionless network of block builders. This multi-builder landscape helps mitigate the risk of transaction censorship, as no single entity controls which valid bundles are included in a block.
Protection Scope & Limitations
Protect is highly effective against opportunistic MEV like frontrunning and sandwich attacks on DEX swaps. It does not protect against:
- Time-bandit attacks (chain reorgs)
- MEV inherent to a transaction's logic (e.g., arbitrage between two of your own swaps)
- Attacks that do not rely on mempool visibility (e.g., NFT sniping based on on-chain events) Understanding these boundaries is crucial for setting user expectations.
Ecosystem Usage & Integration
Flashbots Protect is a public RPC endpoint that allows users to submit transactions directly to the Flashbots network, shielding them from frontrunning and sandwich attacks on Ethereum. It is the primary user-facing gateway for accessing Flashbots' MEV protection services.
Comparison: Public vs. Private Transactions
Using Flashbots Protect fundamentally changes transaction flow:
- Standard Flow: Tx β Public Mempool β Visible to Searchers β Potential Frontrun β Included by Miner.
- Protect Flow: Tx β Flashbots Relay β Private Order Flow Auction β Bundle Built by Builder β Included in Block. The key difference is the removal of the public mempool visibility window, which is the source of most sandwich attacks and frontrunning. Transactions are only observable on-chain after they have been executed.
Use Cases and Limitations
Ideal for:
- Large DeFi swaps (e.g., Uniswap, Curve) where slippage matters.
- NFT minting and competitive bidding.
- Arbitrage and liquidations where timing is critical.
Limitations:
- Not all builders support all chains; primarily focused on Ethereum Mainnet.
- Transactions may have slightly higher latency as they wait for a builder to include them in a bundle.
- Does not protect against time-bandit attacks or cross-domain MEV.
Visual Explainer: The Transaction Journey
This visual guide traces the path of a user's transaction from wallet submission to on-chain confirmation, highlighting the critical role of Flashbots in shielding users from predatory Maximal Extractable Value (MEV) strategies.
The journey begins when a user signs and broadcasts a transaction, typically via their wallet. In a traditional public mempool model, this transaction becomes immediately visible to all network participants, including searchers who scan for profitable MEV opportunities. This exposure creates significant risks: transactions can be front-run, where a searcher's identical but higher-fee transaction is processed first to capture a trading profit, or sandwiched, where buy and sell orders are placed around the user's trade to extract value from slippage. For users, this results in failed transactions, worse prices, and a poor experience.
Flashbots Protect, specifically its RPC endpoint (rpc.flashbots.net), provides an alternative route. Instead of broadcasting to the public Ethereum mempool, transactions are sent directly to the Flashbots relay. This relay acts as a private communication channel to block builders, who are entities that assemble the contents of a new block. By bypassing the public mempool, the transaction details are hidden from general network observers, eliminating the surface area for front-running and sandwich attacks during the propagation phase. This is the core of transaction privacy in the MEV supply chain.
Once received by the relay, the transaction is forwarded to a network of builders who compete to create the most profitable block. Builders incorporate the user's transaction into their block proposals alongside bundles from searchers. Crucially, Flashbots Protect transactions are given priorityβthey cannot be displaced by other transactions paying higher fees within the same builder's block. This guarantee protects against time-bandit attacks, where a searcher might try to reorganize the chain to steal a pending transaction. The builder's block is then sent to the relay, which validates it before passing it to validators (or proposers) for inclusion in the blockchain.
The final step occurs when a validator, selected to propose the next block, retrieves the most profitable block from the relay. They then attest to and publish this block on-chain. From the user's perspective, their transaction either appears successfully in the next block or fails simulated execution and reverts without ever being publicly broadcast, saving them gas fees. This end-to-end process, known as the Flashbots Protect pipeline, demonstrates how MEV infrastructure can be redesigned to offer users credible neutrality and protection, turning a potential economic negative into a service that enhances blockchain usability.
Comparison: Public Mempool vs. Flashbots Protect
A feature-by-feature comparison of submitting transactions to the public mempool versus using the Flashbots Protect RPC endpoint.
| Feature / Metric | Public Mempool | Flashbots Protect |
|---|---|---|
Transaction Visibility | Public to all network participants, including searchers and arbitrage bots. | Private until inclusion in a block; visible only to builders in the Flashbots Relay. |
Frontrunning Risk | ||
Sandwich Attack Risk | ||
Transaction Ordering | Determined by the public gas auction (gas price/priority fee). | Determined by builder logic, often based on total MEV or fee value. |
Failed Transaction Cost | Gas is paid for failed transactions that are included in a block. | No gas cost for failed transactions (revert protection). |
Submission Path | Sent directly to a public Ethereum node. | Sent via the |
Censorship Resistance | High; any validator can include the transaction. | Medium; dependent on builders connected to the Flashbots Relay. |
Primary Use Case | Standard, non-sensitive transactions. | MEV-sensitive trades, arbitrage, large liquidations, NFT minting. |
Security Considerations & Limitations
Flashbots Protect is a service that shields users from Maximum Extractable Value (MEV) exploitation by routing transactions through a private, off-chain relay. While it offers significant security benefits, its architecture introduces specific considerations.
Reliance on Trusted Relays
The service's security model depends on the integrity of the Flashbots relay. Users must trust that the relay operators will not censor, front-run, or leak their transactions. While Flashbots has a strong reputation, this introduces a trust assumption into a system designed to be trust-minimized.
- Centralization Risk: The relay is a centralized component, creating a potential single point of failure or censorship.
- Relay Governance: The relay's policies on transaction inclusion are set by the Flashbots team, not by on-chain consensus.
Transaction Reversion & Non-Inclusion
Transactions submitted via Protect are not guaranteed to be included in a block. The relay only forwards bundles to builders if they are profitable for the searcher creating them. This can lead to:
- Failed Transactions: If a transaction's execution reverts during simulation, it will be dropped by the relay.
- Stranded Transactions: Low-fee or complex transactions that are not MEV-opportunities may never be picked up by a builder, causing them to timeout.
- No Gas Auction: Users cannot pay a higher priority fee to force inclusion, as the relay uses a first-come, first-served queue.
Limited Blockchain Support
Flashbots Protect is not a universal solution. Its availability and security guarantees are chain-specific.
- Ethereum-Centric: The primary, most battle-tested implementation is for Ethereum Mainnet. Support for other EVM chains (e.g., Arbitrum, Polygon) may be experimental or non-existent.
- Architectural Differences: Chains with different consensus mechanisms (e.g., Solana, Cosmos) require entirely different MEV mitigation designs. Protect's model does not directly translate.
No Protection Against All MEV
Protect specifically guards against frontrunning and sandwich attacks in the public mempool. It does not eliminate other forms of MEV that occur on-chain.
- Backrunning: Searchers can still observe and execute transactions that follow a user's action in the same block.
- Arbitrage & Liquidations: These are non-adversarial MEV and are a natural part of market efficiency. Protect does not prevent these actions; it only prevents others from stealing the opportunity via frontrunning.
- Long-term MEV: Strategies like Oracle manipulation or governance attacks are outside its scope.
Privacy vs. Accountability Trade-off
By moving transactions off the public mempool, Protect enhances privacy but reduces transparency and auditability.
- Opaque Order Flow: It becomes difficult for network participants to monitor transaction flow and detect systemic manipulation or censorship.
- Regulatory Scrutiny: The private relay model can attract attention from regulators concerned about off-chain coordination and market fairness.
- Builder Centralization: The system relies on a small set of sophisticated block builders, potentially consolidating power over block construction.
Integration and User Error Risks
Security depends on correct implementation by wallets and users.
- RPC Endpoint Configuration: Users must correctly configure their wallet (e.g., MetaMask) to use the Flashbots Protect RPC. Mistakes revert them to the vulnerable public mempool.
- Smart Contract Wallets: Support for account abstraction and smart contract wallets can be limited or require specific integration.
- Simulation Failures: Complex transactions involving multiple contracts may fail simulation in the relay for nuanced reasons, leaving users without clear error messages.
Frequently Asked Questions (FAQ)
Common questions about Flashbots Protect, a service that allows users to submit private transactions to protect against frontrunning and failed transactions on Ethereum.
Flashbots Protect is a Relay service that allows users to submit private transactions to the Flashbots Auction to protect them from frontrunning and sandwich attacks. It works by routing transaction bundles through a private communication channel to block builders (searchers) who include them directly in a block, bypassing the public mempool. This prevents malicious actors from seeing the transaction details and exploiting them before confirmation. Users submit their transactions to the Protect RPC endpoint, and builders compete to include them in the next block, often providing a refund for any unused gas.
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.