The Metagov research team wanted to provide its understanding of this proposal/discussion per the evidence collected. We are not supporting any stance or proposal over another, we are here to provide evidence driven contextualization.
ENS is clearly at an inflection point. This thread and the Retro both surface a governance system under strain: delegates are overloaded with too many operational proposals, the DAO spends scarce voting attention on small questions instead of truly strategic ones, and there is no clear accountability layer between tokenholders and funded entities like Labs, service providers, and public goods initiatives. This is compounded by slow, inconsistent cross–working-group coordination, which blocks contributors and leaves the governance layer feeling slow, under‑specified, and misaligned with ENS’s role as core Ethereum infrastructure. At the same time, any attempt to fix this by moving budget authority into the ENS Foundation risks new legitimacy and conflict‑of‑interest concerns if the oversight body is not credibly independent from Labs.
A core tension underneath all of this is the difference between decentralizing decision‑making and decentralizing control over the protocol itself. On one side, ENS wants broad, permissionless participation in governance: many delegates, open working groups, community‑driven proposals, and public deliberation. On the other, it must preserve decentralization at the protocol layer: no single entity should be able to unilaterally change contracts, seize names, or capture the treasury, and the system must remain credibly neutral. Moving some operational authority into a smaller body like an expanded Foundation board would centralize decision‑making in one dimension, but if designed correctly it can actually protect protocol‑level decentralization by letting tokenholders retain sole authority over core protocol changes, constitutional amendments, and high‑level treasury moves, while a focused body handles noisy recurring operational questions that are currently burning out delegates. If the recommended Accountability and Transparency infrastructure are adopted this structure provides new levels of access for the entire ecosystem to assess the performance of the Foundation board which effectively empowers token holders like never before, perhaps the critical enabler of decentralization. (Side note…there is a field in governance management that looks at mimicry scenarios where organizational forms seem optimized for decentralization, or some other principle/purpose, but it never happens because the form is confused with the function (ie “if we just adopt the same org chart we will get the same result). The org chart does not matter as much as the function and without empowering token holders with data (capability) the ability to vote with the new knowledge (opportunity) and the understanding that their voice matters (motivation) then the decentralization function never materializes no matter what the org chart looks like.)
The preliminary recommendations coming out of the retro take a staged, infrastructure‑first approach rather than immediate structural surgery. They propose: (1) a 12‑month ENS Governance Masterplan with clear objectives, KPIs for each WG and for Labs, and a COI policy, to replace implicit expectations and ad‑hoc roles; (2) transparency and documentation infrastructure—standard templates, a shared governance data repository, and aligned quarterly reporting—so budgets, decisions, and outcomes are traceable instead of being held in people’s heads; (3) a delegate accountability baseline with expectations, participation and rationale metrics, COI disclosures, dashboards, and re‑delegation nudges, to make representation legible and reduce “ghost” or ossified delegation; (4) treasury oversight improvements via review clauses for large allocations and spend‑to‑outcomes reviews tied to the Masterplan; and (5) a graduated sanctions framework so repeated non‑compliance with reporting, participation, or COI norms leads to predictable, proportionate consequences instead of personality‑driven conflict.
If ENS were to adopt an expanded Foundation board as proposed, these recommendations effectively become the operating system that board runs on, and they are also the main safeguards against unhealthy centralization. The Masterplan and KPIs define the board’s mandate and evaluation frame, so it is judging Labs, service providers, and any successor to WGs against DAO‑ratified objectives rather than improvising priorities. The transparency and documentation stack becomes the board’s information substrate, ensuring that any concentration of operational authority is surrounded by radically open information: standardized reports, a shared repository, and clear links between spending and outcomes that tokenholders and delegates can audit and contest. Delegate accountability measures shape the interface between the DAO and the board, so the people who appoint and, if necessary, remove directors are themselves visible and accountable rather than “black boxes” of voting power.
Treasury oversight tools provide a review calendar and practice that an expanded board can internalize—structured reviews and conditional renewals instead of blunt, all‑or‑nothing funding decisions—while the graduated sanctions ladder gives the board proportional tools to adjust expectations and funding over time. Rather than decentralization expressing itself only through occasional high‑stakes “yes/no” votes or social pressure, it is embedded in these predictable processes: every large allocation has review conditions, every recurring failure has pre‑agreed consequences, and any board operating in this environment is constrained by publicly known rules.
In that sense, the retro’s recommendations and the Foundation‑board proposal are complementary. The recommendations build the data, rules, and feedback loops necessary for any accountability‑focused mid‑layer to function credibly and to centralize some operational work without undermining protocol‑level decentralization. The board proposal is one concrete structural instantiation of that mid‑layer. The remaining design questions—what exactly gets delegated to the board vs reserved for the DAO, how independent the board must be from Labs, and how to transition away from the current WG model without losing decentralization or contributor pathways—are easier to answer, and safer to implement, if ENS first adopts this governance infrastructure and then layers structural reforms on top of it.