Private Order Flow

What Is Private Order Flow?

Private order flow refers to blockchain transactions that bypass the public mempool and are submitted directly to block builders through private channels. In standard Ethereum operation, when a user sends a transaction, it is broadcast to a peer-to-peer network of nodes that maintain a shared waiting area called the mempool. Every pending transaction in the mempool is visible to anyone monitoring the network, including automated bots (searchers) that scan for profitable opportunities.

This visibility creates a problem. Searchers can observe a large swap on a decentralized exchange, place their own trade ahead of it to move the price (front-running), and then sell after the victim's trade executes at a worse price. This extraction of value from ordinary users is a core component of maximal extractable value (MEV). Private order flow emerged as a defense: if the transaction never appears in the public mempool, searchers cannot see it and cannot exploit it.

The concept draws parallels to dark pools in traditional finance, where institutional orders are matched away from public exchanges to prevent market impact. On Ethereum, private order flow has grown from a niche practice to the dominant way transactions reach the chain. By early 2025, roughly half of all Ethereum transactions were routed through private channels rather than the public mempool.

How It Works

Private order flow operates within Ethereum's proposer-builder separation (PBS) architecture, where block construction is handled by specialized builders rather than validators themselves. The flow works as follows:

1. A user configures their wallet to use a private RPC endpoint (such as Flashbots Protect) instead of a standard public Ethereum node
2. When the user submits a transaction, it is sent to the private RPC service rather than broadcast to the public mempool
3. The service forwards the transaction to one or more block builders, optionally sharing limited "hints" (partial transaction data) with a set of searchers
4. Searchers compete to create beneficial backrun transactions that capture arbitrage opportunities created by the user's trade
5. The builder bundles the user's transaction with the winning searcher's backrun into a block and submits it to the MEV-Boost auction
6. The validator (proposer) selects the most valuable block and proposes it to the network

The user's transaction only becomes visible once it is included in a finalized block. At no point does it sit in the public mempool where adversarial searchers could target it.

Order Flow Auctions

Many private order flow services use a mechanism called an order flow auction (OFA). Rather than simply hiding transactions, they allow searchers to compete for the right to backrun a user's trade. Backrunning is generally harmless to the user: the searcher captures arbitrage that exists after the user's trade executes, without affecting the user's execution price.

The key innovation is that the value captured by the backrun is partially or fully refunded to the original user. This turns MEV from a tax on users into a rebate. Different services structure these auctions differently:

• Flashbots Protect uses the MEV-Share protocol, which lets users control how much transaction data is revealed to searchers. Users receive 100% of the backrun refund, with Flashbots taking no cut.
• MEV Blocker (built by CoW DAO) shares full transaction details with registered searchers and returns 90% of the backrun bid to users, with 10% going to the validator.

Configuring a Wallet

Adding private transaction protection typically requires changing a single RPC setting in a wallet like MetaMask:

// Flashbots Protect RPC endpoint
Network Name: Flashbots Protect
RPC URL: https://rpc.flashbots.net/fast
Chain ID: 1
Currency: ETH

// Transactions sent through this RPC bypass
// the public mempool automatically

Once configured, all transactions from the wallet are routed privately with no change to the user experience. The transaction lands on-chain with a median inclusion time under one block.

Why It Matters

MEV extraction imposes a real cost on Ethereum users. Research estimates that over $1.2 billion in cumulative MEV has been extracted on Ethereum, with sandwich attacks accounting for roughly 51% of all MEV volume as of 2025. Every user who swaps tokens on a DEX without MEV protection risks receiving a worse price than they should.

Private order flow matters for several reasons beyond individual protection:

• It reduces the effective cost of using DeFi by eliminating slippage caused by front-running, making decentralized exchanges more competitive with centralized alternatives
• Order flow auctions convert adversarial MEV extraction into user refunds, aligning incentives between searchers and the users whose transactions create the opportunity
• For protocols and applications that route user transactions, offering MEV protection has become a competitive differentiator and a matter of user trust

The growth of private order flow also has implications for other blockchain ecosystems. Bitcoin's UTXO model and lack of a global state machine make MEV extraction structurally different, but as DeFi activity expands to Bitcoin Layer 2 networks, the lessons from Ethereum's private order flow evolution are directly relevant. For a deeper analysis, see the research on MEV extraction on Bitcoin L2s.

