PBS Auction and MEV-Boost: How Ethereum Blocks Get Built

What is the PBS auction on Ethereum?

Proposer-builder separation, usually called PBS, is a way of splitting two jobs involved in producing an Ethereum block. A proposer is the validator selected by Ethereum’s proof-of-stake protocol to publish the next block. A block builder is a specialized operator that gathers transactions, decides their order, simulates the result, and creates a profitable block for the proposer to publish.

The PBS auction is the competition between builders for that proposer’s block slot. Builders calculate how much value a particular block can produce, then offer a payment in ETH to the proposer. The proposer normally chooses the highest valid-looking bid. In plain English, builders are buying a brief right to supply the next block, and validators are selling that right through automated software.

The value being auctioned is not simply a collection of ordinary gas fees. It often includes maximal extractable value, or MEV, the value available from ordering, including, excluding, or inserting transactions. Liquidations in DeFi lending markets, arbitrage between exchanges, and user swaps can all create MEV. The auction can route part of that value to validators, but it does not make the underlying competition harmless or equally distributed.

Why MEV and block auctions carry real risks

MEV is not a bonus created from nothing. In many cases, it comes from traders or application users receiving a worse outcome because another party reordered transactions faster. A common example is a sandwich attack, where a searcher places one trade before and one after a user’s swap, worsening the user’s execution price. Builders may include bundles designed by searchers, so the final block reflects a competitive and sometimes adversarial market for transaction order.

There are operational risks too. A validator relying on MEV-Boost depends on software, relays, internet connectivity, and external builder bids during a short Ethereum slot. If that infrastructure fails, a validator can miss a block proposal and lose expected income. A builder can also withhold the full block after a proposer signs for it, although relay designs aim to reduce that risk by checking payload availability before exposing a bid.

History shows that complex incentives can fail in ways that are expensive before users understand them. DeFi liquidations have cascaded during volatile markets, bridges and smart contracts have lost large sums through exploits, and validators have faced slashing penalties for certain serious protocol mistakes. PBS does not directly custody a validator’s staked ETH, but running unfamiliar validator infrastructure, following copied configurations, or trusting an unvetted relay can still create financial and uptime risk.

How the proposer-builder separation pipeline works

Ethereum selects a proposer for each roughly 12-second slot. Without PBS tooling, that validator’s execution client can build a block itself from transactions in its mempool, the waiting area for submitted transactions. With MEV-Boost, the proposer can ask multiple relays for blinded block bids instead. A blinded block header reveals key block details and the promised payment, but not the full transaction list or execution payload.

A block builder is the party doing the intensive assembly work. It receives public transactions and may receive private order flow from wallets, trading firms, applications, or searchers. It tests combinations of transactions, includes valid bundles, accounts for gas limits and protocol rules, and estimates how much ETH it can pay the proposer while retaining a profit. That informational advantage is one reason specialist builders have become important.

Relays sit between builders and proposers. A relay receives candidate blocks and bids from builders, validates important details, and forwards the best available blinded bids to MEV-Boost users. When a proposer selects and signs a blinded block, the relay releases the full execution payload so the proposer can publish it. This pipeline separates block construction from block publication, but the separation is implemented largely outside Ethereum’s core protocol rather than enforced entirely on-chain.

What validators actually bid for, and what they receive

A frequent misunderstanding is that validators bid for blocks in the PBS auction. Normally, they do not. The selected validator has a scarce asset already: the right to propose a block in that slot. Builders are the ones bidding for access to that opportunity. The validator compares offers, typically using MEV-Boost and relay responses, then selects a bid that appears most valuable and valid.

The builder’s payment is generally directed to the proposer’s fee recipient address in the block. The quoted amount can include ordinary priority fees plus value captured through arbitrage and other MEV strategies. A higher advertised bid is not automatically better if delivery fails, the relay is unavailable, or the block proves invalid. In practice, validator software and relay reputation matter alongside the headline value.

For an individual staker, this arrangement can improve expected rewards relative to locally building every block. That is why MEV-Boost became widely adopted after the Merge and developed into the dominant relay and builder market for many Ethereum validators. Still, increased yield is compensation for dependence on an external market. It is not a guaranteed return, and a staker should distinguish historical reward data from future outcomes.

Why a few builders and relays can matter so much

Ethereum may have many validators, but block building can be much more concentrated. Large builders benefit from private transaction flow, sophisticated infrastructure, searcher relationships, fast simulations, and capital. Those advantages can compound: better order flow produces stronger bids, stronger bids win more blocks, and winning more blocks can attract more order flow. A few builders can therefore account for a substantial share of blocks during some periods.

