Understanding Proposer-Builder Separation
Proposer-Builder Separation is a blockchain architecture design that divides the responsibilities of creating blocks and proposing them to the network. This division helps prevent validator centralization by mitigating the centralizing effects of Maximal Extractable Value.
Traditional blockchain networks rely on a single entity to create new blocks. Whether a miner in a proof-of-work system or a validator in a proof-of-stake system, this participant selects transactions from the mempool, determines their order, and proposes the final block to the network. The rise of decentralized finance (DeFi) introduced complex economic incentives that altered block production.
The ability to extract value by reordering, including, or excluding transactions created a highly competitive environment. Sophisticated participants began using advanced algorithms to maximize their profits, giving large operations a structural advantage. Proposer-Builder Separation introduces a structural change to consensus mechanisms to address these imbalances. By dividing block production into two distinct roles, this architectural shift maintains network decentralization, levels the playing field for participants, and enables future scalability upgrades.
What Is Proposer-Builder Separation?
Proposer-Builder Separation is a design model that alters how blockchains generate and validate blocks. Historically, a single validator selected transactions from the public mempool, ordered them, executed them to compute the new state, and proposed the resulting block to the rest of the network.
This unified role became problematic with the emergence of Maximal Extractable Value (MEV). MEV refers to the maximum value that can be extracted from block production in excess of standard block rewards and gas fees. Extracting MEV requires specialized software, high-speed infrastructure, and continuous algorithmic optimization. In a traditional model, validators who invest heavily in MEV extraction consistently earn greater rewards than solo or less sophisticated validators. Over time, this dynamic forces smaller validators to either pool their resources with large entities or exit the network entirely, leading to severe centralization at the consensus layer.
Proposer-Builder Separation solves this by decoupling the block creation process into two independent functions. One group of participants focuses entirely on the complex task of sequencing transactions to maximize value. The other group selects and submits the most profitable block to the network. The primary goal of this separation is to strip the centralizing forces of MEV away from the consensus layer. By outsourcing the computationally intensive work of block construction, the network ensures that any validator can participate and earn proportional rewards without needing to run specialized MEV extraction software.
How Does PBS Work?
The mechanics of Proposer-Builder Separation rely on a distinct division of labor between two primary actors: builders and proposers. Builders are specialized, resource-intensive network participants. They monitor the public mempool and private transaction channels, simulate thousands of different transaction orderings, and construct the most profitable block possible. Once a builder constructs a block, they submit a bid representing the value they are willing to pay the network for the right to have their block included in the chain.
Proposers are the standard validators responsible for consensus. Instead of building blocks themselves, proposers simply evaluate the bids submitted by the various builders. The proposer selects the block with the highest bid, signs it, and broadcasts it to the network. The proposer receives the bid amount as their reward. This ensures they capture the majority of the MEV generated by the builder without having to execute complex strategies themselves.
To ensure this relationship functions securely, the system uses a blind auction mechanism and commit-reveal schemes. If proposers could see the contents of a builder's block before committing to it, a malicious proposer could copy the transaction order, replace the builder's payout address with their own, and steal the MEV strategy. To prevent this, builders send their blocks to a relay. The relay verifies the block's validity and forwards only the block header and the bid amount to the proposer. The proposer must cryptographically sign this header, committing to propose that exact block without seeing the underlying transactions. Once the proposer's signature is registered, the relay reveals the full block body to the network, finalizing the process securely.
Types of PBS and Implementations
The implementation of Proposer-Builder Separation currently exists in two primary forms: out-of-protocol and in-protocol. Out-of-protocol separation is the model actively used on existing infrastructure today, most notably on the Ethereum network. This version is achieved through third-party software sidecars, such as MEV-Boost, which validators run alongside their standard consensus clients.
In the out-of-protocol model, the network relies on independent relays to act as trusted intermediaries between builders and proposers. These relays hold the block bodies and ensure that builders pay the proposers as promised. While this system successfully democratizes MEV rewards across the validator set, it introduces a reliance on centralized relay operators. If a relay goes offline or acts maliciously, it can disrupt block production or compromise the blind auction process.
In-protocol separation, often referred to as Enshrined PBS (ePBS), is a proposed future upgrade that integrates the separation directly into the blockchain's core consensus rules. Enshrined PBS aims to eliminate the need for trusted third-party relays entirely. Instead of relying on external software to manage the blind auction and commit-reveal mechanics, the blockchain protocol itself enforces the rules. Builders would submit their bids and cryptographic commitments directly to the network, and the protocol would guarantee the delivery of the block body and the payment to the proposer. This transition from external middleware to core protocol infrastructure moves the network toward a fully trustless block production pipeline.
Benefits of Proposer-Builder Separation
The most immediate benefit of Proposer-Builder Separation is the democratization of MEV rewards, which directly preserves validator decentralization. In a unified model, large staking pools and institutional validators possess the capital to develop proprietary MEV extraction algorithms, allowing them to offer greater rewards to delegators and capture a disproportionate share of the network. By separating the roles, a solo validator running standard hardware at home has access to the exact same MEV opportunities as the largest institutional pool. The validator simply accepts the highest bid from the open builder market, effectively leveling the playing field and keeping the consensus layer decentralized.
Beyond decentralization, this separation paves the way for critical future scalability upgrades. As blockchain networks aim to process more transactions per second, the computational burden of executing and verifying blocks increases. Because builders are already specialized entities running high-performance hardware, the network can safely shift the heavy lifting of data processing to them.
This dynamic is essential for concepts like statelessness and data availability sampling. In a stateless network, validators would not need to store the entire blockchain state to verify blocks, dramatically lowering the hardware requirements for participating in consensus. Similarly, upgrades like danksharding require blocks to contain large amounts of data to support layer-2 rollups. Expecting standard validators to construct and process these massive blocks would lead to immediate centralization. By designating builders to handle the intensive data bandwidth, the network can scale its throughput exponentially while keeping the validator set lightweight and accessible.
Challenges and Trade-Offs
While Proposer-Builder Separation addresses validator centralization, it shifts centralizing forces to the builder layer. The builder market is naturally driven by economies of scale and exclusive access to transaction flow. Builders who consistently win auctions attract more private transaction order flow from users and applications, which in turn allows them to build more profitable blocks and win even more auctions. This feedback loop can quickly lead to an oligopoly where a small handful of optimized builders construct the vast majority of all blocks on the network.
This builder centralization introduces concerns regarding transaction censorship. If a few entities control block production, they possess the power to exclude specific transactions from the blockchain. For example, builders operating in specific jurisdictions might choose to censor transactions associated with sanctioned addresses to maintain regulatory compliance. If these builders dominate the market, users interacting with censored addresses could face severe delays in getting their transactions confirmed.
Additionally, implementing Enshrined PBS presents technical complexities. Moving the blind auction and commit-reveal mechanics into the core protocol requires careful engineering to avoid introducing new attack vectors. Designing a system where the protocol can trustlessly guarantee that a builder will reveal a block body after a proposer has committed to it, without slowing down the network's block times or causing missed slots, requires fundamental changes to how consensus algorithms operate.
The Role of Chainlink in MEV Mitigation
Proposer-Builder Separation effectively addresses the centralizing impact of MEV on the consensus layer, but it does not eliminate the existence of MEV or protect end users from predatory transaction ordering. Malicious MEV strategies, such as frontrunning and sandwich attacks, still occur within the blocks constructed by builders, resulting in worse execution prices for users interacting with DeFi protocols.
The Chainlink platform complements the structural solutions of PBS by addressing MEV at the application and oracle layer. Operating through the Chainlink data standard, decentralized oracle networks provide secure Data Feeds and low-latency Data Streams that ensure accurate, high-frequency pricing for smart contracts. By delivering precise market data onchain, this standard reduces the arbitrage opportunities that builders exploit during periods of high volatility, limiting the total surface area for toxic MEV extraction. Additionally, protocols can use mechanisms to internalize and recapture MEV as an additional revenue source.
Developers can use the Chainlink Runtime Environment (CRE) to build custom execution logic and orchestrate complex workflows that include fair transaction ordering mechanisms. Using CRE, developers can design systems where transactions are sequenced securely before they enter the public mempool, ensuring that user orders are processed fairly and cannot be exploited by specialized builders. This approach protects users at the point of execution. While Proposer-Builder Separation ensures that the underlying blockchain remains decentralized and scalable, the Chainlink platform ensures that the applications built on top of it remain secure, fair, and resistant to value extraction.









