Credible Neutrality
Credible neutrality is a design principle for protocols and platforms that ensures no participant receives preferential treatment.
Key Takeaways
- Credible neutrality means a mechanism's design makes it obvious that no participant receives preferential treatment: the fairness must be transparent enough for anyone to verify, not just promised by the operator.
- Violations include MEV extraction, front-running, validator censorship, and stablecoin address freezes: any time a privileged actor can selectively include, exclude, or reorder participants' transactions.
- Restoring neutrality is an active area of protocol design: Ethereum's proposer-builder separation, inclusion lists, and encrypted mempools each address a different dimension of the problem.
What Is Credible Neutrality?
Credible neutrality is a design principle for protocols, platforms, and governance mechanisms. A mechanism is credibly neutral when its rules make it easy for any observer to see that it does not discriminate for or against specific people. The concept was formalized by Vitalik Buterin in a January 2020 essay, where he argued that shared systems need more than just fairness: they need fairness that is visible and verifiable, even to a relatively uninformed observer.
The distinction between neutrality and credible neutrality matters. A system might be neutral in practice (no one has been treated unfairly yet) without being credibly neutral (anyone could look at the rules and confirm fairness is guaranteed). A lottery where a single committee picks winners might happen to be fair, but it is not credibly neutral because participants cannot verify the absence of bias. A lottery where winners are selected by a published algorithm using a public random seed is credibly neutral: the design itself proves fairness.
In blockchain systems, credible neutrality is closely related to censorship resistance and permissionlessness. A protocol that anyone can use but where certain actors can selectively delay, reorder, or exclude transactions has permissionless access without credible neutrality.
How It Works
Buterin proposed four properties that credibly neutral mechanisms should satisfy:
- Do not write specific people or predetermined outcomes into the mechanism. A rule like "anyone who mines a valid block receives the block reward" qualifies. A rule like "Bob receives 1,000 coins" does not.
- Make execution open source and publicly verifiable. Participants should be able to audit the mechanism's code and confirm it matches its claims.
- Keep the mechanism simple. Complexity creates hiding places for bias that participants cannot easily detect.
- Do not change the mechanism frequently. Every change resets the "veil of ignorance": participants must re-evaluate whether the new rules are still fair.
Neutrality in Transaction Ordering
One of the most consequential areas where credible neutrality breaks down is transaction ordering. In both Bitcoin and Ethereum, whoever constructs a block has discretion over which transactions to include and in what order. This discretion creates opportunities for maximal extractable value (MEV): profits captured by reordering, inserting, or censoring transactions.
Common MEV strategies that violate credible neutrality include:
- Front-running: observing a pending transaction and placing a competing transaction ahead of it to capture the price movement
- Sandwich attacks: placing orders both before and after a target trade to extract value from the price impact
- Backrunning: placing a transaction immediately after a target to capture arbitrage opportunities it creates
- Selective censorship: deliberately excluding certain transactions from blocks, either for profit or under regulatory pressure
Ethereum's Approach
Ethereum has developed several mechanisms to restore credible neutrality in block production:
- Proposer-builder separation (PBS): separates the roles of building blocks (selecting and ordering transactions) and proposing blocks (committing them to the chain). This prevents validators from directly extracting MEV from their own blocks. The current implementation relies on external relays like MEV-Boost, but enshrined PBS (ePBS) aims to bring this separation into the protocol itself, removing relays as trusted intermediaries.
- Inclusion lists: proposals like EIP-7805 (FOCIL) would allow a committee of validators to specify transactions that must be included in a block. Builders retain ordering discretion but cannot censor specific transactions. This directly addresses the censorship dimension of neutrality.
- Encrypted mempools: proposals where transactions are encrypted until they are committed to a block. Builders cannot see transaction content and therefore cannot make inclusion decisions based on it. This addresses front-running and content-based censorship simultaneously.
These three mechanisms are complementary: PBS limits who can reorder, inclusion lists force inclusion, and encrypted mempools prevent content-based discrimination. For a deeper analysis of how these interact, see MEV, PBS, and Validator Economics.
Bitcoin's Model
Bitcoin's architecture provides a simpler form of credible neutrality. Miners receive nearly all their transactions from the public peer-to-peer network, and Bitcoin's script language is not expressive enough to create the complex DeFi interactions that generate most MEV on Ethereum. Without automated market makers, lending protocols, or sandwich-vulnerable swap transactions, the economic incentive for transaction reordering is much smaller.
However, Bitcoin's neutrality is not absolute. Large mining pools like Marathon Digital operate private transaction submission services (such as Slipstream) that allow users to submit transactions directly to the pool, bypassing the public mempool. If certain miners consistently earned higher revenue per hash through private order flow, it could undermine the assumption that all miners compete on equal terms. The development of Stratum v2 aims to return block template construction to individual miners, reducing pool operators' discretion over transaction selection.
Use Cases
Protocol Governance
Credible neutrality applies beyond transaction ordering to how protocols are governed and upgraded. A governance process where a small committee can unilaterally change rules violates credible neutrality even if the committee acts fairly. Transparent on-chain governance with publicly visible voting and predefined upgrade paths is closer to the ideal: participants can verify that no insider advantage exists.
Layer 2 Networks
Layer 2 scaling solutions face their own neutrality challenges. Most rollups currently rely on a single sequencer that determines transaction ordering, creating a concentrated point of discretion. Decentralized sequencing, shared sequencers, and based rollups (which delegate sequencing to the Layer 1) are all approaches to distributing this power.
Bitcoin Layer 2 protocols like Spark take a different approach. By using a VTXO-based model with FROST threshold signatures, Spark ensures that users retain the ability to unilaterally exit to the base layer without needing operator cooperation. This exit guarantee is a key component of credible neutrality: even if the operator misbehaves, users are not trapped.
Payment Networks and Stablecoins
Payment networks and stablecoin issuers face a fundamental tension with credible neutrality. Issuers like Circle (USDC) and Tether (USDT) maintain the technical ability to freeze or blacklist specific addresses. In the United States, the GENIUS Act requires permitted stablecoin issuers to maintain the capability to seize, freeze, or burn tokens on lawful orders.
This creates a design tradeoff: legal redeemability (the guarantee that tokens can be exchanged for underlying reserves) may require the issuer to maintain freeze capabilities, which inherently violates credible neutrality. A stablecoin that cannot freeze addresses may be more neutral but could lose its legal standing as a redeemable instrument. For more on how these mechanisms work in practice, see the research on stablecoin blacklisting and sanctions mechanics.
Risks and Considerations
Neutrality vs. Compliance
Pure credible neutrality can conflict with legal requirements. Regulators may require transaction screening, address blocking, or identity verification that inherently treats some participants differently. The challenge is finding designs that satisfy compliance obligations at the edges (on-ramps, off-ramps, application layer) while preserving neutrality at the protocol layer.
Neutrality Does Not Guarantee Fairness
A credibly neutral mechanism treats everyone the same by its rules, but those rules can still produce unequal outcomes. A fee market where the highest bidder wins block space is credibly neutral (the rule applies equally to everyone) but systematically favors well-capitalized participants. Neutrality is a necessary condition for fair infrastructure, not a sufficient one.
Complexity of Enforcement
The mechanisms designed to restore neutrality (PBS, inclusion lists, encrypted mempools) add significant protocol complexity. Each new component introduces its own assumptions, attack surfaces, and potential failure modes. A 2025 report from the Proof of Stake Alliance warned that inclusion lists could expose validators to stricter regulatory scrutiny, potentially undermining the very neutrality they aim to protect. Simpler protocols, as Buterin noted in his original essay, are easier to audit for neutrality.
Centralization Pressure
Even in credibly neutral systems, economic forces can create centralization. In Ethereum's current MEV supply chain, a small number of builders construct the majority of blocks. While the rules are neutral, the market outcome concentrates power. Monitoring decentralization metrics and designing incentives that resist winner-take-all dynamics remain open challenges.
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.