Relays also create concentration pressure. They are trusted to screen builder submissions, select bids, and deliver payloads at the right moment. Validators can connect to several relays, and the ecosystem has both regulated and non-regulated operators, but broad reliance on a small group still creates correlated failure points. A technical outage, policy change, attack, or legal demand affecting major relays can have network-wide consequences.

This is the political economy behind the word decentralized. Ethereum’s consensus protocol distributes the authority to attest and propose across many validators, yet the commercially valuable job of arranging transactions may be performed by far fewer firms. The chain can continue operating while this market becomes concentrated, but users should not confuse continued block production with a solved decentralization problem. Ethereum validator economics and transaction ordering are linked more closely than a simple validator count suggests.

OFAC censorship and the limits of relay policies

Censorship became a prominent concern after the United States Treasury’s Office of Foreign Assets Control, or OFAC, sanctioned Tornado Cash addresses in 2022. Some relays and builders chose to exclude transactions involving sanctioned addresses from blocks they built or relayed. When a large share of proposed blocks followed those policies, affected transactions could wait longer and the network appeared less permissionless in practice.

It is important to separate temporary filtering from permanent protocol-level censorship. If at least some builders, relays, and proposers are willing to include a valid transaction, it can still reach Ethereum. However, a transaction that is technically possible but consistently delayed by dominant infrastructure is not receiving the same practical access as other transactions. The distinction matters most during periods of market stress, legal pressure, or high congestion.

Relay operators have responded differently over time. Some have applied compliance filters, some have adopted more permissive policies, and some validators connect to multiple relays to avoid reliance on a single policy. Those choices reduce but do not remove the risk. Validators and users should treat relay policy as a changing operational fact, not assume every part of the block-building supply chain shares Ethereum’s base-layer neutrality.

What preconfirmations and the roadmap beyond PBS may change

Today’s MEV-Boost setup is often described as out-of-protocol PBS. Ethereum’s consensus rules select the proposer, while the builder auction and relay workflow happen through external software and market conventions. Researchers have explored enshrined PBS, or ePBS, which would move more of the separation process into Ethereum’s protocol. The goal is to reduce dependence on trusted relays while preserving the benefits of specialist block building.

Preconfirmations are another developing idea. A preconfirmation is an early promise that a transaction will be included or ordered in a certain way before the final Ethereum block is published. This could improve user experience for trading and payments, but it also creates a new market for credible promises. Who can make the promise, what collateral backs it, and what happens when they fail are design questions with real consequences.

Possible designs involve proposers, builders, validators, or separate sequencing services. Each option may improve speed or certainty for some users while shifting power toward operators with reliable infrastructure and valuable order flow. There is no finished roadmap that guarantees a more decentralized outcome. The useful question is not whether PBS, ePBS, or preconfirmations are inherently good, but which trust assumptions and failure modes each design moves into view.

Practical implications for ETH holders, users, and stakers

ETH holders do not need to operate MEV-Boost to use Ethereum, but they should understand why a transaction’s ordering may not match the order in which it was broadcast. For swaps and liquidations, use settings that limit the price you will accept, such as slippage controls where available. Private transaction submission can reduce exposure to public-mempool attacks in some cases, but it introduces trust in the private endpoint and does not guarantee a favorable execution.

Solo stakers considering MEV-Boost should start with official client and relay documentation, understand how their validator client, consensus client, execution client, and MEV-Boost process interact, and monitor missed proposals. Use more than one reputable relay only after understanding the operational trade-offs. Do not treat a social-media relay list or an advertised reward figure as due diligence. Staking decisions involve technical, market, counterparty, and possible slashing risks, not just APY.

For readers evaluating Ethereum’s decentralization, track builder concentration, relay market share, censorship behavior, missed-slot events, and protocol research rather than relying on a single metric. A large validator set is meaningful, but it does not answer who sees transactions first or who determines their order. How MEV affects crypto users is often more useful context than headline claims about network neutrality.

Read Ethereum block-building news critically

PBS, MEV-Boost, relay policy, and preconfirmation research move quickly, and manually following every builder outage, censorship debate, and Ethereum upgrade proposal is difficult. Zippfeed surfaces Ethereum and ETH headlines with bullish, neutral, or bearish sentiment scoring plus an importance rating, helping you separate a meaningful change in block-building infrastructure from routine market noise before forming your own view.