PBS Governance is the formal and informal system for making collective decisions about the Proposer-Builder Separation (PBS) protocol. This includes establishing the technical specifications (like those for MEV-Boost), updating relay and builder software, managing the builder registry, and setting policies for censorship resistance and validator obligations. Unlike core protocol upgrades managed by Ethereum Improvement Proposals (EIPs), PBS governance often operates through a combination of client developer coordination, relay operator consensus, and broader community signaling.
PBS Governance
What is PBS Governance?
PBS Governance refers to the evolving set of rules, processes, and community-led mechanisms that oversee and manage the Proposer-Builder Separation (PBS) framework within a blockchain ecosystem, primarily Ethereum.
A central challenge in PBS governance is balancing decentralization with efficiency. Key entities involved are relay operators, who curate the builder marketplace and must be trusted for liveness and censorship properties, and block builders, whose competitive landscape is governed by economic rules. Governance decisions here directly impact validator rewards (through MEV extraction), network latency, and the resilience of the chain against centralization risks. The community uses forums, research calls, and client implementations to debate and steer these components.
The governance process is critical for the in-protocol PBS (ePBS) roadmap, where today's off-chain coordination via MEV-Boost will be formalized into the core consensus layer. Current governance focuses on proposer commitments, such as the builder-registration API and the potential for inclusion lists, which are rules validators can enforce to guarantee transaction inclusion. These mechanisms are debated and refined through the governance process to ensure the final protocol design aligns with Ethereum's core values of neutrality and permissionlessness.
How PBS Governance Works
Proposer-Builder Separation (PBS) governance refers to the mechanisms and processes that determine how the roles, responsibilities, and economic incentives are structured and updated within a PBS ecosystem.
PBS governance is distinct from the core blockchain protocol's governance and focuses specifically on the builder-proposer marketplace. Its primary function is to define the rules of interaction between block proposers (validators) and block builders (specialized entities), including how builders bid for block space, how proposers select winning bids, and how the mev-boost relay network or similar infrastructure is managed. This governance layer ensures the marketplace remains competitive, transparent, and resistant to centralization or manipulation.
Key governance decisions include setting parameters for the builder registry, establishing slashing conditions for malicious builders, defining the requirements for relay operators, and potentially overseeing the development of in-protocol PBS implementations. These decisions are typically made by a consortium of stakeholders, which may include core protocol developers, major validator pools, builder representatives, and researchers, often through an Ethereum Improvement Proposal (EIP) process or dedicated working groups like the Ethereum Protocol Fellowship.
A central tension in PBS governance is balancing decentralization with efficiency. Overly restrictive rules can stifle builder innovation and reduce maximal extractable value (MEV) redistribution to validators, while overly permissive rules could lead to builder cartels and censorship. Governance processes must also adapt to emerging threats, such as the potential for time-bandit attacks or builder collusion, requiring continuous research and iterative protocol upgrades to maintain system integrity and fairness for all participants.
Key Governance Areas in PBS
Governance in Proposer-Builder Separation (PBS) focuses on managing the critical interfaces and incentives between network participants to ensure decentralization, censorship resistance, and efficient block production.
Builder Registration & Reputation
Governance defines the rules for builder registration on the network, including staking requirements, slashing conditions, and reputation systems. This ensures builders are credible and accountable. Key mechanisms include:
- Minimum viable issuance (MVI) or stake requirements.
- Slashing for malicious behavior like withholding blocks.
- Reputation scoring based on past performance and reliability.
Relay Governance & Neutrality
Relays are trusted intermediaries that facilitate communication between proposers and builders. Governance must enforce relay neutrality and prevent censorship. Key areas include:
- Relay operator requirements and attestation policies.
- Censorship resistance monitoring and slashing.
- Data availability and block disclosure rules.
- Managing the relay inclusion list to prevent builder exclusion.
Auction Mechanism Design
Governance defines the auction rules for block space, balancing efficiency with fairness. This includes:
- Payment structure (e.g., priority fees, MEV burn).
- Bid commitment and reveal schemes to prevent front-running.
- Block validity conditions that builders must meet.
- Rules for handling out-of-slot execution and re-orgs.
MEV Distribution & Burn
A core governance challenge is managing the distribution of Maximal Extractable Value (MEV). Policies determine how value flows between builders, proposers, and the protocol itself. Key decisions involve:
- The MEV burn percentage sent to the protocol treasury or burned.
- Proposer payment guarantees and minimum thresholds.
- Mitigating proposer centralization risks from outsized MEV rewards.
Protocol Upgrades & Fork Coordination
PBS introduces complex protocol changes that require careful coordination. Governance manages the upgrade path for:
- In-protocol PBS (ePBS) implementation and migration.
- Consensus layer and execution layer changes.
- Fork choice rule adjustments to account for builder behavior.
- Backward compatibility and client implementation timelines.
Censorship Resistance Enforcement
Governance must define and enforce anti-censorship measures to prevent centralized builders or relays from filtering transactions. This is often managed through:
- Proposer commitments to include certain transactions.
- Censorship detection tools and slashing conditions.
- Inclusion lists that proposers can force into a block.
- Monitoring builder centralization metrics and market share.
Who Governs PBS? Key Entities
Proposer-Builder Separation (PBS) is a multi-party system. Governance is not centralized but distributed across distinct protocol roles, each with specific responsibilities and incentives.
User & Developer Influence
While not direct governors, users and developers exert soft governance through economic choices:
- Users can use privacy-preserving RPCs (e.g., Flashbots Protect) to submit transactions directly to builders, bypassing the public mempool.
- DApp Developers can implement MEV-aware design (e.g., CoW Swap, SUAVE) to mitigate negative externalities.
- Stakers choose which relay and builder policies to support via their validator client configuration, voting with their stake.
Regulatory & Legal Frameworks
External legal systems influence PBS governance, particularly around censorship. Key pressures include:
- OFAC Sanctions Compliance: Some U.S.-based relays and builders filter transactions, leading to censorship concerns.
- Consumer Protection Laws: May target MEV extraction practices deemed exploitative.
- Anti-Trust Scrutiny: Builder dominance could attract regulatory attention. These frameworks create constraints that relays and builders often operationalize through their inclusion policies, affecting transaction flow on-chain.
Comparison of PBS Governance Models
Key architectural and governance trade-offs between different approaches to implementing Proposer-Builder Separation (PBS) in blockchain protocols.
| Governance Feature | Enshrined PBS | Permissioned PBS | Permissionless PBS |
|---|---|---|---|
Protocol-Level Enforcement | |||
Builder Registration Required | |||
Censorship Resistance Guarantee | High (Protocol) | Medium (Trusted Set) | Variable (Market) |
Governance Complexity | High (Hard Fork) | Medium (Committee) | Low (Code is Law) |
Builder Collusion Risk | Low | High | Medium |
Time to Finality Impact | < 1 slot | 1-2 slots | 2+ slots |
MEV Redistribution | Protocol-Controlled | Builder-Dictated | Market-Dictated |
Primary Development Stage | Research | Live (e.g., MEV-Boost) | Experimental |
Evolution of PBS Governance
The governance of Proposer-Builder Separation (PBS) has evolved from a theoretical concept into a critical, multi-layered framework for managing the decentralized auction of block production rights on Ethereum.
The evolution of PBS governance traces the development of the rules, mechanisms, and stakeholder roles that oversee the market where block builders compete to construct blocks and proposers (validators) select the most profitable one. Initially proposed to mitigate Maximal Extractable Value (MEV) centralization risks, its governance has progressed through distinct phases: from off-chain, trusted relay-based models to the ongoing development of in-protocol PBS (ePBS), which aims to enshrine the auction logic directly within Ethereum's consensus layer. This shift fundamentally changes who controls the critical auction mechanism and how its parameters are updated.
Early PBS implementation relied heavily on off-chain governance by relay operators. Centralized relays like Flashbots acted as trusted intermediaries, setting rules for builder registration, censorship resistance (e.g., inclusion lists), and data transparency. This period was characterized by rapid iteration but also centralization risks, as relay operators held significant power over market access and rules. The governance of this system was informal, driven by individual relay policies and community pressure, highlighting the need for a more robust, protocol-native solution.
The current evolutionary direction is toward enshrined PBS (ePBS), which moves the core auction and governance into the Ethereum protocol itself. Key governance questions for ePBS include: Who controls the crList (censorship resistance list) mechanism? How are builder registration and slashing conditions determined? How are protocol parameters like auction fees adjusted? Governance of these elements is intended to fall under Ethereum's existing consensus-layer upgrade process, involving researchers, client developers, and ultimately stakeholder votes via the Ethereum Improvement Proposal (EIP) process, making the system more transparent and decentralized.
A critical governance challenge throughout this evolution is balancing competing interests: proposer welfare (maximizing rewards), builder competition (ensuring a healthy market), censorship resistance (guaranteeing transaction inclusion), and protocol simplicity. Different governance models allocate control over these trade-offs differently. For instance, a proposer-driven model might let the validator choose the crList, while a builder-driven model might assign that duty to the winning builder, each with distinct implications for decentralization and efficiency.
The endpoint of this governance evolution is a stable, decentralized system where the rules of block construction and proposal are as resilient as the blockchain itself. Success means achieving a sustainable equilibrium where MEV is efficiently redistributed without creating new centralization vectors, and where updates to the PBS mechanism are governed by the broad Ethereum community rather than a few off-chain entities. This represents a major step in maturing Ethereum's core economic infrastructure.
Security & Centralization Considerations
PBS fundamentally reconfigures block production roles, creating new trust assumptions and attack surfaces that must be carefully managed to preserve network security and decentralization.
Builder Centralization Risk
The builder role is capital-intensive, favoring specialized entities with access to MEV extraction strategies, low-latency infrastructure, and large capital reserves. This can lead to a small number of dominant builders, creating a centralization bottleneck in block production. Mitigations include decentralized builder networks and inclusion lists to prevent censorship.
Relayer Trust & Censorship
In two-slot PBS, the relayer is a trusted intermediary that receives the builder's block and forwards it to the proposer. This creates a single point of failure for censorship or data withholding. Solutions like trust-minimized relayers using TLSNotary proofs or MEV-Boost+ aim to reduce this trust requirement.
Proposer Collusion & MEV Theft
A malicious proposer could collude with a builder to steal MEV or renege on payment after receiving a block. Enshrined PBS (ePBS) protocols use cryptographic commit-reveal schemes and slashing conditions to enforce builder payments and punish dishonest proposers, securing the economic transaction.
Validator Set Decentralization
PBS preserves validator set decentralization by keeping the role of proposing and attesting to blocks permissionless and accessible. The consensus layer remains separate from the execution layer's builder market. This prevents the consolidation of staking power and block production power into the same entities.
Governance & Protocol Upgrades
Transitioning to an enshrined PBS (ePBS) design requires careful consensus-layer protocol changes. Governance must balance introducing new complexity against the security benefits of removing trusted relayers. Key decisions involve the design of the builder registration mechanism, payment enforcement, and slashing conditions.
Long-Term Censorship Resistance
A centralized builder market could censor transactions (e.g., OFAC-sanctioned addresses). Inclusion lists are a countermeasure, allowing a proposer to mandate specific transactions be included. The long-term security goal is a credibly neutral block production market where censorship is economically disadvantageous.
PBS Governance in Practice
Proposer-Builder Separation (PBS) governance involves distinct roles and mechanisms for managing the relationship between block proposers and specialized builders in a blockchain's block production process.
Builder Registration & Reputation
Builders must register and often stake collateral to participate, establishing a reputational and financial stake in the system. This creates a Sybil-resistance mechanism and a slashing condition for malicious behavior. A public registry allows proposers to verify builder identities and track performance metrics like inclusion rate and bid reliability.
Auction Mechanisms & Commit-Reveal
The core governance layer for PBS is the sealed-bid auction. Builders submit encrypted bids containing the block header and a fee. After the winning bid is selected, a commit-reveal scheme ensures the builder reveals the full block body. This prevents front-running and bid sniping, making the auction trust-minimized. The dominant model is MEV-Boost on Ethereum.
Validator/Proposer Responsibilities
Validators (proposers) are governed by protocol rules to select the highest-value bid from the auction. Their key governance duties are:
- Relay Trust: Choosing a reputable, censorship-resistant relay to run the auction.
- Payload Verification: Validating the block header meets consensus rules before signing.
- Uncle Bandit Risk: Understanding the risk of proposing an empty block if the winning builder withholds the payload.
Relay Governance & Censorship Resistance
Relays are critical trusted intermediaries in current PBS implementations. Their governance is off-chain but vital. Key concerns and mitigations include:
- Censorship Lists: Relays may filter transactions, requiring proposer vigilance.
- Decentralization: Efforts like the Relay Monitor and multiple relay options prevent single points of failure.
- Transparency: Public APIs for bid data and block inclusion are essential for ecosystem oversight.
Enshrined PBS (In-Protocol)
A long-term governance goal is moving PBS into the core protocol. Enshrined PBS would replace off-chain relays with on-chain, cryptoeconomically secured mechanisms. This involves complex protocol changes like:
- Builder stakes slashed for misbehavior.
- On-chain auction contracts.
- Two-slot proposals separating header and body submission. It aims to minimize trust and enhance credible neutrality.
MEV Distribution & Burn
PBS governance directly controls how Maximal Extractable Value (MEV) is distributed. Key models are:
- Proposer Payment: MEV is captured by builders and paid to proposers via bids, redistributing value to stakers.
- MEV Burn: A portion of MEV is destroyed (burned) instead of paid, acting as a deflationary mechanism and reducing validator centralization pressures. Ethereum's EIP-1559 base fee burn is a precursor to this concept.
Frequently Asked Questions (FAQ)
Proposer-Builder Separation (PBS) is a core Ethereum protocol design that separates the roles of block proposal and block construction to improve network efficiency and decentralization. This FAQ addresses common questions about its governance, implementation, and impact.
Proposer-Builder Separation (PBS) is a design paradigm that decouples the role of the block proposer (who chooses the next block) from the block builder (who assembles the block's transactions). It is critically important for mitigating Maximal Extractable Value (MEV) centralization risks and ensuring the long-term decentralization of Ethereum. Without PBS, validators with sophisticated MEV extraction capabilities could outcompete others, leading to validator centralization. PBS allows for a competitive, specialized market of builders while keeping the consensus role of proposers simple and accessible.
Key benefits include:
- Decentralization: Prevents MEV advantages from consolidating block production.
- Efficiency: Enables specialized builders to create more valuable, optimally ordered blocks.
- Simplicity: Reduces the technical burden on individual validators.
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.