The Ethereum Foundation published its mandate, and a lot of people read it as a change of direction. It’s not. It reads that way because it’s the first time the Foundation has written down, in a single place, what Ethereum was always supposed to be. I support the mandate. And I think most of the surrounding noise is either missing the point or defending an arrangement that happened to be comfortable.
The document organizes everything around four properties: censorship resistance, open source (free as in freedom), privacy, and security (CROPS). The mandate treats them as an indivisible whole and as non-negotiable at the base layer, which means no development priority is ever allowed to displace them.
None of that is new.
It’s the reason anyone serious started building on Ethereum in the first place, instead of using a database with extra steps. The core value was never the throughput or the token price. It was that no single actor (a company, a government, the Foundation itself) could revoke the properties you depend on. That’s the whole thesis, and it points at the same decentralized future I keep coming back to. It’s the thing I was drawn to in 2018, and it hasn’t changed since.
What the mandate adds is a written commitment that the Foundation will never trade those properties away. That sounds small but it’s not. An unwritten understanding drifts, and the mandate is honest enough to say so directly: standards tend to flow from high to low, like water, and are far easier to lose than to regain. A vibe drift, but a written mandate can be pointed at.
So when I see the mandate dismissed as the Foundation retreating, or navel-gazing, or choosing ideological purity over growth, I think the criticism has the layers backwards.
A base layer is not a business development department
The loudest specific complaint is that the Foundation has been bad at business development. It hasn’t courted institutions hard enough, hasn’t sold Ethereum to the firms that would bring volume, hasn’t behaved like an organization whose job is adoption. Critics, including former EF researchers, have pointed to the lack of BD as a failure, and the factual core of it is correct. The Foundation has not operated as a sales organization.
But that is the point, not the failure.
The mandate says plainly that the Foundation is not a marketing agency and not a development company. A base layer institution stewards the protocol. It does not drive the commercial activity above it. Those are different jobs, and the mandate’s contribution is to stop pretending they’re the same one.
Think about how the internet actually got built. The people who specified TCP/IP did not run marketing campaigns for the web. The Internet Engineering Task Force (IETF) maintained protocols and got out of the way. Business development, developer relations, the commercial push, all of it came from actors who had a direct commercial incentive to do that work. That wasn’t a gap in internet governance. It was internet governance working correctly. Expecting the Foundation to do business development is like expecting the IETF to have bought billboards for HTTP.
And a clearly defined, neutral base layer makes higher-layer building easier, not harder. Anyone making a long-term infrastructure bet (an institution, a protocol team, anyone planning in years rather than quarters) needs to know what the base layer will never compromise on. Uncertainty about the base layer is the thing that actually deters serious building. The mandate removes that uncertainty. It is the opposite of an obstacle to adoption.
The mandate even has a word for this posture: subtraction. The Foundation deliberately reducing its own influence over time, so the protocol doesn’t depend on it. A Foundation chasing business development is a Foundation expanding its footprint, which is the exact opposite of what it just committed to.
“But,” I hear you interrupt, “someone has to do the outreach.” Yes. Someone does. The mandate names the worry directly, the one that goes “if the Ethereum Foundation, with its stature and legitimacy, doesn’t strive to stay front and center, then who else realistically could?” The answer is that a healthy population of builders produces those on its own, with the base layer legible enough to write a business plan against.
Compliance belongs upstream
The second objection is that by refusing to bend on censorship resistance and privacy, the Foundation makes life harder for regulated institutions and hands ammunition to everyone who wants Ethereum to fail.
I think the opposite is true, and this is the part of the mandate I would defend most strongly.
CROPS commits the Foundation to keeping compliance mechanisms off the base layer. Know-your-customer checks, anti-money-laundering rules, transaction monitoring: all of that belongs at the application layer. In smart contracts, in regulated products, in the custody wrappers that institutions build on top of Ethereum.
The reason this matters is structural. The moment you accept the framing that the protocol itself should enforce compliance, every future regulatory demand becomes a protocol-level argument. Whose rules get encoded? Updated by whom, and on what timeline? You have turned a settled base layer into a permanent negotiation.
A base layer that can be modified for one regulator can be modified for any regulator.
That is the capture risk that makes infrastructure untrustworthy over long horizons, and it is exactly what the application-layer model avoids. Regulated DeFi protocols enforce KYC at the contract level. Compliant stablecoins keep their blacklist functions. Institutional custody wraps Ethereum access however the rules require. None of that touches the base layer, and none of it needs to.
This is simply how regulated industries interact with neutral infrastructure everywhere else. Banks are heavily regulated, and they do not expect the electricity grid to run identity checks on the current they draw. Regulators adapt to foundational infrastructure. They are slow about it, but they adapt, and the history of internet regulation shows it happening over and over. Hand them a protocol willing to enforce their rules, and you remove their reason to adapt completely. That isn’t a concession. It is a strategic mistake that compounds over decades.
The governance complaints are real. The mandate makes them fixable.
Now the criticism I do take seriously.
The Foundation has real challenges. Governance opacity, voting structures that aren’t disclosed, thin spending transparency, weak accountability. Those are legitimate, and I’m not going to pretend the mandate makes them disappear.
But they are downstream problems. They are organizational, they are tractable, and they are far easier to fix once the question of purpose is settled than while it is still open. Try to reform governance while the mission itself is contested and you end up debating two things at once and resolving neither. Sequence matters here. Get the constitutional layer right first, then build institutional reform on top of it. The mandate is the constitutional layer, and it is a precondition for the rest of the work, not a distraction from it.
History suggests this: The Internet Corporation for Assigned Names and Numbers (ICANN) was genuinely chaotic for years with accusations of capture, opaque decisions, questionable spending, national governments trying to pull it in different directions. Serious people argued the dysfunction would fatally compromise the neutrality of the internet. It didn’t. The IETF had its own messy, contentious governance fights. In both cases the protocol layer absorbed the institutional turbulence above it, because the protocol’s values were clear enough that building carried on regardless. The dysfunction got addressed incrementally, and it never threatened the protocol itself.
That is the whole point of what the mandate calls the walkaway test: a protocol robust enough to keep working even if its stewards disappeared tomorrow.
Ethereum starts from a better position than early internet governance did. It is more ideologically coherent and considerably better at coordination. If ICANN survived its mess without a written constitution to anchor it, Ethereum can survive institutional reform with one.
Which brings me to the part that is uncomfortable to say plainly.
A large share of the loudest opposition comes from people whose roles, funding, or influence were shaped by a more interventionist Foundation. I don’t raise that to dismiss them. It is a human and entirely understandable response, and several of those critics are pointing at real transition costs. Losing institutional memory in the middle of a roadmap is a genuine concern. It is also a normal cost of an institution growing up, not evidence that the direction is wrong.
So we should separate the two. When the criticism is “this will be disruptive,” it is often correct, and the Foundation should be honest about that. When the criticism is “this is the wrong direction,” I think it is frequently the disrupted talking, and it means their objections were worth reading with their structural position in view.
What the mandate is actually for
The mandate was never going to be popular, and being popular was never its job. Its job was to be legible. To state, in writing, what Ethereum will and will not ever trade away, so that nobody building on it has to guess.
The business development will still happen. The institutional adoption will continue. It will happen the way it always should have: above the base layer, done by the people with the incentives to do them well, on top of a foundation whose identity nobody has to infer from a mood.
A decade from now, I expect this to read as the moment Ethereum stopped apologizing for what it is.