Use Cases

DEX Traders

The most common use case is protecting token swaps on decentralized exchanges like Uniswap or Curve. Without private routing, a large swap through an automated market maker is visible in the mempool and can be sandwiched: a searcher places a buy before the victim's trade (pushing the price up) and a sell immediately after (profiting from the inflated price). The victim receives fewer tokens than they would have in an unmanipulated market.

With private order flow, the swap is invisible until it is included in a block, eliminating the sandwich opportunity entirely.

NFT Mints and Token Launches

During high-demand events like NFT mints or token launches, public transactions can be front-run by bots that detect the mint transaction and submit their own with higher gas fees. Private submission ensures the user's transaction reaches the builder without being outbid or displaced.

Liquidation Protection

DeFi users managing leveraged positions risk having their collateral management transactions front-run. If a user submits a transaction to add collateral and avoid liquidation, a searcher could front-run it to trigger the liquidation first and claim the reward. Private routing removes this vulnerability.

Protocol-Level Integration

Some DeFi protocols integrate private order flow at the smart contract or router level. CoW Protocol, for example, batches user orders off-chain and submits them as a single private transaction, providing MEV protection by design rather than requiring users to configure their wallets individually.

Risks and Considerations

Builder Centralization

The most significant concern with private order flow is its centralizing effect on block building. As of early 2025, two builders (Beaverbuild/BuilderNet and Titan Builder) produced approximately 86% of all Ethereum mainnet blocks. This concentration is driven by a self-reinforcing cycle: builders with more exclusive order flow can construct more valuable blocks, win more auctions, and attract even more order flow.

Research from the ACM Web Conference 2025 found that the top three builders control over 95% of winning blocks and can submit bids roughly 27% lower than competitors while maintaining their win rate, because their exclusive order flow makes their blocks inherently more valuable. This undermines the decentralization goals that PBS was designed to achieve.

Incomplete Protection

Private order flow does not guarantee complete safety from MEV extraction. Research published in late 2024 documented 2,932 confirmed sandwich attacks against private transactions during November and December 2024, causing over $409,000 in user losses. These attacks were possible because some builders or intermediaries in the private pipeline either leaked transaction data or engaged in adversarial behavior themselves.

A single entity was responsible for roughly 65% of these private sandwich attacks, highlighting that private does not mean trustless: users must trust the private RPC service and the builders it forwards transactions to.

Transparency and Censorship

Blockchains derive much of their value from transparency: anyone can verify the state of the network and the contents of the mempool. Private order flow moves a growing share of economic activity into opaque channels controlled by a small number of entities. This raises concerns about censorship resistance: if most transactions flow through a handful of builders, those builders gain the power to selectively include or exclude transactions.

The European Securities and Markets Authority (ESMA) flagged this in its 2025 report on crypto-assets, noting that centralization at the relay and builder levels creates operational and censorship risks for the Ethereum network.

The Encrypted Mempool Alternative

Some researchers argue that private order flow is a band-aid that treats the symptom (MEV exploitation) while creating new problems (centralization). An alternative approach is the encrypted mempool, where transactions are encrypted before broadcast and only decrypted after block ordering is finalized. This would preserve the public nature of the mempool while making front-running technically impossible.

Projects like Shutter Network are developing threshold-encrypted mempool solutions and have proposed EIP-8105 for a universal enshrined encrypted mempool on Ethereum. Shutter's approach has been live on Gnosis Chain since mid-2024. If successful, encrypted mempools could reduce the need for private order flow entirely.

Private Order Flow vs. Public Mempool

The Road Ahead

The Ethereum community is exploring several paths to address the tradeoffs of private order flow:

• BuilderNet, launched by Flashbots in late 2024, uses trusted execution environments (TEEs) to create a decentralized block-building network where no single entity can see or censor transactions
• Encrypted mempools (Shutter Network, EIP-8105) aim to make front-running technically impossible at the protocol level, reducing the need for private channels entirely
• Enshrined PBS proposals would move builder separation into Ethereum's consensus layer, giving the protocol more control over how order flow is handled

The outcome of this debate will shape whether Ethereum evolves toward a transparent, protocol-enforced solution to MEV or continues to rely on off-protocol private infrastructure controlled by a small number of market participants.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.