EF Mandate explained

The "EF Mandate", published by the Ethereum Foundation on March 13, 2026, is a document in which the Foundation states why it exists, what it does, and what it does not do. The Foundation blog introduced it as a constitution, a declaration and an operating guideline, and the full text was recorded onchain. The document says the Foundation is a steward rather than the owner of Ethereum and treats a decline in its own influence as success, so it reads as a reference point for judging the Foundation's future decisions.

Original · Foundation blog · published 2026-03-13

Key ideas

I. Ethereum (ETHEREUM)

The document begins by saying Ethereum was born from a dream of freedom. It sees Ethereum's value in domains that need both self-sovereign computation, where users keep control of their own computation to the end, and the ability to cooperate at scale without harming others' sovereignty. The first application is money, and Ethereum aims to be humanity's common computing foundation, in other words a world computer, that anyone can keep using without trust or permission. The Foundation states that it exists to make Ethereum robust enough to hold this role.

II. The Foundation's role (OUR ROLE)

The Foundation introduces itself as Ethereum's first steward, while drawing a line that it is neither Ethereum itself nor its owner. It explains that its role is to coordinate people with the same purpose so they can work together, and to provide foundations and context, without creating a central bottleneck or a monoculture. The final goal is to pass the walkaway test, in which Ethereum keeps running even if the Foundation disappears, and the measure of performance is Ethereum's resilience, not profit or organizational growth. This section also contains the point that the document is above all a practical guide for Foundation members, and an admission that the Foundation has not always done well in the past.

III. The Foundation's mission (OUR MANDATE)

The Foundation's mission has two branches. The first is to build and protect Ethereum as a decentralized, resilient, self-sovereign tool. For this, it treats CROPS, which bundles censorship resistance, open source and free, privacy, and security, as a premise that no priority can replace. The second is to provide self-sovereignty, in a guaranteed form and at the scale they want, to users who want it. The document adds that this mission is written with a thousand-year horizon, and that because principles tend to flow downhill like water, it starts from the highest standard.

IV. Principles of action (PRINCIPLES FOR ACTION)

The mission stands on two pillars, technology and society, with four principles in each pillar. The technology pillar spells out the four CROPS properties one by one, and the society pillar covers the attitude with which the Foundation works and whom it partners with. The document insists that protocol work, community support and decision-making must all come from these two pillars, and that CROPS is not up for negotiation. At the end of the technology pillar it brings up the walkaway test again, and concludes that minimizing intermediaries and structural decentralization are the path to it.

V. How it works (CARRYING OUT THE WORK)

The Foundation's way of operating is summarized as subtraction for resilience. It holds that Ethereum is stronger the more it runs without the Foundation's guidance, and prefers work that makes the Foundation less necessary over time. It then lists nine things the Foundation does not do, and offers criteria for choosing between an incremental approach and a CROPS-native approach, given that CROPS is not yet the default. In confrontations, it says it chooses to build open-source defensive tools that anyone can use rather than to state opinions on specific conflicts.

VI. Resolving hard judgments (RESOLVING QUANDARIES)

The document holds that although details cannot be predicted over the next thousand years, the structure of conflict repeats, like the shape of a valley carved by a river. It therefore presents, with examples, five tensions around Ethereum that will continue until the mission ends. They are the choice between the path that can ship quickly and the path that removes points of concentrated influence, one layer versus the whole system, user protection versus user agency, intermediation versus disintermediation, and a polished team versus a team with substance. All five cases are tied together by the same standard: prefer what will not become a bottleneck tomorrow over what works today.

VII. The future (THE FUTURE)

The document diagnoses that people have long been pushed to believe there are only two bad options. One is to accept rule by great sovereigns such as states, corporate oligarchies, or grand ideologies. The other is to smash everything without principle, turn cynical, or side with whoever is advantageous. Ethereum rejects the idea that there is no alternative, and says it is not a weapon for either side but a tool for people to step out of power struggles and build, for themselves, a refuge where they neither oppress nor are oppressed. The Foundation takes responsibility for keeping the path to that refuge open, and says the front line Ethereum holds is protecting permissionless computation and communication with maximal privacy and user agency.

VIII. Closing words (CLOSING)

The document stresses again that the Foundation's job is neither to take over markets, companies or states nor to help them extract. Its purpose is to free individuals from capture, strengthen freedom of association, and provide infrastructure that gives a voice to forms of cooperation and community that existing hierarchies do not recognize. It describes Ethereum as a device that keeps you from being "rugged" by others, society, governments, companies and AI, and even by your own mistakes. It ends with a pledge not to let the torch of freedom go out until it is handed on to the next generation as it was received, and a declaration that it is building a machine of freedom for a thousand years.

Technical principles

Social principles

How hard calls get made

When two technically plausible paths compete, which one is chosen?

It chooses the one that removes points of concentrated influence, not the one that can ship faster. A design that defaults to permissionless p2p propagation from the start, rather than a private relay for trusted partners only, is given as an example.

How is a proposal viewed if it preserves CROPS at one layer but creates a bottleneck in another layer?

It weighs the impact on the whole system, rejects proposals that shift a bottleneck to another layer, and welcomes proposals that expand protocol features to remove bottlenecks at other layers. However, protocol changes are hard to reverse, so a much higher bar applies.

To protect users in a hostile environment, who should block what?

Instead of opaque 'safe modes' that are on by default or AI that reports on users in secret, it supports defensive tools with transparent rules that users can choose and turn off.

What is done when an intermediary sits in an important use case?

It lowers barriers to entry for intermediaries and widens competition, while always building a path that does not need an intermediary. For an app that needs identity verification, it first looks for a design that proves only the properties actually needed, rather than the easy approach of wrapping a government ID in a zero-knowledge proof.

What is used to judge which teams to support?

It looks at the tradeoffs a team repeatedly chooses and its actual design, rather than polished language, reputation, or peer endorsement. The first version need not be finished; it is enough that it is built in public and other teams can pick it up.

Glossary