ENThe distinction matters because Ethereum is a decentralized protocol maintained by independent developers, client teams, validators, node operators, application builders, researchers, and users. The Foundation is one participant within that broader system.
Key Takeaways:
- The Ethereum Foundation is a nonprofit support organization, not the owner or central governing authority of Ethereum.
- As of June 23, 2026, the EF is organized around five domain clusters, plus operations and management-support functions.
- Its work covers protocol development, research, security, ecosystem funding, education, community coordination, and institutional engagement.
- The EF finances its work through a treasury that includes ETH, liquid reserves, staking income, and carefully governed onchain strategies.
- The Ecosystem Support Program reported supporting 677 projects with $44.4 million in 2024.
| The Ethereum Foundation (EF) is a nonprofit that supports Ethereum through protocol research, grants, security work, developer infrastructure, and community coordination. It is not Ethereum itself. The network is maintained by independent developers, validators, node operators, and users. The EF can influence priorities, but it cannot change the protocol or force upgrades on the network. |
Ethereum.org defines the EF as a nonprofit that funds protocol development, supports ecosystem growth, and advocates for Ethereum. The same official reference states explicitly that the Foundation does not control or lead Ethereum and is only one part of a much larger ecosystem.
Three entities are often incorrectly treated as interchangeable:
The Foundation was created during Ethereum’s early development and helped establish the legal and financial infrastructure that supported the network’s launch. Its importance has remained substantial, but its formal authority over Ethereum has always been limited by the network’s decentralized design.
Ethereum has no CEO, shareholders, or single organization capable of changing its rules alone. Protocol changes depend on research, public discussion, software implementation, validator and node adoption, and wider ecosystem acceptance.
=>Read more: Ethereum Blockspace Explained: The Real Commodity of the Network
| The Ethereum Foundation matters because it funds essential public goods that often lack clear commercial incentives, including client maintenance, security, research, developer tools, and education. It acts as a steward and research sponsor, directing resources toward shared ecosystem needs. Its influence comes from expertise, funding, and coordination, but it does not control Ethereum’s network or protocol. |
Public blockchains depend on work that is essential but not always commercially attractive. A trading application can charge fees. A wallet company can sell services. A core client team maintaining consensus software may create value for every network participant without having an obvious business model.
The Ethereum Foundation helps address this coordination gap by supporting:
Ethereum.org groups the EF’s principal work into protocol development, ecosystem funding, and research. Its programs include the Ecosystem Support Program, academic grants, Devcon, and the Ethereum protocol bug bounty program.
This work can affect Ethereum’s direction. Funding one research area rather than another changes which ideas receive resources. Supporting particular client teams can influence implementation capacity. Convening developers can accelerate coordination.
However, influence should not be confused with command. The Foundation cannot force independent client developers to ship code, validators to run it, exchanges to support it, or users to accept it.
=> Read more: Does Ethereum Foundation Control Ethereum?
| The Ethereum Foundation combines board oversight and executive management with specialized teams for protocol, access, users, community, institutions, and operations. This structure separates strategic governance from research, ecosystem programs, communications, and external engagement. It governs the Foundation’s internal work and resources, not Ethereum’s decentralized network or protocol. |
According to the EF’s June 23, 2026 announcement, its current operating model contains five domain clusters, plus operations and management-support functions. The reorganization also reduced the organization by 54 colleagues, approximately 20% of the EF’s workforce.
Organizational area | Primary role |
| Protocol Layer | Hardens and scales the Ethereum protocol while protecting censorship resistance, openness, privacy, and security |
| Access Layer | Improves credible, verifiable access to Ethereum for reading data, transacting, proving, delegating, and exiting |
| User Layer | Connects technical work with real user needs, constraints, failure modes, and measures of self-sovereignty |
| Community Layer | Communicates the EF’s mission and builds relationships across Ethereum and aligned technology communities |
| Institutional Layer | Works with businesses, universities, governments, nonprofits, and policy stakeholders |
| Operations | Supports finance, legal, people, infrastructure, compliance, and organizational execution |
| Management and support | Sets organizational priorities and supports executive coordination |
This table maps the EF as an organization. It should not be interpreted as a map of Ethereum governance, because independent protocol contributors, node operators, validators, companies, and communities sit outside this hierarchy.
=> Read more: Ethereum Virtual Machine (EVM) Explained
The Board is responsible for organizational oversight, while executive management translates the Foundation’s mandate into operating priorities.
The most recent dedicated leadership update before this article stated that Bastian Aue had been appointed interim Co-Executive Director alongside Hsiao-Wei Wang after Tomasz Stańczak stepped down in February 2026.
That executive structure manages the Foundation’s employees, programs, treasury policies, and internal accountability. It does not manage Ethereum validators, independent client teams, decentralized applications, or ETH holders.
The domain-cluster model reflects the expanding range of problems surrounding Ethereum.
The Protocol Layer focuses on forks, trusted dependencies, privacy, security, toxic MEV, post-quantum research, zkEVM development, and other long-horizon protocol questions. The Access Layer focuses on whether users can access Ethereum without unverifiable intermediaries. The User, Community, and Institutional layers connect technical development with users, contributors, institutions, researchers, and policy environments.
Author Perspective
From the author’s perspective, the Ethereum Foundation should be judged by how effectively it strengthens Ethereum without becoming a permanent center of control. At Cryptothreads, we view its real value as the ability to fund research, security, client development, and public goods that commercial markets often neglect.
That influence matters, but it should not be confused with ownership. The better the EF becomes at coordinating experts and supporting difficult upgrades, the more important transparency and restraint become.
The key test is whether EF-backed work creates independent teams, standards, funding channels, and security institutions that can operate beyond the Foundation itself. Cryptothreads believes a healthy EF should lead where coordination is weak, step back where the ecosystem is capable, and remain accountable whenever its capital shapes technical priorities.
— Cryptothreads.io Editorial Team
| The Ethereum Foundation funds its work through a treasury holding crypto assets and liquid reserves, not through an Ethereum protocol tax. It supports research, grants, security programs, and independent teams by selling assets, staking ETH, and using selected onchain strategies. Resources are allocated through internal programs, research rounds, public-goods grants, and funding partnerships. |
The EF’s treasury supports salaries, research programs, grants, events, operations, and long-term commitments.
Its June 2025 Treasury Policy introduced two main operating indicators:
At the time the policy was published, the targets were annual operating expenditure equal to 15% of the treasury and a 2.5-year operating buffer. The policy also described an intended gradual reduction toward a long-term 5% annual expenditure baseline, subject to future review.
These values should be understood as policy targets at publication, not permanent protocol rules.
In February 2026, the EF announced that approximately 70,000 ETH was being staked, with staking rewards directed back to the treasury. Its setup uses distributed signing, multiple client pairings, minority clients, and infrastructure spread across several jurisdictions.
The broader treasury policy also permits carefully assessed onchain deployment. It emphasizes audited, permissionless, and established protocols while recognizing smart-contract, governance, custody, stablecoin, and oracle risks.
Funding mechanism | How it supports the EF | Main consideration |
| Treasury reserves | Finance operations, research, grants, and long-term commitments | ETH price and liquidity exposure |
| Periodic asset management | Converts assets into the liquidity needed for expenses | Sale timing and market impact |
| ETH staking | Produces ETH-denominated rewards for the treasury | Validator, slashing, infrastructure, and concentration risk |
| Onchain strategies | May generate returns or support aligned Ethereum applications | Smart-contract, governance, oracle, and custody risk |
| Funding coordination | Connects projects with EF grants and other capital providers | Selection quality and funding concentration |
The main distinction is that Ethereum does not automatically collect a protocol tax for the EF. Treasury decisions belong to the Foundation as an organization and are separate from Ethereum’s consensus rules.
The Ecosystem Support Program, or ESP, is a major funding mechanism. It contains two teams:
ESP uses funding wishlists and requests for proposals to identify work that the ecosystem needs. It also offers Office Hours for feedback, project guidance, and help navigating funding opportunities.
| The Ethereum Foundation ecosystem includes its Board, management, specialized teams, treasury functions, grant programs, and independent contributors. Client teams, researchers, validators, developers, companies, and community groups may work with the EF while remaining autonomous. Neither Vitalik Buterin nor the Foundation owns Ethereum. The ecosystem is a network of cooperating participants, not a corporate hierarchy. |
The Board oversees the legal organization, appoints executive leadership, reviews treasury and organizational decisions, and protects the Foundation’s mandate.
Its authority is internal to the EF. It does not serve as the board of the Ethereum network.
Management coordinates priorities, budgets, staffing, and execution. The domain clusters organize work around protocol resilience, access, users, communities, and institutions.
Individual teams may conduct research directly, fund external contributors, convene working groups, or maintain public infrastructure.
ESP is the Foundation’s main public-goods support and funding-coordination program. Its focus includes infrastructure, research, developer tools, community resources, and other free and open source work.
Many people who develop Ethereum are not EF employees. Client developers, Ethereum Improvement Proposal authors, security researchers, testing teams, and application developers can work for independent organizations or contribute individually.
Protocol changes emerge through open proposals, technical debate, implementation, testing, and adoption. Ethereum.org identifies core developers, researchers, EIP contributors, node operators, and validators as separate groups involved in Ethereum’s continuing development and governance.
Validators determine which valid blocks become part of Ethereum’s proof-of-stake chain. Node operators independently choose which software versions and protocol rules to run.
This provides an important check on organizational influence. An EF-supported proposal does not become an enforceable network rule merely because the Foundation supports it.
| The Ethereum Foundation funds shared infrastructure such as protocol clients, security, privacy, research, developer tools, education, and community programs. It prioritizes public goods that may lack clear commercial incentives. Funding does not imply ownership, and grant recipients can remain independent, publish open source work, and make their own technical decisions. |
The EF supports work related to:
The Foundation’s 2026 Protocol Layer mandate also emphasizes safe forks, reduced complexity, fewer trusted dependencies, resistance to censorship and capture, and research into areas such as zkEVMs, Layer 1 privacy, toxic MEV, and post-quantum security.
Public-goods funding may support compilers, testing frameworks, client libraries, debugging tools, formal-verification systems, data infrastructure, educational material, and other resources used by many independent teams.
These tools are often essential to Ethereum’s usability and security, even when they do not have a direct revenue model.
The Foundation has funded research across cryptography, game theory, networking, economics, security, formal verification, consensus, and social coordination.
Academic support expands the number of researchers studying Ethereum-related problems and can create work that remains available beyond a single company or product.
ESP reported the following support for 2024:
These figures represent ESP activity, not the EF’s entire annual budget or every form of Foundation spending.
The EF also supports conferences, educational initiatives, community networks, institutional research, policy engagement, and pathways for businesses or public institutions to understand Ethereum.
These functions can increase adoption, but the stated purpose of the 2026 structure is to preserve Ethereum’s core properties rather than optimize exclusively for short-term commercial growth.
| The Ethereum Foundation faces questions about influence, accountability, treasury risk, and decentralization. Although it does not control Ethereum, its funding and expertise shape priorities. It must support essential public goods without becoming indispensable. The June 2026 restructuring will test whether a leaner organization can preserve continuity, transparency, and ecosystem independence. |
The statement that the EF does not control Ethereum is accurate, but it does not mean the Foundation has no power.
Funding, hiring, convening, research access, and public communication can shape priorities. The important governance question is whether competing teams, funders, clients, and research communities retain credible alternatives.
Holding a large share of organizational reserves in ETH aligns the EF with Ethereum’s long-term health. It also exposes operating capacity to the same market cycle affecting the ecosystem it supports.
The treasury policy attempts to address this through liquidity planning, expenditure buffers, risk controls, and counter-cyclical spending.
Public-goods funding requires judgment. Relevant questions include:
Publishing allocation data, selection frameworks, milestones, and program reviews can make this influence easier to evaluate.
The June 23, 2026 restructuring reduced EF staffing by approximately 20%. The Foundation described the change as a move toward a leaner and more focused organization. Whether it improves execution will depend on continuity, delivery, transparency, and the ecosystem’s ability to absorb contributors who leave the EF.
A successful Ethereum Foundation must solve an unusual problem. It needs to remain capable enough to fund critical work while helping create an ecosystem that does not depend on the Foundation for every essential function.
That means its long-term success cannot be measured only by budget size, headcount, or visibility. It should also be measured by client diversity, independent research capacity, distributed funding, credible governance alternatives, and the resilience of public goods outside the EF.
No. The EF may fund research or contributors involved in an upgrade, but changes must pass through open technical discussion, implementation, testing, and adoption. Independent node operators and validators ultimately choose which compatible software to run.