When a decentralized naming system that has quietly powered millions of Ethereum addresses suddenly decides it needs a full-time legal body and a five-person board, you know the conversation has shifted. I have followed ENS for years, watching it grow from a clever address-replacement tool into something closer to digital identity infrastructure. The latest governance move feels less like routine maintenance and more like a deliberate step toward institutional adulthood.
Why ENS Needed This Structural Shift
ENS has spent nearly a decade proving that human-readable names can sit comfortably on top of long cryptographic addresses. Names such as alice.eth or company.eth now appear across wallets, apps, and Layer 2 networks. Yet the organization behind those names remained, in legal terms, almost invisible. A pure DAO cannot easily sign contracts, hire permanent staff, hold trademarks in its own name, or sit at the table with traditional internet standards bodies. That gap has become harder to ignore.
The proposal that just cleared on-chain execution, often called the Next Era of ENS DAO, addresses the gap head-on. It transforms the existing ENS Foundation into a full-time operating entity with professional staff, a clear mandate, and control over a substantial endowment. At the same time it carefully fences off the protocol itself so that tokenholders keep final say over upgrades, fees, and core parameters. The balance feels deliberate rather than accidental.
The New Five-Seat Board and Its Makeup
Five voting directors now oversee the foundation. Alexander Urbelis steps in as executive director and holds one seat. ENS founder Nick Johnson occupies another. The remaining three seats go to independent directors: Kartik Talwar, Brett Sun, and Anthony Leutenegger. Those independent members receive 40,000 USDC each year and serve two-year terms that tokenholders can renew. If a director declines the compensation, the money goes to a nonprofit or public-goods project of their choosing. That detail is small but telling. It signals an attempt to keep incentives aligned without creating pure financial dependence.
Tokenholders retain the ability to appoint and remove directors. Removal is not a casual process. It requires a written petition, supporting evidence, a formal response window for the board, and a thirty-day cooling-off period before any vote. The design tries to prevent both sudden coups and permanent entrenchment. In practice it will only work if the community stays engaged enough to use the tools when needed.
What the Foundation Can and Cannot Control
Perhaps the most carefully drafted part of the proposal concerns the boundary between operational work and protocol governance. Smart-contract upgrades, registration pricing, fee structures, constitutional changes, the root key, and registry controls stay exclusively with ENS tokenholders. The foundation handles the messy off-chain reality: employment contracts, intellectual property, standards-body participation, and day-to-day execution of grants. That separation matters. Without it, the move toward a traditional foundation structure would have felt like a quiet centralization of power.
Protocol control remains exclusively with ENS tokenholders.
ENS Labs continues as a separate Singapore-based company with its own management. The foundation will hold trademarks and brand assets, then license the relevant rights back to Labs while funding its work through the existing grant relationship. The arrangement keeps operational continuity while clarifying who owns the intellectual property.
The Endowment and Its New Safeguards
Administrative control of the Endowment Safe, valued at roughly $65 million in ETH and stablecoins as of July, now sits with the foundation board through approved signers. The assets themselves have not moved to a new address. No director, employee, or private party gains beneficial ownership. That distinction is important for both legal and psychological reasons. Tokenholders remain the ultimate economic owners.
Every endowment transaction defaults to a nine-day timelock. During that window the ENS Security Council can cancel anything that appears unauthorized, incorrect, malicious, or outside the foundation’s approved mandate. The technical implementation relies on an OpenZeppelin Timelock Controller paired with a Blockful Security Council contract. Existing investment permissions granted to the endowment manager stay unchanged. The design adds friction without freezing the capital entirely.
A separate one-time transfer of one million ENS tokens moves to the Foundation Safe for future employee compensation. Those tokens carry strict conditions. Grants must use multi-year vesting. Compensation for a director or the executive director requires approval from independent board members. Until tokens are granted, the foundation cannot vote, delegate, lend, or pledge them. It cannot transfer them to ENS Labs or use them to pay Labs staff. If the foundation ever closes or tokenholders vote a recall, unused tokens return to the DAO. The restrictions feel almost paranoid in their thoroughness, which is probably the point.
Operational Wallet and Budget Discipline
The DAO’s operational wallet remains under its previous structure. As of July it held about $16 million in ETH and stablecoins, with active payment streams continuing under existing terms. Before regular operating funds flow, the executive director must submit a projected budget to the board and publish a high-level version on the governance forum. Setup transfers cannot exceed $500,000 before that disclosure, and the first annual budget is due within sixty days of the proposal’s adoption. Current grants and service-provider commitments run to their scheduled end. Future grant work, including the Service Provider Program, moves under the foundation while existing reporting duties stay in place.
I have seen too many crypto organizations treat budgets as afterthoughts. The requirement for public high-level disclosure before significant transfers is a quiet but useful discipline. It does not guarantee perfect spending, yet it raises the cost of careless decisions.
Speaking for .ens in Traditional Standards Bodies
Legal personality finally lets the foundation represent ENS in front of bodies such as ICANN, the IETF, and the W3C. At ICANN the foundation intends to pursue formal recognition and stewardship of .ens as a top-level domain. That ambition sits at the intersection of two naming systems that have largely ignored each other until now. Blockchain names and the legacy Domain Name System still operate in parallel universes. Bridging them requires someone who can walk into a meeting room and speak with recognized authority.
Other Web3 naming projects have already tested the waters. Some have sought approval for their own strings. ENS itself has experimented with hybrid approaches, including integration with ICANN-recognized domains that work in ordinary browsers and email clients. The foundation’s formal mandate simply makes those conversations more coherent. Whether traditional registries will welcome a blockchain-native TLD remains an open question, but at least the conversation can now happen without legal awkwardness.
For users in the United States the legal standing carries practical weight. Naming disputes and impersonation cases can end up in American courts. A registered entity is far better equipped to seek injunctions or defend trademarks than a pure on-chain organization. Formal recognition for DAOs remains limited across most U.S. jurisdictions. Wyoming has experimented with structures for decentralized organizations, yet an on-chain vote alone still does not give a DAO the same capacity to hire, hold assets, or appear in court.
Conflict-of-Interest Rules and Transparency
The foundation will adopt an interim conflict-of-interest policy covering directors and the executive director. Disclosures and recusals must be recorded publicly. Funding decisions that affect ENS Labs require support from a majority of eligible independent directors. A refined policy is due for board approval within ninety days. These rules will not eliminate every potential conflict, but they raise the visibility of those that arise. In a space that still struggles with insider deals, visibility itself is progress.
What This Means for the Broader DAO Landscape
I keep returning to a simple observation. Many DAOs reach a point where pure on-chain coordination becomes inefficient for certain tasks. Hiring full-time staff, managing intellectual property, or negotiating with legacy institutions requires legal wrappers and clear lines of authority. The risk is that those wrappers quietly re-centralize power. ENS has tried to design the wrapper so that the most important decisions stay with tokenholders while the foundation handles the rest. Whether that design holds under pressure will become clear only after the first serious disagreement.
The nine-day timelock and Security Council veto create a useful circuit breaker. They do not make the foundation powerless, yet they give the community time to react if something goes wrong. Combined with the petition-based removal process for directors, the structure contains more checks than many earlier foundation experiments. That does not make it perfect. It does make it more thoughtful than average.
One subtle benefit of the new structure is continuity of institutional memory. Pure DAOs often lose operational knowledge when key contributors step back or move on. A full-time executive director and professional staff can preserve context across cycles of tokenholder attention. At the same time the board remains accountable to those same tokenholders. The dual structure tries to capture both the stability of a traditional organization and the legitimacy of decentralized ownership.
Practical Implications for Name Holders and Developers
For ordinary .eth name holders the day-to-day experience should change little in the short term. Registration, renewal, and resolution continue under existing smart contracts. The real shifts will appear in areas that most users never see: how grants are administered, how trademarks are enforced, and how ENS presents itself in policy discussions. Developers who rely on ENS infrastructure may notice more consistent support and clearer roadmaps once a professional staff is in place.
The one-million-token compensation pool could also attract talent that previously hesitated to work full-time for a pure DAO. Multi-year vesting reduces the risk of short-term extractive behavior. Independent-director approval for senior compensation adds another layer of scrutiny. None of these mechanisms guarantee good outcomes, yet they raise the probability that the people hired will stay aligned with long-term protocol health.
Risks That Remain on the Table
No governance redesign eliminates every risk. Capture of the board by a coordinated minority remains possible, even with independent seats and removal procedures. The Security Council itself could become a point of contention if its members are perceived as unaccountable. The endowment, while protected by a timelock, is still large enough that a series of poorly judged investments could erode community trust. And the boundary between foundation operations and protocol control, however carefully drawn on paper, will face real-world tests when priorities conflict.
There is also the cultural risk. Some DAO participants view any move toward traditional legal structures as a betrayal of decentralization ideals. Others see pure on-chain governance as increasingly impractical for organizations of real scale. ENS has chosen a middle path. The success of that path will depend less on the elegance of the proposal and more on how the new directors and executive leadership behave under ordinary and extraordinary pressure.
Looking Ahead
The proposal has already completed on-chain execution. The foundation now has its legal standing, its five-seat board, and its mandate. The first budget is due within sixty days. Independent directors will begin their terms. The Security Council will watch endowment transactions. Tokenholders will continue to vote on protocol-level decisions. In the background the slow work of seeking recognition for .ens at traditional standards bodies can begin in earnest.
I have found that the most interesting governance experiments are the ones that try to keep two seemingly opposing goals in tension: operational effectiveness and decentralized legitimacy. ENS has just placed a large bet that those goals can coexist inside a carefully designed dual structure. The next twelve to eighteen months will show whether the design is robust enough for the real world. For anyone who cares about how blockchain identity systems mature, this particular experiment is worth watching closely.
The naming system that began as a simple way to replace long addresses has grown into something closer to public infrastructure. Public infrastructure eventually needs institutions that can speak, hire, sign, and defend. The question was never whether ENS would need such institutions. The question was whether it could create them without surrendering the decentralized control that made the project interesting in the first place. The answer that just passed on-chain is an attempt to do both at once. Time will tell how well that attempt holds.
In the end the story is less about any single board seat or token transfer and more about a broader maturation process. Many early crypto projects treated legal structure as an afterthought. ENS has now treated it as a core design problem, complete with timelocks, independent oversight, public budgets, and explicit boundaries around protocol power. That level of care is still rare. Whether it becomes a model or a cautionary tale depends on the people who now sit in those five chairs and on the tokenholders who retain the power to replace them.
The endowment sits under a nine-day window. The board serves two-year terms. The protocol remains under tokenholder control. The foundation can finally walk into rooms that a pure DAO could not enter. Those are the concrete changes. The cultural and political consequences will unfold more slowly, in the ordinary work of hiring, budgeting, negotiating standards, and responding to the first serious disagreement. For a system that already underpins millions of names, getting those ordinary details right may matter more than any single dramatic proposal.
I remain cautiously optimistic. The design contains more friction and more transparency than many earlier attempts at the same problem. Friction and transparency are not guarantees of good outcomes, but they are better starting conditions than their opposites. ENS has given itself tools. Now it has to use them with the same care that went into writing the proposal.
