Summary

The EF Mandate is a foundational document articulating the Ethereum Foundation’s purpose, principles, and self-conception. It provides the philosophical grounding for CROPS and the Zero Option — the core values that guide protocol development decisions.

Core Thesis

Ethereum exists to provide two things simultaneously:

  1. Self-sovereign computation: users have final say over their own computation, data, assets, and identities
  2. Coordination without coercion: the ability to coordinate at scale without violating others’ sovereignty

No other infrastructure achieves both. Local computation (running apps on your own machine) provides self-sovereignty without coordination. Centralized platforms provide coordination without self-sovereignty. Ethereum is specifically valuable in the overlap.

Key Principles

Ethereum as Liberatory Technology

  • Not just freedom from specific bad actors, but from “attempts to order reality itself in a way that leaves no alternative”
  • The protocol should have no alternative-free lock-ins
  • Every layer should preserve the user’s right to exit (“the Zero Option” in the ethereum-values wiki page)

EF’s Self-Description

  • “Not the parent, owner, or ruler of Ethereum”
  • Role: “coordinate, provide substrate, offer context that helps anyone who shares our purpose work together”
  • Explicit rejection of centralizing bottleneck role
  • “The Foundation exists to ensure Ethereum becomes, and stays, a decentralized and resilient civilizational foundational infrastructure”

The “Walkaway Test”

Ethereum should be able to pass the walkaway test: the protocol and core application layers should become robust and trustless enough to continue functioning even if the EF and today’s core developers disappeared tomorrow.

This is the most concrete statement of EF’s view of its own relevance — it should make itself unnecessary.

Financial Independence

The EF explicitly rejects accepting “flows of value” even when framed as reasonable rewards or alignment incentives: “These are slippery slopes to arbitrary extraction and insidious capture.” Enduring assets: legitimacy and virtue.

Connection to CROPS

The CROPS mandate (Censorship Resistance, Responsibility/Open Source, Privacy, Security) in the Ethereum”s Values: Zero Option, CROPS, and the Right to Quit wiki page operationalizes the more abstract principles of the EF Mandate:

  • CROPS lists specific technical properties
  • The EF Mandate explains why those properties matter at a civilizational level

Relationship to MEV and Protocol Design

The EF Mandate’s “no alternative-free lock-ins” principle directly addresses MEV concerns:

  • If all relays/builders censor, and local builds are uncompetitive, users are locked in → violates the mandate
  • ePBS, FOCIL, and encrypted mempools are not just technical improvements — they are implementations of the mandate’s requirements
  • The “400% PBS premium” must not come at the cost of censorship capability at the relay layer