Ethereum Foundation cuts 54 staff — about 20% — as it reorganizes around its new "Mandate"

Three months after publishing a manifesto pledging to defend self-sovereignty over marketability, the EF has restructured into five "clusters" and parted ways with roughly a fifth of its people.

On June 23, 2026, the Ethereum Foundation announced it had concluded a "months-long process of reorganization" and, in doing so, laid off 54 employees — described in the same post as "roughly 20% of the EF." That math implies a headcount of around 270 before the cuts. The EF framed the reorganization as the implementation of two documents: the EF Mandate, published March 13, 2026, and a Treasury Management Policy, which the June post references but does not reproduce or date.

Both are the EF's own blog posts — authoritative on what the organization is doing and saying, but also the organization's own framing of itself. That distinction matters for how to read the language, which is closer to manifesto than press release.

What actually changed

The EF says it now organizes work into five domain "clusters" plus operations and management:

• Protocol layer — core protocol work: shipping forks, reducing complexity, defending the transaction pipeline against "toxic MEV and privileged orderflow," and turning long-horizon research (post-quantum security, zkEVM, L1 privacy) into protocol changes. The post is explicit that this cluster "does not exist to make Ethereum more marketable or focused on short-term interests."
• Access layer — making self-sovereign actions usable in practice: "reading the chain, transacting, proving, delegating, and exiting," including for AI agents acting on users' behalf. Its stated principle is the "zero option": for every intermediated path, a credible intermediary-free path must exist.
• User layer — user research, personas, education, impact evaluation. The EF says the goal is "not for the EF to become a product studio."
• Community layer — how the EF presents itself, and outreach to open-source, privacy, cryptography, and civil-liberties communities.
• Institutional layer — engagement with financial institutions, enterprises, governments, universities, and nonprofits, plus policy and regulatory tracking.

The organizing concept across all of this is CROPS — an acronym defined in the March Mandate as censorship resistant, open source, private, and secure. The June post uses "CROPS properties" repeatedly but never re-expands the acronym; a reader without the Mandate in hand would not know what it stands for.

The people leaving

The EF says the severance for departing staff is "the higher of one month's pay per year worked at the EF and the amount locally mandated by the individual's jurisdiction" — the same terms offered to colleagues who left "in the past few months." Transition support includes help finding another role in the ecosystem and "a small transition grant earmarked to cover individual transition expenses (career coaching and similar)." The EF says "many" of the 54 will be "finding ways to contribute to Ethereum from outside the EF in the coming weeks." No individuals, teams, or specific functions are named.

Key facts

• 54 employees laid off, described as "roughly 20% of the EF" — implying a pre-cut headcount near 270 (EF blog, June 23, 2026).
• Reorganization into five work clusters plus operations and management (EF blog, June 23, 2026).
• Severance: higher of one month's pay per year of service, or locally mandated minimum; same terms as prior recent departures (EF blog, June 23, 2026).
• Reorg framed as implementing the EF Mandate (published March 13, 2026) and a Treasury Management Policy (referenced, not published).
• CROPS = censorship resistant, open source, private, secure (EF Mandate, March 13, 2026).

The real-world read

The stated reason is timing-agnostic; the timing tells a different story. The June post says the cuts let the EF focus "without excessive disruption from short-term market movements." That is a curious justification for a 20% reduction: cutting a fifth of staff is a response to resource pressure, and invoking "market movements" while citing a "Treasury Management Policy" strongly implies the EF's treasury — largely ETH — drove the decision. Yet no dollar figures, no treasury size, no budget, and no runway numbers appear in either post. The financial premise of the whole exercise is asserted and then left unquantified.

The Mandate's rhetoric sits awkwardly against the institutional cluster. The March Mandate rails against "zero-sum financial crypto," "corpo-compromised crypto," and systems controlled by "intermediaries [who] extract." The protocol cluster explicitly refuses to make Ethereum "another financial rail controlled by intermediaries." But the new institutional layer exists to build "showcases" with financial institutions, enterprises, and governments — the intermediated paths. The EF's answer is that these integrations should "maximize CROPS properties" and preserve users' "practical ability to exit." Whether that reconciliation holds is exactly the tension the reorg papers over, and the EF asserts the good outcome ("many enterprises, governments, and nonprofits will realize that their incentives favor serving users") as a belief, not a demonstrated result.

The language is doing a lot of work. "Changing shape," "parting ways with 54 of our colleagues," "concluding a months-long process" — these are softening phrases for layoffs. The framing that departing staff will "find ways to contribute from outside the EF" is presented as reassurance, but it is not a commitment the EF can make on anyone's behalf.

What's conspicuously unsaid: which teams or functions were cut; whether protocol/core-dev work was protected or trimmed; the actual contents, date, or numbers of the Treasury Management Policy; and how the five-cluster structure maps onto the prior org. The EF says it will "share much more in the coming month" — meaning the substance of what changed is still pending.

Opinion, and whose

The claim that this leaves the EF "leaner and more focused" is the EF's own characterization. The belief that enterprises and governments will find their incentives favor strengthening self-sovereignty is the EF Board's stated conviction, not an established fact. The framing of the Mandate as "part constitution, part manifesto" is the EF's self-description. No external or independent assessment of the reorganization has emerged; all forward-looking statements here originate with the Foundation.

Sources

• Ethereum Foundation blog, "The EF's new structure," June 23, 2026 (Tier 1, primary) — the layoff count and ~20% figure, severance terms, and the five-cluster structure. This is the EF's own announcement; the framing is the organization's own.
• Ethereum Foundation blog, "The Promise of Ethereum: Introducing the EF Mandate," March 13, 2026 (Tier 1, primary) — the Mandate, the CROPS definition, and the mission language the reorg cites. This is a manifesto/constitution written by the EF Board about itself; treat its rhetoric as self-presentation, not neutral description.

This is news coverage, not financial advice.